diff options
| author | Iain Sandoe <iain@sandoe.co.uk> | 2025-09-01 14:05:48 +0100 |
|---|---|---|
| committer | Iain Sandoe <iain@sandoe.co.uk> | 2025-09-01 19:13:42 +0100 |
| commit | 4a84a19674ff7146b38449ddffda1b8d36da118f (patch) | |
| tree | 766e4d224df7bcae8bc0883b783cbbbcebe713a2 /libgomp/testsuite/libgomp.fortran/allocatable10.f90 | |
| parent | 713299077407bd1472e14fa10a8d4565932da8da (diff) | |
| download | gcc-4a84a19674ff7146b38449ddffda1b8d36da118f.zip gcc-4a84a19674ff7146b38449ddffda1b8d36da118f.tar.gz gcc-4a84a19674ff7146b38449ddffda1b8d36da118f.tar.bz2 | |
configure, Darwin: Do not claim .cfi_xxx instruction support.
While the assemblers used by Darwin that are based on LLVM, do
support .cfi_ instructions, their use triggers production of
compact unwind which currently does not interwork properly with
GCC's output.
When the system objdump is used in the configure process this is
currently working by good fortune (the objdump does not recognise
the command and we fail to detect the cfi_advance.
However, if a user has binutils objdump earlier in thier PATH then
we will detect support and try to use .cfi_ which will cause later
and hard-to-diagnose issues.
Until we have this resolved, force cfi instruction use off for
Darwin.
gcc/ChangeLog:
* configure: Regenerate.
* configure.ac: Do not claim cfi instruction support even
if the assembler has it.
Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
Diffstat (limited to 'libgomp/testsuite/libgomp.fortran/allocatable10.f90')
0 files changed, 0 insertions, 0 deletions