From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>,
Gary Oblock <gary@amperecomputing.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: What version of binutils is required
Date: Tue, 23 Feb 2021 10:27:10 +0100 [thread overview]
Message-ID: <f19926c5-c4b2-f628-53f2-8b6b934ca315@suse.cz> (raw)
In-Reply-To: <CAFiYyc2fZEY66=PNmOrCBUn-dKovcwZYeH8gdGggLtVSEvZMyw@mail.gmail.com>
On 2/23/21 9:41 AM, Richard Biener via Gcc wrote:
> On Tue, Feb 23, 2021 at 1:12 AM Gary Oblock via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> I'm having a "linker" error (according to Martin Liška) when
>> compiling a SPEC test (x264_r) with a vendor branch under development (my optimization is done at LTO time.)
>>
>> The binutils on my development machine is the version
>> that came with Ubuntu 18.02. Do I need to install a more
>> current version of binutils?
>
> Just try? Or at least tell us which version ships with Ubuntu 18.02 ...
You likely have version 2.30 (3 years old). Anyway I would test the latest binutils release.
Moreover, you can also experiment with ld.gold.
Cheers,
Martin
>
>> Thanks,
>>
>> Gary Oblock
>>
>>
>> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any unauthorized review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
next prev parent reply other threads:[~2021-02-23 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 23:58 Gary Oblock
2021-02-23 8:41 ` Richard Biener
2021-02-23 9:27 ` Martin Liška [this message]
2021-02-23 17:55 ` Gary Oblock
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=f19926c5-c4b2-f628-53f2-8b6b934ca315@suse.cz \
--to=mliska@suse.cz \
--cc=gary@amperecomputing.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).