public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/109263] [10/11/12 Regression] '-g0 -ggdb -flto' gives linker error
Date: Mon, 17 Apr 2023 09:14:40 +0000 [thread overview]
Message-ID: <bug-109263-4-l90l9JWF3e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109263-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109263
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:42b3d387f7335a4bc8846e3b7a2a78fb47be68b2
commit r12-9410-g42b3d387f7335a4bc8846e3b7a2a78fb47be68b2
Author: Richard Biener <rguenther@suse.de>
Date: Thu Mar 23 16:56:53 2023 +0100
lto/109263 - lto-wrapper and -g0 -ggdb
The following makes lto-wrapper deal with non-combined debug
disabling / enabling option combinations properly. Interestingly
-gno-dwarf also enables debug.
PR lto/109263
* lto-wrapper.cc (run_gcc): Parse alternate debug options
as well, they always enable debug.
(cherry picked from commit 4cbd5ef0350d8ab04993eb4c48ab80999fb4f358)
next prev parent reply other threads:[~2023-04-17 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 15:10 [Bug lto/109263] New: " lukeocamden at gmail dot com
2023-03-23 15:14 ` [Bug lto/109263] " marxin at gcc dot gnu.org
2023-03-23 15:58 ` rguenth at gcc dot gnu.org
2023-03-23 18:24 ` [Bug lto/109263] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2023-03-27 6:45 ` cvs-commit at gcc dot gnu.org
2023-03-27 6:46 ` [Bug lto/109263] [10/11/12 " rguenth at gcc dot gnu.org
2023-04-17 9:14 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-02 12:45 ` [Bug lto/109263] [10/11 " cvs-commit at gcc dot gnu.org
2023-07-07 10:07 ` [Bug lto/109263] [10 " rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109263-4-l90l9JWF3e@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).