From: Andris Pavenis <andris.pavenis@iki.fi>
To: Jeff Law <law@redhat.com>, 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: Sun, 15 Nov 2015 08:28:00 -0000 [thread overview]
Message-ID: <5648423C.5050705@iki.fi> (raw)
In-Reply-To: <564585D5.8070105@redhat.com>
On 11/13/2015 08:40 AM, 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
> Instaled with a better ChangeLog. Presumably there's going to be a followup to simplify a bunch
> of hte djgpp configuration?
>
> jeff
>
>
>
There are large number of changes in djgpp related configuration files accumulated over many years.
Some cleanup and
verification whether all is still needed and and of course testing of both cross- and native
compiler is required.
It would be rather difficult to split it into parts. I'll going to submit configuration changes for
DJGPP
(gcc/config.host + gcc/config/i386/*djgpp*) in one large patch after cleanup and testing unless
there are objections.
Therefore small small separate changes can be expected first.
Andris
prev parent reply other threads:[~2015-11-15 8:28 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
2015-11-13 6:40 ` Jeff Law
2015-11-15 8:28 ` Andris Pavenis [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=5648423C.5050705@iki.fi \
--to=andris.pavenis@iki.fi \
--cc=dj@delorie.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).