Martin Kinkelin

Results 511 comments of Martin Kinkelin

> Is there a log somewhere, showing this code compiling on a 32-bit platform? So you don't take my word for it? :P - https://dev.azure.com/ldc-developers/ldc/_build/results?buildId=2905&view=logs&j=97a617bf-bcbd-5dfa-bba2-cfba2747b693 (Windows x86), https://dev.azure.com/ldc-developers/ldc/_build/results?buildId=2905&view=logs&j=d63d0aa7-5d01-5c9f-d5bd-b8a45119ae4e (Ubuntu 18.04...

> and I'm not sure, the druntime and phobos are built there I already told you they are built there, but as you won't take my word for it and...

@JohanEngelen: tests/fuzz_basic.d finally failed again [here](https://circleci.com/gh/ldc-developers/ldc/4165?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link); output: ``` 3173: WARNING: Failed to find function "__sanitizer_print_stack_trace". 3173: WARNING: Failed to find function "__sanitizer_set_death_callback". 3173: INFO: Seed: 607937059 3173: INFO: Loaded 1...

I found the `x86-64` vs. `x86_64` particularly annoying too. For some arch families, there's no 1:1 mapping (`x86` => `i[3-6]86`, `arm` => `armv{6,7a,...}`)...

I don't know of any either; that's why I've created a little list in https://wiki.dlang.org/Cross-compiling_with_LDC#The_-mtriple_command-line_option.

Same gdb as you, gdb-related failures using LLVM 3.7 when invoking `ctest -R dmd-testsuite`: dmd-testsuite-debug: - `runnable/gdb14313.d`: expected regex `.*4000065002`, actual `$1 = -294902294` dmd-testsuite: - `runnable/gdb14276.d`: expected `.*1234`, actual...

With gdb 7.11.1, LDC master, LLVM 3.9 and Linux x64 (Xubuntu 16.04), all gdb tests pass when performed manually EXCEPT for gdb10311 (captured local showing up as `` - it...

Inside dmd-testsuite-debug they all fail though, due to: ``` No line in the current file. Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not...

With https://github.com/ldc-developers/ldc/pull/1784, only `gdb10311` remains disabled. Shall we close this issue?

You're defining that symbol (and initializing with 0). Add an `extern` to reference the linker-generated special symbol. I don't know whether it holds the address as value, or whether its...