public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: FX <fxcoudert@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	       "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	       "sellcey@mips.com" <sellcey@mips.com>,
	       Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	       "burnus@net-b.de" <burnus@net-b.de>,
	       Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [Patch] Add to the libgfortran/newlib bodge to "detect" ftruncate support in ARM/AArch64/SH
Date: Fri, 28 Aug 2015 15:34:00 -0000	[thread overview]
Message-ID: <20150828151706.GA5933@arm.com> (raw)
In-Reply-To: <20150828094031.GA40378@arm.com>

On Fri, Aug 28, 2015 at 10:40:31AM +0100, James Greenhalgh wrote:
> On Tue, Aug 25, 2015 at 03:44:05PM +0100, FX wrote:
> > > 2015-08-25  James Greenhalgh  <james.greenhalgh@arm.com>
> > > 
> > > 	* configure.ac: Auto-detect newlib function support unless we
> > > 	know there are issues when configuring for a host.
> > > 	* configure: Regenerate.
> > 
> > Thanks for CC’ing the fortran list.
> > 
> > Given that this is newlib-specific code, even though it’s in libgfortran
> > configury, you should decide and commit what’s best. I don’t think we have
> > any newlib expert in the Fortran maintainers.
> > 
> > Wait for 48 hours to see if anyone else objects, though.
> 
> OK, it has been 48 hours and I haven't seen any objections. The newlib
> patch has now been committed.
> 
> I agree with Marcus' suggestion that we put the more comprehensive patch
> (which requires the newlib fix) on trunk and my original patch (which does
> not) on the release branches.
> 
> I'll go ahead with that later today.

Now in place on trunk (r227301), gcc-5-branch (r227302) and gcc-4_9-branch
(r227304).

Give me a shout if you see issues in your build systems.

Thanks,
James

  reply	other threads:[~2015-08-28 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  8:32 James Greenhalgh
2015-08-20 10:02 ` Marcus Shawcroft
2015-08-21 10:49   ` James Greenhalgh
2015-08-25 14:14     ` James Greenhalgh
2015-08-25 14:48       ` FX
2015-08-28 10:07         ` James Greenhalgh
2015-08-28 15:34           ` James Greenhalgh [this message]
2015-08-30 16:03             ` Hans-Peter Nilsson
2015-09-03  9:40               ` James Greenhalgh
2015-09-03 11:31                 ` Hans-Peter Nilsson
2015-08-20 21:06 ` Steve Ellcey

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=20150828151706.GA5933@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sellcey@mips.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).