public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Gary Oblock <gary@amperecomputing.com>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Collect2 issue
Date: Thu, 11 Feb 2021 09:54:33 +0100	[thread overview]
Message-ID: <ed1468e3-eed2-bc4e-c7be-96b4158c91d2@suse.cz> (raw)
In-Reply-To: <BYAPR01MB54646D9FBC4EA47B8ABDA4AAC68C9@BYAPR01MB5464.prod.exchangelabs.com>

On 2/11/21 9:40 AM, Gary Oblock via Gcc wrote:
> I'm running my new optimization (LTO with one partition)
> on a SPEC17 test.
> 
> I got the mysterious message
>    "collect2: error: ld returned 1 exit status"

Hello.

Can you please post full build log done with --verbose GCC argument?

Thanks,
Martin

> 
> Now, first off, with my debugging on at full tilt and it's
> clear my optimization bailed out after analyzing
> the code without doing anything.
> 
> Second, this is a canned test not modified by
> me or anybody else for that matter so, it's
> not a user error.
> 
> Finally, reading various blogs it seems that
> old object files hanging around can make
> collect2 to go bonkers. Therefore, I used
> specmake to clean the build and it didn't
> help, not that this makes any sense with one
> partition.
> 
> By the way, for those of you that get upset
> at the very notion of invoking LTO as one partition,
> it's actually not that bad. I can compiler gcc
> that way on a laptop in about 50 minuets using
> only 4.7% of my memory!
> 
> Any ideas?? What's happening, how to diagnose
> what's happening, how to work around it, etc...
> 
> Thanks,
> 
> Gary
> 
> 
> 
> 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.
> 


      reply	other threads:[~2021-02-11  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11  8:40 Gary Oblock
2021-02-11  8:54 ` Martin Liška [this message]

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=ed1468e3-eed2-bc4e-c7be-96b4158c91d2@suse.cz \
    --to=mliska@suse.cz \
    --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).