From: Jeff Law <law@redhat.com>
To: Andris Pavenis <andris.pavenis@iki.fi>,
GCC Patches <gcc-patches@gcc.gnu.org>,
DJ Delorie <dj@delorie.com>
Subject: Re: [PATCH] gcc.c: new macro POST_LINK_SPECS to be able to add additional steps after linking
Date: Fri, 13 Nov 2015 06:41:00 -0000 [thread overview]
Message-ID: <56458627.1060809@redhat.com> (raw)
In-Reply-To: <5642C46C.2060406@iki.fi>
On 11/10/2015 09:30 PM, Andris Pavenis wrote:
> On 11/10/2015 11:20 PM, Jeff Law wrote:
>> On 11/10/2015 11:16 AM, Andris Pavenis wrote:
>>> One may need to execute extra steps after linking program. This is
>>> required
>>> for example for DJGPP to run stubify.exe on file generated by linker.
>>>
>>> The only way how to achieve was to use LINK_COMMAND_SPEC. It would be
>>> much easier
>>> and less error prone to use new macro POST_LINK_SPEC introduced in this
>>> patch.
>>>
>>> Andris
>>>
>>> ChangeLog entry
>>>
>>> 2015 Nov 10 Andris Pavenis <andris.pavenis@iki.fi>
>>>
>>> * gcc.c: new macro POST_LINK_SPEC
>>> * doc/tm.texi.in: document POST_LINK_SPEC
>>> * doc/tm.texi: regenerate
>>>
>> Can you also include the changes to djgpp.h which exploit this
>> capability?
>>
>> Jeff
>
> OK. I'm only sending changes for djgpp.h. There are required changes to
> other files not included, so djgpp.h patch currently
> to illustrate use of POST_LINK_SPEC only not committing.
Thanks. I think the key is that y'all have to essentially duplicate and
hack of LINK_COMMAND_SPEC and this change allows the djgpp port to avoid
that problem.
Thanks again,
Jeff
>
next prev parent reply other threads:[~2015-11-13 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 18:16 Andris Pavenis
2015-11-10 21:20 ` Jeff Law
2015-11-11 4:30 ` Andris Pavenis
2015-11-13 6:41 ` Jeff Law [this message]
2015-11-13 6:40 ` Jeff Law
2015-11-15 8:28 ` Andris Pavenis
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=56458627.1060809@redhat.com \
--to=law@redhat.com \
--cc=andris.pavenis@iki.fi \
--cc=dj@delorie.com \
--cc=gcc-patches@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).