Martin Kinkelin
Martin Kinkelin
> Not sure why LDC needs to pass a target flag to Clang for a native build. Or where it gets the OS version https://github.com/ldc-developers/ldc/pull/4534. I'm not going to waste...
Yeah well I assume importC simply ignores the `register` keyword, so... **Edit**: I was actually expecting it to be defined to an empty macro in `importc.h` ;) - but we...
Imports are most likely processed before static asserts. This is nothing LDC-specific obviously.
The dwarf version can be customized via `-dwarf-version`.
So looks like emcc requires v5 then. I doubt any of this is LDC-related, all Emscripten toolchain specifics.
Well AFAICT from your output is that your `emcc` (which version?) doesn't support DWARF 5. `warning: unsupported DWARF version (5)` doesn't come from LDC itself (nor from LLVM I guess),...
Hmm, testing `-gc` instead of `-g` might be worth a try (using C++ as DWARF language then instead of D).
IIRC, the printed features are the explicit ones (`-mattr`), plus one of the few set here implicitly, like that `+cx16`. AFAIU, a `-mcpu` selects the min CPU model and so...
If you're interested in seeing the state of *all* features, then this should help (as pointer towards an implementation): https://github.com/ldc-developers/ldc/blob/20d22b1e36242423e073b246a621c46217a92277/driver/cpreprocessor.cpp#L128-L143 This might be nice for wasm32's ~13 features, but for...
> These warnings only happen during release builds with LTO(full) enabled. Okay that finally makes some sense now. I bet they vanish when using an emscripten with matching LLVM version.