From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9BFB53858409; Tue, 23 Jan 2024 10:30:29 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9BFB53858409
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706005830;
	bh=gsEBxsdyMPLU1FEF/m0YZxMFwc7uZZYqL6B0YZpMNi0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=aW4FalBvrZFIK1wc+CaVGRTrJjDWv6g+rXTHAqLEce1SdU0K147/oaatYuBgbj7xs
	 +7YVdfTNHxtEUCuCKezH6xbrJeqgXWitOxX6U6csflXnyhtZP+c3cNVWQQXZIB6R/e
	 IBtFWz3dd13VyMOlmlAP2uOEqCLOwQNO0VEFAAVo=
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107931] [12/13/14 Regression] -Og causes always_inline to
 fail since r12-6677-gc952126870c92cf2
Date: Tue, 23 Jan 2024 10:30:27 +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: 12.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107931-4-4wrgABQdnq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107931-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107931

--- Comment #27 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 23 Jan 2024, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107931
>=20
> --- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #25)
> > Btw, I'd rather go the opposite and make the testcase at hand always in=
valid
> > and diagnosed which means diagnose taking the address of always-inline
> > declared functions and never emit an out-of-line body for them.
>=20
> That would need an exception at least for gnu extern inline always_inline
> functions,
> because the way they are used in glibc requires &open etc. to be valid (a=
nd use
> then as fallback the out of line open).

Sure, already the C frontend should resolve to the out-of-line open call
there, we shouldn't do this in the middle-end.  Yes, indirect 'open' will
then not be fortified, but so what.=