public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Andris Pavenis <andris.pavenis@wippies.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 6/6] [DJGPP] configure.ac: enable LTO
Date: Sun, 13 Dec 2015 17:01:00 -0000	[thread overview]
Message-ID: <566DA471.5060005@redhat.com> (raw)
In-Reply-To: <566C4DE0.2080307@wippies.com>

On 12/12/2015 09:40 AM, Andris Pavenis wrote:
> On 12/11/2015 12:32 AM, Jeff Law wrote:
>> On 12/05/2015 10:25 AM, Andris Pavenis wrote:
>>> Patch enables LTO support for DJGPP in top level configure.ac
>>>
>>> Andris
>>>
>>> 2015-12-05 Andris Pavenis <andris.pavenis@iki.fi>
>>>
>>> * configure.ac: enable LTO for *-*-msdosdjgpp
>> OK once prereqs have gone in.  Note you should to the autoconf dance
>> to update the generated files.  Mention them in your ChangeLog as
>>     * configure: Regenerated
>>
>> jeff
>>
>>
> Updated patch is in attachment.
>
> Andris
>
> PS. Somebody other should apply this and my other DJGPP related patches
> as I do not have SVN write access.
I think the better solution is to get you write access :-)

https://gcc.gnu.org/svnwrite.html

You can list me as your sponsor.

Cheers,
Jeff

  reply	other threads:[~2015-12-13 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05 17:25 Andris Pavenis
2015-12-10 22:32 ` Jeff Law
2015-12-12 16:40   ` Andris Pavenis
2015-12-13 17:01     ` Jeff Law [this message]
2015-12-13 18:12       ` DJ Delorie
     [not found]         ` <56739EF4.2040800@wippies.com>
     [not found]           ` <56785A71.3040306@redhat.com>
     [not found]             ` <5678EC40.2040404@iki.fi>
     [not found]               ` <56904664.70508@redhat.com>
2016-01-09  7:36                 ` 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=566DA471.5060005@redhat.com \
    --to=law@redhat.com \
    --cc=andris.pavenis@wippies.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).