https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79975
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|i?86-pc-solaris2.*, |i?86-*-*, x86_64-*-*
|amd64-pc-solaris2.*, |
|x86_64-unknown-freebsd12.0, |
|i386-apple-darwin11.4.2, |
|i386-apple-darwin16.7.0 |
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-01-31
Host|i?86-pc-solaris2.*, |
|amd64-pc-solaris2.* |
Summary|SEGV in cc1 compiling |SEGV in cc1 compiling
|gcc.dg/rtl/x86_64/final.c |gcc.dg/rtl/x86_64/final.c
| |with -fno-dwarf2-cfi-asm
Ever confirmed|0 |1
Build|i?86-pc-solaris2.*, |
|amd64-pc-solaris2.* |
--- Comment #4 from Rainer Orth <ro at gcc dot gnu.org> ---
After fixing the detection of HAVE_GAS_CFI_DIRECTIVE on x86_64-pc-solaris2.*
with gas, I noticed that this failure disappeared on that target. So obviously
only targets with HAVE_GAS_CFI_DIRECTIVE 0 are affected.
And indeed, the SEGV can easily be reproduced on x86_64-pc-linux-gnu with
-fno-dwarf2-cfi-asm.
Since the testcase is compile-only anyway (thus not depending on toolchain
support
for cfi directives) and scans for those in the assembler output, I'll soon
submit
a patch to add an explicit -fdwarf2-cfi-asm which avoids the SEGV on all x86
targets.
