Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault when building toolchain with GCC 11 and glibc 2.12.1 #2021

Open
tawmoto opened this issue Aug 30, 2023 · 1 comment
Open

Comments

@tawmoto
Copy link

tawmoto commented Aug 30, 2023

  • Report crosstool-NG version
    Version does not show correctly, but I downloaded version 1.25 and compiled it manually
./ct-ng version
This is crosstool-NG version UNKNOWN
  • Report host OS and its version
    Xubuntu 22.04.02

Building GCC 10 works perfectly, building GCC 11 does not work.

from /home/taw/Desktop/crosstool/crosstool-ng-crosstool-ng-1.25.0/prefix/bin/.build/x86_64-unknown-linux-gnu/src/gcc/gcc/data-streamer.c:25:
[ERROR]    ./insn-flags.h:11097:8: internal compiler error: Segmentation fault
[ALL  ]    11097 | extern rtx        gen_sha256msg2                                 (rtx, rtx, rtx);
[ALL  ]          |        ^~~
[ALL  ]    0x7f5c8b02b51f ???
[ALL  ]    	./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
[ALL  ]    0x7f5c8b012d8f __libc_start_call_main
[ALL  ]    	../sysdeps/nptl/libc_start_call_main.h:58
[ALL  ]    0x7f5c8b012e3f __libc_start_main_impl
[ALL  ]    	../csu/libc-start.c:392

P.S. config.zip is not a zip file, I renamed it so I can upload
config.zip
build.log

@milkylainen
Copy link

That is an odd combo. There's inevitably going to be some sort of issues combining newer CCs with something as old as glibc 2.12 and a 2.6.32 kernel interface.

But it is most likely a compiler bug.
I don't have an answer, but you could try to force gcc emitted instructions to atleast SSE level arch by setting tune and arch to something proper. Provided that matches your target. I don't have high hopes though.

And even if you do succeed, it's probably an emission break from your old compiler, as most toolsets don't tend to set specific targets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants