February 17
On 2/17/2025 8:55 PM, Steven Schveighoffer wrote:
> On Monday, 17 February 2025 at 22:14:13 UTC, Walter Bright wrote:
>> Is this an issue with the new GC, or the old one?
> 
> Old gc

I'm a little surprised to see a problem crop up after 25 years of continuous use?

Perhaps try an older release of the compiler?

February 18
On 18/02/2025 6:22 PM, Walter Bright wrote:
> On 2/17/2025 8:55 PM, Steven Schveighoffer wrote:
>> On Monday, 17 February 2025 at 22:14:13 UTC, Walter Bright wrote:
>>> Is this an issue with the new GC, or the old one?
>>
>> Old gc
> 
> I'm a little surprised to see a problem crop up after 25 years of continuous use?
> 
> Perhaps try an older release of the compiler?

This has already been solved, see Johan's comments.

ASAN with a fake stack isn't operating properly.

February 18

On Monday, 17 February 2025 at 21:56:29 UTC, Luís Marques wrote:

>

On Sunday, 16 February 2025 at 22:40:58 UTC, Luís Marques wrote:

>

On Sunday, 16 February 2025 at 22:06:37 UTC, Johan wrote:

>

This used to work, but somehow does not work anymore since LDC 2.100 (I perhaps have forgotten about this and just noticed it). [2]

You are very welcome to help investigate why it is no longer working!

Sure, I'll have a look. Thanks.

I don't think this broke with the D 2.100. For instance, LDC 1.29.0 is based on 2.099.1 and exhibits the same problem. Even older LDC versions don't trip on this exact program but they do output AddressSanitizer CHECK failures.

==4108825==AddressSanitizer CHECK failed: /home/vsts/work/1/s/compiler-rt/lib/sanitizer_common/sanitizer_linux_libcdep.cpp:556 "((*tls_addr + *tls_size)) <= ((*stk_addr + *stk_size))" (0x78927e371080, 0x78927e371000)

I'll need some time to dig through the IR, the GC, etc.

It is likely related to LLVM version. Did you already check that? Possibly a subtle change in API.

>

If you are going to look at this, please let me know, to avoid duplicate efforts.

Not soon, no.

-Johan

February 19
On 2/17/2025 9:26 PM, Richard (Rikki) Andrew Cattermole wrote:
> This has already been solved, see Johan's comments.

Excellent! Carry on...

March 06

On Tuesday, 18 February 2025 at 18:05:41 UTC, Johan wrote:

>

It is likely related to LLVM version. Did you already check that? Possibly a subtle change in API.

I'm only now checking that, I ran into a lot of yak shaving tasks.

BTW, did LDC stop emitting warnings/errors since 1.35? E.g. for the ; vs {}

https://godbolt.org/z/K95E99a5z

March 07

On Tuesday, 18 February 2025 at 18:05:41 UTC, Johan wrote:

>

It is likely related to LLVM version. Did you already check that? Possibly a subtle change in API.

LDC 1.40.0 (git commit 9296fd6fcc) reproduces the problem with both LLVM 15.0 and 19.1, so for now it seems that this isn't related to something having changed on the LLVM side.

1 2
Next ›   Last »