public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Jeff Law <law@redhat.com>, David Edelsohn <dje.gcc@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH,RFC] collect2 LTO for AIX
Date: Wed, 01 Nov 2017 19:20:00 -0000	[thread overview]
Message-ID: <6d77f19b-18c8-2e51-456e-cc51a1711369@sifive.com> (raw)
In-Reply-To: <0ee55db0-8824-bfb9-33c0-a27ad39c5add@redhat.com>

On 10/30/2017 12:13 PM, Jeff Law wrote:
> On 10/13/2017 12:04 PM, David Edelsohn wrote:
>> This patch adds the basic LTO scanning pass to the COFF support in
>> collect2.  I don't believe that this change should affect other COFF
>> targets adversely (do they even use collect2?), but I wanted to give
>> people an opportunity to comment.
> I honestly can't remember what the COFF targets do anymore :-)  Didn't
> we delete them all a while back?  I see that the generic COFF targets
> died back in gcc-4.4.

We still have PE-COFF for Windows and XCOFF for AIX.  The SVR3 Unix 
COFF, embedded COFF, and ECOFF (MIPS/Alpha) support is gone.  Hopefully 
Microsoft and IBM will see the light someday and switch to ELF.

Jim

  parent reply	other threads:[~2017-11-01 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 18:07 David Edelsohn
2017-10-30 19:20 ` Jeff Law
2017-10-31 19:28   ` David Edelsohn
2017-11-01 19:21     ` Jim Wilson
2017-11-06 16:01     ` Jim Wilson
2017-11-06 17:01       ` Jim Wilson
2017-11-06 17:34       ` David Edelsohn
2017-11-01 19:20   ` Jim Wilson [this message]
2019-07-04 15:04 ` Martin Liška
2019-07-04 15:27   ` David Edelsohn
2019-07-04 15:53     ` Martin Liška
2019-07-06  3:11       ` 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=6d77f19b-18c8-2e51-456e-cc51a1711369@sifive.com \
    --to=jimw@sifive.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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).