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 5DD123858D20; Fri,  1 Sep 2023 17:30:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5DD123858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1693589435;
	bh=dfd1n12P1gD1OByDyzytwYznfdTB5x1AWsp0ZkRWPjY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ept0mWmfEtplo2B/O7YHUPfZn2evlqoekcZn339SZcsV5bqOBUfJKAUd8RC9UzWCv
	 iWoLZLqf7TNbnalkA+LfzC32FLJVRaTfystayGerK862nWMYnhMw0BQ2+yR24Clli3
	 kY9oRJjQzMsAzOztoRUMDKxJdjqATYdkO1zX//78=
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111243] The -Og option inlines functions, making for
 a poor debugging experience.
Date: Fri, 01 Sep 2023 17:30:34 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 13.2.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xry111 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111243-4-Rvv1ZeRIAs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111243-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111243-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=3D111243

--- Comment #11 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Alex Mohr from comment #10)
> (In reply to Xi Ruoyao from comment #9)
> > I believe the only real issue is imprecise documentation: "It is a bett=
er
> > choice than -O0" has some caveats and it's not always true.
>=20
> Is there a way to explicitly enable the compiler passes that collect debug
> info that are disabled at -O0?

I don't think so, many -fxxx optimize options have no effect at -O0.

But if you are using -Og you can add -fno-inline if you really don't want
inlining.=