public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/90392] Bogus value for %u in LINK_PLUGIN_SPEC
Date: Fri, 17 Apr 2020 17:43:37 +0000 [thread overview]
Message-ID: <bug-90392-4-4l6LPZmihY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90392-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90392
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Summary|[8/9/10 Regression] |Bogus value for %u in
|Assertion failure in |LINK_PLUGIN_SPEC
|ldlang.c:6868 when |
|compiling with -flto |
--- Comment #13 from Jeffrey A. Law <law at redhat dot com> ---
Updating summary, dropping regression marker. Behavior seen as far back as
gcc-6, probably started before then. Given the dl.res has been consistent,
it's most likely not memory corruption -- if it were memory corruption I'd
expect to see different results over time rather than the consistent "dl.res"
output for %u.res.
next prev parent reply other threads:[~2020-04-17 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-90392-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:59 ` [Bug driver/90392] [9/10 Regression] Assertion failure in ldlang.c:6868 when compiling with -flto jakub at gcc dot gnu.org
2020-04-01 8:56 ` rguenth at gcc dot gnu.org
2020-04-01 11:14 ` ohaiziejohwahkeezuoz at xff dot cz
2020-04-17 15:55 ` [Bug driver/90392] [8/9/10 " law at redhat dot com
2020-04-17 17:43 ` law at redhat dot com [this message]
2021-06-01 8:14 ` [Bug driver/90392] Bogus value for %u in LINK_PLUGIN_SPEC rguenth at gcc dot gnu.org
2022-05-27 8:33 ` 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-90392-4-4l6LPZmihY@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).