The 17.2 update is accompanied by updated Command Line Tools,
so, having made a copy of the current CLTs, I let it update.
I get:
A. with ”-largs -Wl,-ld_classic” in the linker parameters:
/Users/wf/KDF9/emulation/Testing: failure
raised PROGRAM_ERROR : Open failed to get RW access
This is what should happen.
B. recompiled and relinked without ”-largs -Wl,-ld_classic”:
/Users/wf/KDF9/emulation/Testing: failure
raised CONSTRAINT_ERROR : erroneous memory access
OOPS!
Strangely, this is now the ONLY one out of dozens of regression tests
that fails in this software configuration.
Previously, they all failed at the link stage.
moi <findlaybill@blueyonder.co.uk> writes:
The 17.2 update is accompanied by updated Command Line Tools,
so, having made a copy of the current CLTs, I let it update.
I think you mean 14.2!
GCC 13/CLT 15.* still has issues with exceptions, eg this unresolved
issue: https://github.com/iains/gcc-13-branch/issues/10, and the
ld-classic dance fixes them as far as I can tell.
I'm working with this fix: https://github.com/simonjwright/xcode_15_fix
which is included in my GCC 13.2.0 build: https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-13.2.0-aarch64
...
Strangely, this is now the ONLY one out of dozens of regression tests
that fails in this software configuration.
Previously, they all failed at the link stage.
Yes, the 15.1 betas fixed the linking problem. I've no idea why some exceptions don't get caught/raise memory access errors. I do think that
the aarch64 GCC 14 has fixed the problem.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 44:48:51 |
Calls: | 8,141 |
Calls today: | 4 |
Files: | 13,085 |
Messages: | 5,858,055 |