public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/94249] [10 regression] Many -flto -fuse-linker-plugin tests FAIL: could not add symbols
Date: Mon, 23 Mar 2020 19:04:45 +0000 [thread overview]
Message-ID: <bug-94249-4-kYfFjs9RFL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94249-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94249
--- Comment #12 from dave.anglin at bell dot net ---
On 2020-03-23 1:37 p.m., danglin at gcc dot gnu.org wrote:
> I don't see a define for __BIG_ENDIAN__.
It seems we need this patch.
next prev parent reply other threads:[~2020-03-23 19:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 12:40 [Bug lto/94249] New: " ro at gcc dot gnu.org
2020-03-21 12:40 ` [Bug lto/94249] " ro at gcc dot gnu.org
2020-03-21 17:44 ` marxin at gcc dot gnu.org
2020-03-21 18:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-21 21:13 ` danglin at gcc dot gnu.org
2020-03-22 8:53 ` marxin at gcc dot gnu.org
2020-03-22 9:28 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-22 17:55 ` marxin at gcc dot gnu.org
2020-03-22 18:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-22 21:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-23 1:15 ` dave.anglin at bell dot net
2020-03-23 9:06 ` marxin at gcc dot gnu.org
2020-03-23 17:37 ` danglin at gcc dot gnu.org
2020-03-23 19:04 ` dave.anglin at bell dot net [this message]
2020-03-24 10:40 ` cvs-commit at gcc dot gnu.org
2020-03-24 10:41 ` marxin at gcc dot gnu.org
2020-03-24 17:05 ` cvs-commit at gcc dot gnu.org
2020-03-24 17:08 ` cvs-commit at gcc dot gnu.org
2020-03-24 17:10 ` cvs-commit at gcc dot gnu.org
2020-04-01 7:37 ` cvs-commit at gcc dot gnu.org
2020-04-01 17:25 ` raj.khem at gmail dot com
2020-04-01 17:25 ` raj.khem at gmail dot com
2020-04-02 11:07 ` marxin at gcc dot gnu.org
2020-04-02 13:41 ` raj.khem at gmail dot com
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-94249-4-kYfFjs9RFL@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).