public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Michael Meissner <mrmeissn@us.ibm.com>
Subject: Re: [RS6000] Don't pass --oformat to ld
Date: Wed, 02 Sep 2015 03:29:00 -0000	[thread overview]
Message-ID: <CAGWvnyna-DOs78trFAEMWeDYaHPACNzjEniKqGz7HmT+YoxRdA@mail.gmail.com> (raw)
In-Reply-To: <20150902013502.GT24814@bubble.grove.modra.org>

On Tue, Sep 1, 2015 at 9:35 PM, Alan Modra <amodra@gmail.com> wrote:
> bugzilla.redhat.com/show_bug_cgi?id=1255946 shows that gcc built with
> both powerpc64-linux and powerpc64le-linux support passes wrong linker
> options when trying to link in the non-default endian.  A --oformat
> option coming from LINK_TARGET_SPEC is only correct for 32-bit.
>
> It turns out that GNU ld -m options select a particular ld emulation
> (e*.c file in ld build dir) which provides compiled-in scripts or
> selects a script from ldscripts/.  Each of these has an OUTPUT_FORMAT
> statement, which does the same thing as --oformat.  --oformat is
> therefore redundant when using GNU ld built this century, except
> possibly when a user overrides the default ld script with -Wl,-T and
> their script neglects OUTPUT_FORMAT, and it isn't the default output.
> I don't think it's worth fixing this possible use case.
>
> Bootstrap and testing in progress.  OK for mainline assuming all is
> OK?
>
>         * config/rs6000/sysv4le.h (LINK_TARGET_SPEC): Don't define.
>         * config/rs6000/sysv4.h (LINK_TARGET_SPEC): Likewise.
>         (LINK_SPEC, SUBTARGET_EXTRA_SPECS): Delete link_target.

Okay.

Thanks, David

  reply	other threads:[~2015-09-02  3:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  1:35 Alan Modra
2015-09-02  3:29 ` David Edelsohn [this message]
2015-09-24  6:24 ` Michael Ellerman
2015-09-24 13:19   ` Alan Modra
2015-09-24 13:38     ` David Edelsohn

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=CAGWvnyna-DOs78trFAEMWeDYaHPACNzjEniKqGz7HmT+YoxRdA@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=amodra@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mrmeissn@us.ibm.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).