public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Carter <jcarter@johmar.engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ld --relax should be on by default
Date: Wed, 02 May 2001 19:30:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005515@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005510@msgid-missing>

Yes, it is the SGI compiler with the GNU linker.

The request was not to have the frontend always pass the
the flag to the linker, but have the linker do the right
thing and handle these legal cases without error. Many people
with big projects invoke the linker independantly from the
rest of the compiler.

I do not know what the "relax" option does exactly, but if
it is to relax an optimization then the correct behavior
would to be to have a flag to enable the optimization
and have the relax be the default, not the other way around.
Currently the gentle user has now way of knowing what's
going on and how to get his/her code linked.

Unless of course there is something inherently wrong with
the user code that is tripping this error. I don't believe
this is the case.

If changing the behavior of the IA64 Linux targeting linker
is not an option, then at a minimum the message should suggest
using the "relax" option.

Regards,

Jack

On May 2, 12:18pm, Jim Wilson wrote:
> Subject: Re: [Linux-ia64] ld --relax should be on by default
> Are you running into this problem using the SGI compiler with the GNU linker?
> That wasn't clear from your message.  That effects the kind of solution we
> need, since fixing gcc to always pass --relax to the linker isn't going to
> fix your problem.
>
> Jim
>-- End of excerpt from Jim Wilson




      parent reply	other threads:[~2001-05-02 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 17:01 [Linux-ia64] ld --relax should be on by default Jack Carter
2001-05-02 19:14 ` Jim Wilson
2001-05-02 19:18 ` Jim Wilson
2001-05-02 19:30 ` Jack Carter [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=marc-linux-ia64-105590693005515@msgid-missing \
    --to=jcarter@johmar.engr.sgi.com \
    --cc=linux-ia64@vger.kernel.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