backport PR61929 fix to 5 branch

[was: Re: [PATCH] [graphite] fix pr61929] On 17/07/15 06:31, Tobias Grosser wrote: On 07/17/2015 12:23 AM, Sebastian Pop wrote: This fixes bootstrap of GCC with BOOT_CFLAGS="-g -O2 -fgraphite-identity -floop-nest-optimize -floop-block -floop-interchange -floop-strip-mine". It passes regstrap

Re: [committed] Backport r238728 testsuite g++.dg/init/elide5.C fix (PR testsuite/77034)

On 16/08/16 09:18, Jakub Jelinek wrote: Hi! I've backported following fix to 6 branch: 2016-08-16 Jakub Jelinek PR testsuite/77034 Backported from mainline 2016-07-25 Jason Merrill * g++.dg/init/elide5.C (operator

Re: Ping : [Patch, fortran] PR48298 - [F03] User-Defined Derived-Type IO (DTIO)

  On August 27, 2016 at 1:15:51 PM, Janne Blomqvist (blomqvist.ja...@gmail.com(mailto:blomqvist.ja...@gmail.com)) wrote: > > Anyway, a small nit I found was the function st_set_nml_var in > libgfortran. This is an exported function, and thus part of the ABI. > So you cannot add arguments to

Re: [PATCH build/doc] Replacing libiberty with gnulib

-Ayush On 22 August 2016 at 10:13:40 PM, Pedro Alves (pal...@redhat.com) wrote: > On 08/22/2016 05:36 PM, ayush goel wrote: > > +# The expected version number for the various auto tools we will > > +# use after the import. > > +AUTOCONF_VERSION="2.69" > > +AUTOMAKE_VERSION="1.15" > >

Strip NOP_EXPR before building MEM

Hi, I have noticed that ivopts build MEM_REF (NOP_EXPR (address)) where NOP_EXPR converts one pointer type to another. Later it tries to expand it that on strict alignment targets punt on determining the alignment and winds expensive memory reference. It seems to make no sense to have NOP_EXPR

Re: [PATCH 3/4] (v2) Introduce class edit_context

On Wed, Aug 24, 2016 at 09:13:51PM -0400, David Malcolm wrote: > This version removes edit_context::apply_changes and related > functionality, retaining the ability to generate diffs. > > It also improves error-handling (adding a selftest for this). > > gcc/ChangeLog: > * Makefile.in

Re: PR35503 - warn for restrict pointer

On 26 August 2016 at 21:25, Jason Merrill wrote: > On Fri, Aug 26, 2016 at 7:39 AM, Prathamesh Kulkarni > wrote: >> However with C++FE it appears TYPE_RESTRICT is not set for the >> parameters (buf and fmt) >> and hence the warning doesn't get

[SPARC] Fix PR target/77324

This is the build failure introduced on SPARC by the recent reload patch, which causes the pass to be more strict about what it accepts. Tested on SPARC/Solaris, applied on the mainline. 2016-08-28 Eric Botcazou PR target/77324 * config/sparc/sparc.c