From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AE76B3861872; Thu, 2 Jul 2020 16:10:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE76B3861872 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593706213; bh=AtZ5qSoXz0a4PN7n8XXqf48gb7KDQnVD0QRrYNlQ3bw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uSSd5U9FVDC+UfcDeT7LdEXwTsSTwgfVi7PuI5i0hkuzChRVTPYhhdAgmjXV7T7OM Qjvd9bs8Vg38P+Y4WKtaGZ2JQYuxSAbGi2CxN7lJ6K26ffpJAMcBS1P+5ROAToSC6M tZ9fXRm/RClWufk3ZFmGUVcaFqwl1UAOX4/T27vc= From: "mikpelinux at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95952] [8 Regression] gcc-8 bootstrap failure on powerpc64-linux Date: Thu, 02 Jul 2020 16:10:13 +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: 8.4.1 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: mikpelinux at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2020 16:10:13 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95952 --- Comment #12 from Mikael Pettersson --- (In reply to Peter Bergner from comment #11) > At some point in the past, GCC used to disable some instruction patterns > depending on whether the binutils you're building against supports those > instructions or not. Now, GCC will always generate every instruction you > ask it to, but you might get an assembler error trying to assemble those > instructions. I think that change was somewhere in the GCC8 or GCC9 > timeframe. It could be your old binutils in GCC8 is silently turning off > some support and that is causing the problem. I'll try building a 2.23ish > binutils and using that for my GCC8 build. OK. Meanwhile I had a successful bootstrap of GCC8 with binutils-2.34.=