From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 425A73858400; Thu, 26 Aug 2021 09:02:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 425A73858400 From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/102059] Incorrect always_inline diagnostic in LTO mode with #pragma GCC target("cpu=power10") Date: Thu, 26 Aug 2021 09:02:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 11.2.1 X-Bugzilla-Keywords: diagnostic, lto, rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: linkw 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 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, 26 Aug 2021 09:02:27 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102059 --- Comment #15 from Kewen Lin --- (In reply to Florian Weimer from comment #12) > (In reply to Richard Biener from comment #10) > > As of HTM it would make the testcase a user error - when using -mcpu=3D= power10 > > it would require building with -mcpu=3Dpower8 -mno-htm? >=20 > Or -mcpu=3Dpower8 should imply -mno-htm. It's not 100% compatible for sur= e, > but so is removing a feature from a later CPU that was present in an earl= ier > version and enabled by default in GCC. I suspect it's better to take the > compatibility hit at run time, rather than later at run time (once the us= ers > get their hands on POWER10 hardware). Not sure if we faced similar situations before, both power8 and power9 supp= ort HTM, looking forward to the inputs from port maintainers and experts.=