From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4C36638582B2; Thu, 1 Feb 2024 19:16:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C36638582B2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706814990; bh=eLoTlWc5v2C95NRzg3TRHbONPi0cxatmWvxamhyEEi4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yzUhmxxNtL8GSrZRztzx7urpOoggAbn5b96MmMR9ITfUxPvXJjwQkFVj2DXWS23JP ZJgIriZGGVmDUBSMocC95qOuZ0LBlJNd4hKInOTolIVvaSw9TlSHVgYiBEUvZB6+Ms h4AiIdixPhEmlDcODrXAmVYrUjtaPUWOBZ/p8rFE= From: "pinskia at gcc dot gnu.org" To: gcc-rust@gcc.gnu.org Subject: [Bug rust/113553] rust fails to build on sparc64-linux-gnu Date: Thu, 01 Feb 2024 19:16:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rust X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: --- 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=3D113553 --- Comment #6 from Andrew Pinski --- (In reply to John Paul Adrian Glaubitz from comment #5) > (In reply to Rainer Orth from comment #1) > > The build works for me just fine on sparc-sun-solaris2.11. > >=20 > > I've also fired one off on sparc64-unknown-linux-gnu which worked just = as > > well. > > It was a rough ride, however, with the build aborting with > >=20 > > xgcc: fatal error: cannot execute > > '/var/gcc/regression/master/6.4.0-gcc-gas-gld/build/./gcc/cc1plus': > > posix_spawn: Bad address > >=20 > > several times. When I ran make under strace -f, however, the build wor= ked > > just > > fine. Quite ugly, actually. >=20 > It seems that this can be avoided by building with one job, i.e. with "ma= ke > -j1". >=20 > Some playing around showed that this fixes the problem for me: >=20 > diff --git a/libiberty/pex-unix.c b/libiberty/pex-unix.c > index af98062a94c..a1d35820181 100644 > --- a/libiberty/pex-unix.c > +++ b/libiberty/pex-unix.c > @@ -574,8 +574,8 @@ pex_unix_exec_child (struct pex_obj *obj > ATTRIBUTE_UNUSED, > { > int ret; > pid_t pid =3D -1; > - posix_spawnattr_t attr; > - posix_spawn_file_actions_t actions; > + static posix_spawnattr_t attr; > + static posix_spawn_file_actions_t actions; > int attr_initialized =3D 0, actions_initialized =3D 0; >=20=20 > *err =3D 0; Let me look that seems like an unitialized variable. If it is obvious one, I will apply a patch. --=20 You are receiving this mail because: You are on the CC list for the bug.=