From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B6F983858D34; Thu, 2 May 2024 05:26:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B6F983858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714627603; bh=5u4up0U+WbpkjmUNu/rBfYo5yTgYb8bscvc8HYs9klk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dNBTC7hhetemr3NQfIhI2X8XuY4NC6oSrF5NkZU2xbyqPTptQ4uaS6xo1Ln6N6l7b S6WQvVX1K+PWpWAopngmD9ovHAHP82QaQ1R92aPp1T7vay0JIxkHjN0DpcscUvvx6R xeI/bIbOUjcmCJ2bjbryFt3UMI70OchglMV4/5kg= From: "ro at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114912] [15 regression] SIGBUS in wi::copy<> on SPARC Date: Thu, 02 May 2024 05:26:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 15.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D114912 --- Comment #3 from Rainer Orth --- (In reply to Aldy Hernandez from comment #1) > Since this happens while building libgcc during stage1, perhaps this can = be > reproduced with a cross? Would it be possible to get the preprocessed fi= le > that's failing? I doubt this can be seen in a cross: running the compilation under truss reveals the SIGBUS as 2834: Incurred fault #5, FLTACCESS %pc =3D 0x00723E58 2834: siginfo: SIGBUS BUS_ADRALN addr=3D0xFFBFC954 2834: Received signal #10, SIGBUS [caught] 2834: siginfo: SIGBUS BUS_ADRALN addr=3D0xFFBFC954 i.e. an unaligned access. While SPARC is a strict-alignment target, x86 ca= res little if any about alignment at all. > You could try /var/gcc/reghunt/sigbus-range/288807/./gcc/xgcc -save-temps > [blah blah], and attach the libgcc2.i file that gets generated. Sure, please find _muldi3.i attached. cc1 invocation is cc1 -fpreprocessed _muldi3.i -quiet -dumpbase _muldi3.c -dumpbase-ext .c -mcpu=3Dv9 -g -g -g -O2 -O2 -O2 -Wextra -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -version -fbuilding-libgcc -fno-stack-protector -fPIC -fvisibility=3Dhidden= -o _muldi3.s=