Re: [Contrib PATCH] Add scripts to convert GCC repo from SVN to Git

> On Aug 24, 2019, at 12:30 AM, Joseph Myers wrote: > > On Fri, 23 Aug 2019, Maxim Kuvyrkov wrote: > >> I propose that we switch to gcc-pretty.git repository, because it has >> accurate Committer and Author fields. Developer names and email >> addresses are extracted from source history, and

Re: [PATCH] Fortran - character type names in errors and warning - for review

On 13/09/2019 07:54, Janne Blomqvist wrote: On Mon, Sep 9, 2019 at 4:52 PM Mark Eggleston wrote: To work around these problems I added a new length field to gfc_typespec to used to produce the name of a character type if the character length structure is not present. The addition of the lengt

[PATCH] Fix PR fortran/91716

Hi, this fixes a test case where a short string constant is put in a larger memory object. The consistency check in varasm.c is failed because both types should agree. Since the failed assertion is just a gcc_checking_assert I think a back-port of this fix to the gcc-9 branch will not be neces

Re: [PATCH] Fix PR fortran/91716

On Fri, Sep 13, 2019 at 1:07 PM Bernd Edlinger wrote: > > Hi, > > this fixes a test case where a short string constant is put in a larger > memory object. > > The consistency check in varasm.c is failed because both types should agree. > > Since the failed assertion is just a gcc_checking_assert

Re: [PATCH] Fix PR 91708

On Thu, 12 Sep 2019, Bernd Edlinger wrote: > On 9/12/19 10:08 AM, Richard Biener wrote: > > On Wed, 11 Sep 2019, Bernd Edlinger wrote: > > > >> On 9/11/19 8:30 PM, Richard Biener wrote: > > > > More like the following? I wonder if we can assert that > > MEM_NOTRAP_P () are equal (see all the fo

Re: [PATCH 3/9] operand_equal_p: add support for OBJ_TYPE_REF.

On 8/20/19 8:39 AM, Richard Biener wrote: Anyhow, the original patch is OK if you compare OBJ_TYPE_REF_TOKEN/OBJECT irrespective of virtual_method_call_p and order the types_same_for_odr last since that's most expensive. Hi. It's done in the attached patch that survives bootstrap and regressio

[PATCH][GCC] Update my email address

Hi all, This patch changes my email address in the MAINTAINERS file. Committed as r275697. 2019-09-13  Sam Tebbs  gcc/ChangeLog     * MAINTAINERS (Sam Tebbs): Update email address.

Re: [PATCH] DWARF array bounds missing from C++ array definitions

On Fri, Sep 13, 2019 at 1:32 AM Alexandre Oliva wrote: > > On Sep 12, 2019, Richard Biener wrote: > > > Your new predicate looks a bit excessive here given it builds the type > > again? > > Err, there seems to be some misunderstanding here. The predicate avoids > outputting a type for the defini

doc patch committed: Fix typo

I committed this patch to fix a typo in the -flto docs. Ian 2019-09-13 Ian Lance Taylor * doc/invoke.texi (Optimize Options): Fix typo. Index: gcc/doc/invoke.texi === --- gcc/doc/invoke.texi (revision 275698) +++ gcc/doc/invoke.t

Re: [PATCH][GCC] Update my email address

Patch attached. On 13/09/2019 13:34, Sam Tebbs wrote: > Hi all, > > This patch changes my email address in the MAINTAINERS file. Committed > as r275697. > > 2019-09-13  Sam Tebbs  > > gcc/ChangeLog > >     * MAINTAINERS (Sam Tebbs): Update email address. > > diff --git a/MAINTAINERS b/MAINTA

Re: [PATCH] Fix PR 91708

On 9/13/19 1:23 PM, Richard Biener wrote: > On Thu, 12 Sep 2019, Bernd Edlinger wrote: > >> On 9/12/19 10:08 AM, Richard Biener wrote: >>> On Wed, 11 Sep 2019, Bernd Edlinger wrote: >>> On 9/11/19 8:30 PM, Richard Biener wrote: >>> >>> More like the following? I wonder if we can assert that

[PATCH testsuite, arm] cache fp16 hw effective-target tests

In some bare-metal environments, the tests for fp16 runtime support fail in a way that causes a timeout rather than immediate failure. (E.g., the runtime might provide a do-nothing exception handler that just sits in a tight loop and never returns.) This patch changes the effective-target tes

Re: [PATCH] Fix PR 91708

On Fri, 13 Sep 2019, Bernd Edlinger wrote: > On 9/13/19 1:23 PM, Richard Biener wrote: > > On Thu, 12 Sep 2019, Bernd Edlinger wrote: > > > >> On 9/12/19 10:08 AM, Richard Biener wrote: > >>> On Wed, 11 Sep 2019, Bernd Edlinger wrote: > >>> > On 9/11/19 8:30 PM, Richard Biener wrote: > >>> >

libgo patch committed: Don't use \? in grep pattern

This libgo patch avoids using \? in a grep pattern. It's not supported by Solaris grep. Just use * instead; it matches more but it shouldn't matter. This fixes GCC PR 91764. Bootstrapped and ran Go tests on x86_64-pc-linux-gnu. Committed to mainline. Ian Index: gcc/go/gofrontend/MERGE ===

Re: [PATCH 1/4] Remove old IPA-SRA, introduce tree-sra.h

> This patch removes the old IPA-SRA. Please see the covert letter for > more information about the whole patch-set. > > Martin > > 2019-07-23 Martin Jambor > > * dbgcnt.def: Remove eipa_sra. > * passes.def: Remove old IPA-SRA. > * tree-pass.h (make_pass_early_ipa_sra

Re: [PATCH 2/4] New parameter manipulation infrastructure

> 2019-08-20 Martin Jambor > > * Makefile.in (GTFILES): Added ipa-param-manipulation.h. > * cgraph.h (ipa_replace_map): Removed fields old_tree, replace_p > and ref_p, added fields param_adjustments and performed_splits. > (struct cgraph_clone_info): Remove ags_t

[committed v2 1/3][GCC] gnatmake: Accept the `--sysroot=' GCC driver option

According to `gnatmake' documentation: "Any uppercase or multi-character switch that is not a 'gnatmake' switch is passed to 'gcc' (e.g., '-O', '-gnato,' etc.)" however the `--sysroot=' switch is actually rejected: gnatmake: invalid switch: --sysroot=... likely because it is one of the very few

[PING^2][PATCH 0/3] GNAT test suite fixes for build sysroot

On Tue, 14 May 2019, Maciej W. Rozycki wrote: > In the course of setting up GCC regression testing for the RISC-V target > I have discovered that the GNAT test suite does not correctly respond to > the test environment settings passed from the test harness in my setup and > consequently no tes

Re: [PATCH 3/4] New IPA-SRA implementation

> This patch actually adds the analysis bits of IPA-SRA - both the > function summary generation and the interprocedural analysis and > decision stage. The transformation itself then happens in the call > graph cloning infrastructure changes which are in the previous patch. > Please see the cover

Re: [PATCH 4/4] Modifications to the testsuite

> This are all modifications to the testsuite required to get to the > state described in the cover letter of the entire IPA-SRA > patch-series. Please note that ipa/ipa-sra-2.c and ipa/ipa-sra-6.c > should actually be svn rm-ed instead as they try to invoke > functionality that the new IPA-SRA do

[patch, testsuite, arm] Fix ICE in gcc.dg/gimplefe-28.c

For the default multilib on arm-none-eabi, gcc.dg/gimplefe-28 has been getting an ICE because, while the target-supports infrastructure is probing to see if it can add the command-line options to enable the sqrt insn ("-mfpu=vfp -mfloat-abi=softfp"), it is not actually adding those options when

[PATCH] Fix up sqrt(x) < c and sqrt(x) >= c match.pd folding (PR tree-optimization/91734)

Hi! As mentioned in the PR, the sqrt (x) < c optimization into x < c*c sometimes breaks the boundary case, if c2=c*c is inexact then in some cases we need to optimize it into x <= c*c rather than x < c*c. The original bugreport is when c is small and c2 is 0.0, then obviously we need <= 0.0 rathe