From: "H.J. Lu" <hjl.tools@gmail.com>
To: Gary Oblock <gary@amperecomputing.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: A weird bug
Date: Thu, 4 Mar 2021 16:09:57 -0800 [thread overview]
Message-ID: <CAMe9rOoRCkyW55Y+fhCTbUA6V_7ShX87UxVoykJENKduXQTGTA@mail.gmail.com> (raw)
In-Reply-To: <BYAPR01MB5464AA4ED44CAAB71B389DDEC6979@BYAPR01MB5464.prod.exchangelabs.com>
On Thu, Mar 4, 2021 at 3:18 PM Gary Oblock via Gcc <gcc@gcc.gnu.org> wrote:
>
> Guys,
>
> I've been trying to debug a linker error (which I thought was a bug in
> my optimization.) Well it turns out it occurs in a brand new virgin
> version of the compiler running with binutils 2.36 which is the latest
> version. I'm posting this on both the binutils list and gcc list
> because people of either list are just as likely to have an idea about
> what's going on. Note, I tried to walk though the ld code in gdb but
> it's nontrivial trying figure out why an error occured. I can't just
> set a watch point on a flag because, at least in some places it seems
> like the default state of the flag is failure and the code then
> proceeds to try various things to see if they'll work.
>
> Regarding the compiler that I built:
Here are scripts I used to build Linux/x86-64 GCC toolchain:
https://gitlab.com/hjl.tools/x86-64-linux-toolchain
--
H.J.
next prev parent reply other threads:[~2021-03-05 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 22:06 Gary Oblock
2021-03-05 0:09 ` H.J. Lu [this message]
2021-03-05 1:37 ` Andrew Pinski
2021-03-05 9:26 ` Martin Liška
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=CAMe9rOoRCkyW55Y+fhCTbUA6V_7ShX87UxVoykJENKduXQTGTA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gary@amperecomputing.com \
--cc=gcc@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).