public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/91299] [10/11/12/13 Regression] LTO inlines a weak definition in presence of a non-weak definition from an ELF file
Date: Tue, 06 Sep 2022 07:20:56 +0000 [thread overview]
Message-ID: <bug-91299-4-DYfmBuH8jg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91299-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91299
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Summary|LTO inlines a weak |[10/11/12/13 Regression]
|definition in presence of a |LTO inlines a weak
|non-weak definition from an |definition in presence of a
|ELF file |non-weak definition from an
| |ELF file
--- Comment #14 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
gcc-4.9 used to get this right, so let's play the regression card? This should
not be in WAITING.
next prev parent reply other threads:[~2022-09-06 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91299-4@http.gcc.gnu.org/bugzilla/>
2022-07-20 6:29 ` [Bug lto/91299] " sen2403 at hotmail dot com
2022-07-20 7:23 ` amonakov at gcc dot gnu.org
2022-07-20 10:44 ` sen2403 at hotmail dot com
2022-07-26 12:27 ` amonakov at gcc dot gnu.org
2022-08-25 13:01 ` sen2403 at hotmail dot com
2022-08-25 13:22 ` sen2403 at hotmail dot com
2022-09-06 7:20 ` amonakov at gcc dot gnu.org [this message]
2022-10-18 7:50 ` [Bug lto/91299] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-07-07 10:35 ` [Bug lto/91299] [11/12/13/14 " 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-91299-4-DYfmBuH8jg@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).