From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 277303858415; Fri, 22 Mar 2024 13:55:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 277303858415 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1711115734; bh=KkmA5FNV0ezRPtMOVQa0BEMJZl56m1DtgLl+Hiie7HU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GGq5z476vKXdGMHqdJUpmIRvfnnkAUpHjZ+XTZHftcK/SZgWkFTYV9XG58kPUTDn5 2BoYFfcaC4NjgybOwr8E7hHyN0I8UdjvTa1yhXqZfJE0qM3HcLQPtQ0zEdMGCZXkBG QAhObZ29JK50vzsFXQO2El28U/L02vD6DmhcCkDg= From: "law at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113357] [14 regression] m68k-linux bootstrap failure in stage2 due to segfault compiling unwind-dw2.c since r14-4664-g04c9cf5c786b94 Date: Fri, 22 Mar 2024 13:55:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: build, ice-on-valid-code, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: law at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113357 Jeffrey A. Law changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 --- Comment #5 from Jeffrey A. Law --- So given my bootstraps (qemu) are working the most likely scenarios are eit= her a difference in the emulators or a difference in the configure setup. The first thing I would suggest would be to put the stage2 compiler under a debugger and find out why it faulted. That might help with understanding t= he problem. ie, are we segfaulting because we dereferenced a NULL pointer, or perhaps faulting because we did an unaligned access, or whatever. The next thing I would suggest would be extracting the .i file and confirmi= ng you can feed that to the stage2 cc1 and see the fault. Assuming you can, = then you ought to be able to do an object bisection. ie, replace .o files for t= he failing stage with those from a previous stage, relink, retest. It'll take= a while. But this usually results in finding a single trigger file. Once that's narrowed down we can figure out the next steps.=