From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1CE9E3857C73; Wed, 19 Jan 2022 14:58:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1CE9E3857C73 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104117] gcc10 fails to build icu for ppc64 on 10.5.8 (direct access to a floating-point constant) Date: Wed, 19 Jan 2022 14:58:14 +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: 10.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_gcchost target_milestone keywords cf_gccbuild cf_reconfirmed_on 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: Wed, 19 Jan 2022 14:58:15 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104117 Iain Sandoe changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Host|powerpc-apple-darwin9 | Target Milestone|--- |10.4 Keywords| |wrong-code Build|powerpc-apple-darwin9 | Last reconfirmed| |2022-01-19 --- Comment #1 from Iain Sandoe --- most likely present on earlier branches. The problem is that we have=20 double var =3D (double) 1; LRA decides that loading a constant integer 1 into a FPR and then using int->double is good. However, it (a) decides to do this in the prologue (before we have got a picbase set up) and (b) does not seem to be checking = that the target agrees that the addressing mode is legitimate (it is not). ---- NOTE: incidental changes on 11.x and master have hidden this (but the chang= es were not a fix for this bug, so it has most likely simply become latent).=