public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: iant@google.com
Subject: Re: [PATCH] LFS support for libbacktrace
Date: Tue, 27 Jun 2017 16:46:00 -0000	[thread overview]
Message-ID: <d3e6043c-1f8b-52ed-7edf-b94a49ed1985@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1706201315280.22867@zhemvz.fhfr.qr>

On 06/20/2017 05:15 AM, Richard Biener wrote:
> On Wed, 14 Jun 2017, Richard Biener wrote:
> 
>>
>> This fixes the [f]open use in libgfortran.  Doesn't fix the ones
>> in libsanitizer because those appearantly use a copy because they
>> need to rename stuff...
>>
>> Bootstrapped and tested on x86_64-unknown-linux-gnu, ok for trunk
>> and branches?
> 
> Ping.
> 
> Richard.
> 
>> Thanks,
>> Richard.
>>
>> 2017-06-14  Richard Biener  <rguenther@suse.de>
>>
>> 	* configure.ac: Add AC_SYS_LARGEFILE.
>> 	* config.h.in: Regenerate.
>> 	* configure: Likewise.
OK.
jeff

  reply	other threads:[~2017-06-27 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 10:40 Richard Biener
2017-06-20 11:15 ` Richard Biener
2017-06-27 16:46   ` Jeff Law [this message]
2017-06-20 23:03 ` Ian Lance Taylor via gcc-patches

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=d3e6043c-1f8b-52ed-7edf-b94a49ed1985@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=rguenther@suse.de \
    /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).