Lucier, Bradley J via Gcc <gcc@gcc.gnu.org> wrote:
I’m seeing an “Illegal Instruction” fault and don’t quite know how to
generate a proper bug report yet.
This is the compiler:
[Bradleys-Mac-mini:~] lucier% /usr/local/gcc-10.3.0/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc-10.3.0/bin/gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-10.3.0/libexec/gcc/x86_64-apple-darwin19.6.0/10.3.0/lto-wrapper
Target: x86_64-apple-darwin19.6.0
Configured with: ../../gcc-10.3.0/configure
--prefix=/usr/local/gcc-10.3.0 --enable-languages=c --disable-multilib
--enable-checking=release
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.3.0 (GCC)
Can someone suggest a way forward?
Please could you raise a PR (Bugzilla) -
(https://gcc.gnu.org/bugzilla/enter_bug.cgi?product=gcc)
.. the information here is enough to start
- but it would help to know what you were compiling when this occurred ..
adding ‘-save-temps’ to the compile line and adding the .i file to the BZ can
be helfpul.
.. I think this will take a little analysis (and isn’t something I've seen
in testing on either i7 or xeon w hardware).
thanks
Iain