public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/113357] New: [14 regression] m68k-linux bootstrap failure in stage2 due to segfault compiling unwind-dw2.c Date: Fri, 12 Jan 2024 17:01:23 +0000 [thread overview] Message-ID: <bug-113357-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113357 Bug ID: 113357 Summary: [14 regression] m68k-linux bootstrap failure in stage2 due to segfault compiling unwind-dw2.c Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: mikpelinux at gmail dot com Target Milestone: --- gcc-14 native(*) bootstrap on m68k-linux-gnu fails during stage2 as follows: ranlib libgcov.a /mnt/scratch/objdir14/./gcc/xgcc -B/mnt/scratch/objdir14/./gcc/ -B/mnt/scratch/install14/m68k-unknown-linux-gnu/bin/ -B/mnt/scratch/install14/m68k-unknown-linux-gnu/lib/ -isystem /mnt/scratch/install14/m68k-unknown-linux-gnu/include -isystem /mnt/scratch/install14/m68k-unknown-linux-gnu/sys-include -fno-checking -g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fPIC -I. -I. -I../.././gcc -I/mnt/scratch/gcc-14-20240107/libgcc -I/mnt/scratch/gcc-14-20240107/libgcc/. -I/mnt/scratch/gcc-14-20240107/libgcc/../gcc -I/mnt/scratch/gcc-14-20240107/libgcc/../include -DHAVE_CC_TLS -o unwind-dw2.o -MT unwind-dw2.o -MD -MP -MF unwind-dw2.dep -fexceptions -c /mnt/scratch/gcc-14-20240107/libgcc/unwind-dw2.c -fvisibility=hidden -DHIDE_EXPORTS during GIMPLE pass: switchlower /mnt/scratch/gcc-14-20240107/libgcc/unwind-dw2.c: In function 'execute_stack_op': /mnt/scratch/gcc-14-20240107/libgcc/unwind-dw2.c:524:1: internal compiler error: Segmentation fault 524 | execute_stack_op (const unsigned char *op_ptr, const unsigned char *op_end, | ^~~~~~~~~~~~~~~~ Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. make[3]: *** [/mnt/scratch/gcc-14-20240107/libgcc/shared-object.mk:14: unwind-dw2.o] Error 1 make[3]: Leaving directory '/mnt/scratch/objdir14/m68k-unknown-linux-gnu/libgcc' make[2]: *** [Makefile:17845: all-stage2-target-libgcc] Error 2 make[2]: Leaving directory '/mnt/scratch/objdir14' make[1]: *** [Makefile:21317: stage2-bubble] Error 2 make[1]: Leaving directory '/mnt/scratch/objdir14' make: *** [Makefile:21513: bootstrap] Error 2 This has been going on since 20231022, 20231015 was good. gcc-13 is also good. Starting a git bisect now, but it'll take at least several weeks to get a result. (*) M1 mini running Aranym running m68k-linux-gnu full-system emulation.
next reply other threads:[~2024-01-12 17:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 17:01 mikpelinux at gmail dot com [this message] 2024-01-12 17:11 ` [Bug target/113357] " pinskia at gcc dot gnu.org 2024-01-12 17:23 ` mikpelinux at gmail dot com 2024-01-27 17:27 ` mikpelinux at gmail dot com 2024-01-31 14:11 ` mikpelinux at gmail dot com 2024-03-22 13:55 ` [Bug target/113357] [14 regression] m68k-linux bootstrap failure in stage2 due to segfault compiling unwind-dw2.c since r14-4664-g04c9cf5c786b94 law at gcc dot gnu.org 2024-05-07 7:43 ` [Bug target/113357] [14/15 " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113357-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).