[testsuite] XFAIL gcc.dg/tree-ssa/ssa-dom-cse-2.c on SPARC 64-bit

For the same reason as on Alpha and PowerPC 64-bit. Tested on x86-64/Linux and SPARC64/Solaris, applied on the mainline. 2016-01-27 Eric Botcazou * gcc.dg/tree-ssa/ssa-dom-cse-2.c: XFAIL on SPARC 64-bit. -- Eric BotcazouIndex: gcc.dg/tree-ssa/ssa-dom-cse-2.c ===

Re: [PATCH] Fix PR69336

> The new test case fails on s390x: Likewise on SPARC 32-bit and 64-bit. -- Eric Botcazou

Re: PING^1: [PATCH] Add TYPE_EMPTY_RECORD for C++ empty class

On Tue, 26 Jan 2016, H.J. Lu wrote: On Tue, Jan 26, 2016 at 1:40 PM, Jakub Jelinek wrote: On Tue, Jan 26, 2016 at 01:21:52PM -0800, H.J. Lu wrote: Like this: /* Returns true if TYPE is POD for the purpose of layout and an empty class or an class with empty classes. */ static bool is_emp

Re: PING^1: [PATCH] Add TYPE_EMPTY_RECORD for C++ empty class

On Wed, Jan 27, 2016 at 09:10:14AM +0100, Marc Glisse wrote: > >Revised: > > > >/* Returns true if TYPE is POD of one-byte or less in size for the purpose > > of layout and an empty class or an class with empty classes. */ > > > >static bool > >is_empty_record (tree type) > >{ > > if (type == err

Re: [PR 69355] Correct hole detection when total_scalarization fails

On Tue, 26 Jan 2016, Martin Jambor wrote: > Hi, > > PR 69355 has revealed that when SRA attempts total scalarization of an > aggregate but this fails because the user type-casts a scalar field > and stores into a it a smaller aggregate (and the scalar field is not > written to, whether directly o

[PATCH, testsuite]: Disable some tests in gcc.dg/torture/pr68264.c for older glibcs

2016-01-27 Uros Bizjak * gcc.dg/torture/pr68264.c: Disable log1p test for glibc < 2.22 and expm1 test for glibc < 2.11. Tested on x86_64-linux-gnu, CentOS 5.11 and Fedora 23. OK for mainline? Uros. diff --git a/gcc/testsuite/gcc.dg/torture/pr68264.c b/gcc/testsuite/gcc.dg/torture/pr

Re: PING^1: [PATCH] Add TYPE_EMPTY_RECORD for C++ empty class

On Wed, 27 Jan 2016, Jakub Jelinek wrote: On Wed, Jan 27, 2016 at 09:10:14AM +0100, Marc Glisse wrote: Revised: /* Returns true if TYPE is POD of one-byte or less in size for the purpose of layout and an empty class or an class with empty classes. */ static bool is_empty_record (tree type)

[PATCH] Remove xfail from thread_local-order2.C.

g++.dg/tls/thread_local-order2.C no longer fail with Glibc-2.18 or newer since this commit: 2014-08-01 Zifei Tong * libsupc++/atexit_thread.cc (HAVE___CXA_THREAD_ATEXIT_IMPL): Add _GLIBCXX_ prefix to macro. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@213504 138bc75d-0d

[PATCH] S/390: Require a hardware vector support for test to succeed.

The test case works on S/390 too, but only with -march=z13 or later (i.e. if Gcc can make use of hardware vector support). Otherwise the optimization gets too complex. The attached patch forces Gcc to use -march=z13 instead of xfail'ing the test on S/390. What do you think about this approach? C

Re: [C PATCH] Fix -Wunused-function (PR debug/66869)

On Tue, Jan 26, 2016 at 5:18 PM, Jakub Jelinek wrote: > On Tue, Jan 26, 2016 at 04:21:08PM +0100, Richard Biener wrote: >> > --- gcc/c/c-decl.c.jj 2016-01-21 00:41:47.0 +0100 >> > +++ gcc/c/c-decl.c 2016-01-25 16:36:31.973504082 +0100 >> > @@ -10741,11 +10741,19 @@ c_write_global_de

Re: [PATCH] Fix up wi::lrshift (PR c++/69399)

On Wed, Jan 27, 2016 at 12:41 AM, Jakub Jelinek wrote: > On Tue, Jan 26, 2016 at 01:55:41PM -0800, Mike Stump wrote: >> On Jan 26, 2016, at 1:26 PM, Jakub Jelinek wrote: >> > will do cc1plus size comparison afterwards. >> >> We know the dynamic check is larger. You can’t tell the advantage of >>

[PATCH] PR other/69006: S/390: Fix extra newlines after diagnostics.

The attached patch removes a blank line after an error message. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69006 Ciao Dominik ^_^ ^_^ -- Dominik Vogt IBM Germany gcc/ChangeLog PR other/69006 * config/s390/s390-c.c (s390_resolve_overloaded_builtin): Remove trailing b

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

+This option is disabled by default for most languages, enabled by +default for languages that use garbage collection. This is not true as of this patch. Index: tree-ssa-loop-ivopts.c === --- tree-ssa-loop-ivopts.c (revision

Re: C++ PATCH for c++/69496 (ICE on VLA in constexpr function)

On Tue, Jan 26, 2016 at 08:58:06PM -0700, Martin Sebor wrote: > On 01/26/2016 04:02 PM, Marek Polacek wrote: > >The (invalid) testcase was causing an ICE because we were passing the result > >of array_type_nelts_top immediately into tree_int_cst_lt, but for VLAs, the > >result doesn't have to be a

Re: [PATCH, PR69110] Don't return NULL access_fns in dr_analyze_indices

On 26/01/16 17:59, Sebastian Pop wrote: Tom de Vries wrote: diff --git a/gcc/tree-data-ref.c b/gcc/tree-data-ref.c index a40f40d..4c29fc2 100644 --- a/gcc/tree-data-ref.c +++ b/gcc/tree-data-ref.c @@ -1510,8 +1510,9 @@ initialize_data_dependence_relation (struct data_reference *a, if (opera

Re: [PATCH] Fix up wi::lrshift (PR c++/69399)

On Wed, Jan 27, 2016 at 11:38:33AM +0100, Richard Biener wrote: > On Wed, Jan 27, 2016 at 12:41 AM, Jakub Jelinek wrote: > > On Tue, Jan 26, 2016 at 01:55:41PM -0800, Mike Stump wrote: > >> On Jan 26, 2016, at 1:26 PM, Jakub Jelinek wrote: > >> > will do cc1plus size comparison afterwards. > >> >

Re: [hsa merge 07/10] IPA-HSA pass

On 01/26/2016 12:41 AM, Jan Hubicka wrote: >> On Mon, Jan 25, 2016 at 04:21:50PM +0100, Martin Liška wrote: >>> On 01/16/2016 11:00 AM, Jan Hubicka wrote: Can't it be represented via explicit REF_ADDR or something like that? Honza >>> >>> Hi. >>> >>> Sure, I've just done a patch that

[PATCH] Fix PR sanitizer/PR69276

Following patch was kind of pre-approved by Jakub in: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69276#c4 Patch can bootstrap in x86_64-linux-gnu and survives regression tests. I also verified that newly added test-case works with the patch. Ready for trunk? Thanks, Martin >From 4e4575cfef5d0

[PATCH] Fix PR pch/68758

Hello. As mentioned in: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68758#c5, I consider more logic to encapsulate valgrind annotation magic within a ENABLE_VALGRIND_ANNOTATIONS macro rather than ENABLE_VALGRIND_CHECKING. With patch applied, ggc invalid reads/writes, reported by valgrind tool,

Re: [PATCH] Fix PR sanitizer/PR69276

On Wed, Jan 27, 2016 at 01:47:10PM +0100, Martin Liška wrote: > Following patch was kind of pre-approved by Jakub in: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69276#c4 > > Patch can bootstrap in x86_64-linux-gnu and survives regression tests. > I also verified that newly added test-case work

Re: [PATCH] Fix PR pch/68758

On Wed, Jan 27, 2016 at 1:52 PM, Martin Liška wrote: > Hello. > > As mentioned in: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68758#c5, I > consider > more logic to encapsulate valgrind annotation magic within a > ENABLE_VALGRIND_ANNOTATIONS > macro rather than ENABLE_VALGRIND_CHECKING. > > Wi

Re: [PATCH, 4.9, rs6000, testsuite] Fix PR69479

On Tue, Jan 26, 2016 at 4:46 PM, Bill Schmidt wrote: > Hi, > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69479 notes that > gcc.dg/and-1.c fails a scan-assembler-not test for nand, but the test > does pass in subsequent releases. The test author indicates in comment > #1 that we can just remov

Re: PING^1: [PATCH] Add TYPE_EMPTY_RECORD for C++ empty class

On Wed, Jan 27, 2016 at 1:03 AM, Marc Glisse wrote: > On Wed, 27 Jan 2016, Jakub Jelinek wrote: > >> On Wed, Jan 27, 2016 at 09:10:14AM +0100, Marc Glisse wrote: Revised: /* Returns true if TYPE is POD of one-byte or less in size for the purpose of layout and an empt

Re: [PATCH] Fix PR sanitizer/PR69276

On 01/27/2016 01:58 PM, Jakub Jelinek wrote: > On Wed, Jan 27, 2016 at 01:47:10PM +0100, Martin Liška wrote: >> Following patch was kind of pre-approved by Jakub in: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69276#c4 >> >> Patch can bootstrap in x86_64-linux-gnu and survives regression tests.

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

On Wed, Jan 27, 2016 at 3:18 AM, Bernd Schmidt wrote: >> +This option is disabled by default for most languages, enabled by >> +default for languages that use garbage collection. > > > This is not true as of this patch. Yes. As I said elsewhere, my intent is to do that as a separate patch. >>

Re: C++ PATCH for c++/69496 (ICE on VLA in constexpr function)

OK, but the testcase should go in ext/. Jason

Re: C++ PATCH for c++/69496 (ICE on VLA in constexpr function)

On Wed, Jan 27, 2016 at 09:08:27AM -0500, Jason Merrill wrote: > OK, but the testcase should go in ext/. Oops, will move it there then, thanks! Marek

Re: [hsa merge 00/10] Merge of HSA branch

Hi, sorry for getting so late to this: On Thu, Jan 21, 2016 at 05:10:17PM -0600, Gerald Pfeifer wrote: > On Tue, 19 Jan 2016, Richard Biener wrote: > > I think the merge warrants a NEWS entry on gcc.gnu.org/ > > ...and gcc-6/changes.html. :-) > > Martin, happy to help. Want to propose some tex

Re: [PATCH] PR other/69006: S/390: Fix extra newlines after diagnostics.

On Wed, 2016-01-27 at 12:01 +0100, Dominik Vogt wrote: > The attached patch removes a blank line after an error message. > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69006 Presumably this was exposed by the stricter testing I added to lib/gcc -dg.exp in r232837? >else if (num_matches > 1) >

[PATCH] Fix PR69166

The following fixes a missing check on commutativity / associativity in reduction detection. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2016-01-27 Richard Biener PR tree-optimization/69166 * tree-vect-loop.c (vect_is_simple_reduction): Always chec

Re: [Fortran, gcc-5, patch, pr69268, v1] [5 Regression] Sourced allocation calls function twice

Hi Paul, thanks for the review. Commited as r232876. Regards, Andre On Tue, 26 Jan 2016 18:36:28 +0100 Paul Richard Thomas wrote: > Dear Andre, > > The patch looks fine to me. OK for 5-branch. > > Thanks for the patch. > > Paul > > On 26 January 2016 at 13:28, Andre Vehreschild wr

Re: [PATCH][Testsuite] Fix scan-tree-dump failures with vect_multiple_sizes

On Fri, Jan 22, 2016 at 3:20 PM, Alan Lawrence wrote: > Since r230292, these tests in gcc.dg/vect have been failing on ARM, AArch64, > and x86_64 with -march=haswell (among others - when prefer_avx128 is true): > > vect-outer-1-big-array.c scan-tree-dump-times vect "grouped access in outer > loo

[patch] libstdc++/69295 Set FP options for failing special functions tests

This should fix the FAILs seen on trunk for some targets. Tested powerpc64-linux, comitted to trunk. commit 6f952bce33752add3fd08efac03bc19782ef09b8 Author: Jonathan Wakely Date: Wed Jan 27 13:55:45 2016 + Set FP options for failing special functions tests PR libstdc++/69295

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

On 01/27/2016 02:59 PM, Ian Lance Taylor wrote: +This option is disabled by default for most languages, enabled by +default for languages that use garbage collection. This is not true as of this patch. Yes. As I said elsewhere, my intent is to do that as a separate patch. Then the followu

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

On Wed, Jan 27, 2016 at 7:16 AM, Bernd Schmidt wrote: > > Still, I feel uncomfortable about making a promise we don't really expect to > fully keep yet, so I would prefer this option to be undocumented for now. I > won't object if someone else wants to approve it as a normal option however. Are y

[COMMITTED] Add myself as GCC maintainer

I've added myself to the "Write After Approval" maintainers (Committed revision 232880): Index: ChangeLog === --- ChangeLog (revision 232874) +++ ChangeLog (working copy) @@ -1,3 +1,7 @@ +2015-01-27 Wilco Dijkstra + + *

Re: C++ PATCH for c++/69379 (ICE with PTRMEM_CST wrapped in NOP_EXPR)

On 01/25/2016 03:00 PM, Marek Polacek wrote: It appears that handling the case when the types don't match is sufficient, at least all the tests pass, thus the following should be enough. OK. + "reinterpret_cast has different types"); Let's say "a reinterpret_cast i

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

On 01/27/2016 04:18 PM, Ian Lance Taylor wrote: On Wed, Jan 27, 2016 at 7:16 AM, Bernd Schmidt wrote: Still, I feel uncomfortable about making a promise we don't really expect to fully keep yet, so I would prefer this option to be undocumented for now. I won't object if someone else wants to a

[PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

Hi, Currently STV pass may require a stack realignment if any transformation occurs to enable SSE registers spill/fill. It appears it's invalid to increase stack alignment requirements at this point. Thus we have to either assume we need stack to be aligned if are going to run STV pass or disable

Re: PING^1: [PATCH] Add TYPE_EMPTY_RECORD for C++ empty class

On Wed, Jan 27, 2016 at 5:46 AM, H.J. Lu wrote: > On Wed, Jan 27, 2016 at 1:03 AM, Marc Glisse wrote: >> On Wed, 27 Jan 2016, Jakub Jelinek wrote: >> >>> On Wed, Jan 27, 2016 at 09:10:14AM +0100, Marc Glisse wrote: > > Revised: > > /* Returns true if TYPE is POD of one-byte or les

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On Wed, Jan 27, 2016 at 7:34 AM, Ilya Enkovich wrote: > Hi, > > Currently STV pass may require a stack realignment if any > transformation occurs to enable SSE registers spill/fill. > It appears it's invalid to increase stack alignment requirements > at this point. Thus we have to either assume w

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On Wed, Jan 27, 2016 at 06:34:41PM +0300, Ilya Enkovich wrote: > @@ -5453,6 +5443,11 @@ ix86_option_override_internal (bool main_args_p, > opts->x_target_flags |= MASK_VZEROUPPER; >if (!(opts_set->x_target_flags & MASK_STV)) > opts->x_target_flags |= MASK_STV; > + /* Disable STV if -

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On Wed, Jan 27, 2016 at 7:34 AM, Ilya Enkovich wrote: > Hi, > > Currently STV pass may require a stack realignment if any > transformation occurs to enable SSE registers spill/fill. > It appears it's invalid to increase stack alignment requirements > at this point. Thus we have to either assume w

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

2016-01-27 18:43 GMT+03:00 H.J. Lu : > On Wed, Jan 27, 2016 at 7:34 AM, Ilya Enkovich wrote: >> Hi, >> >> Currently STV pass may require a stack realignment if any >> transformation occurs to enable SSE registers spill/fill. >> It appears it's invalid to increase stack alignment requirements >> at

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On 27 Jan 16:44, Jakub Jelinek wrote: > On Wed, Jan 27, 2016 at 06:34:41PM +0300, Ilya Enkovich wrote: > > @@ -5453,6 +5443,11 @@ ix86_option_override_internal (bool main_args_p, > > opts->x_target_flags |= MASK_VZEROUPPER; > >if (!(opts_set->x_target_flags & MASK_STV)) > > opts->x_ta

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On Wed, Jan 27, 2016 at 8:11 AM, Ilya Enkovich wrote: > On 27 Jan 16:44, Jakub Jelinek wrote: >> On Wed, Jan 27, 2016 at 06:34:41PM +0300, Ilya Enkovich wrote: >> > @@ -5453,6 +5443,11 @@ ix86_option_override_internal (bool main_args_p, >> > opts->x_target_flags |= MASK_VZEROUPPER; >> >if

[Patch, fortran, GCC-5/6, PR62536, v1] ICE (segfault) for invalid END BLOCK statement

Hi all, attached are two patches one for trunk and one for the gcc-5-branch, which fix an ICE when BLOCK statements are not closed correctly (too many END BLOCKs). Unfortunately did the patch I tailored for gcc-5 not work on trunk. GCC 5: The ICE is prevented by making sure that gfc_current_ns is

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

2016-01-27 19:18 GMT+03:00 H.J. Lu : > On Wed, Jan 27, 2016 at 8:11 AM, Ilya Enkovich wrote: >> On 27 Jan 16:44, Jakub Jelinek wrote: >>> On Wed, Jan 27, 2016 at 06:34:41PM +0300, Ilya Enkovich wrote: >>> > @@ -5453,6 +5443,11 @@ ix86_option_override_internal (bool main_args_p, >>> > opts->x_

Re: [PATCH, PR target/69454] Disable TARGET_STV when stack is not properly aligned

On Wed, Jan 27, 2016 at 8:29 AM, Ilya Enkovich wrote: > 2016-01-27 19:18 GMT+03:00 H.J. Lu : >> On Wed, Jan 27, 2016 at 8:11 AM, Ilya Enkovich >> wrote: >>> On 27 Jan 16:44, Jakub Jelinek wrote: On Wed, Jan 27, 2016 at 06:34:41PM +0300, Ilya Enkovich wrote: > @@ -5453,6 +5443,11 @@ ix8

[PATCH] Add NULL check for vectype in vectorizable_comparison

Hi, This is a trivial patch which adds a NULL check for vectype. We may have a NULL vectype in case of void call. Will commit as obvious to trunk after testing. Thanks, Ilya -- gcc/ 2016-01-27 Ilya Enkovich * tree-vect-stmts.c (vectorizable_comparison): Add NULL check for ve

Re: C++ PATCH for c++/69496 (ICE on VLA in constexpr function)

I wonder if it might be better to instead reject VLAs in constexpr functions altogether. Not because they're not in C++, but because C (or gcc) doesn't allow them to be initialized (and so accepting an initialized VLA is a g++ extension of an extension), and because in constexpr functions they ar

Fix PR ada/69488

This is the en masse failure of the gnat.dg/sso tests on Windows, which is the same DOS line termination issue I run into for gcc.dg/sso on Visium: https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01133.html. Rainer wrote and tested the attached patch on both Windows and Linux. Applied on the mai

Re: NetBSD has SSP in libc

On 01/26/2016 11:41 PM, Thomas Klausner wrote: On Tue, Jan 26, 2016 at 11:35:15PM -0700, Jeff Law wrote: On 01/23/2016 02:52 PM, Thomas Klausner wrote: NetBSD has SSP included in libc: http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/ssp/?only_with_tag=MAIN gcc/configure does not know about t

Re: [C/C++ PATCH] Don't emit invalid VEC_COND_EXPR for vector comparisons (PR c/68062)

On 01/27/2016 12:26 AM, Marek Polacek wrote: Ping. On Wed, Jan 20, 2016 at 12:31:51PM +0100, Marek Polacek wrote: On Wed, Jan 13, 2016 at 11:11:52PM +, Joseph Myers wrote: The C front-end changes are OK. Jason, is the C++ part of this patch here

Re: [PATCH] libcpp: use better locations for _Pragma tokens (preprocessor/69126)

On 01/17/2016 07:09 AM, David Malcolm wrote: Our code for handling the "_Pragma" builtin macro is implemented in libcpp/directives.c:destringize_and_run. It handles _Pragma by creating a one-line buffer containing the _Pragma content, then sending it to do_pragma, which tokenizes it and handles

Re: RFA: Fix ICE compiling gcc.dg/lto/pr55113_0.c for x86/x86_64

On 01/08/2016 02:00 PM, Bernd Schmidt wrote: On 01/08/2016 10:41 AM, Richard Biener wrote: On Tue, Dec 22, 2015 at 10:55 AM, Nick Clifton wrote: Richard Biener wrote: I think the option should be simply removed... Tempting - but we are in stage 3... My patch at least fixes the ICE for now.

Re: [PATCH] fix gimplification of call parameters (PR cilkplus/69267)

On 01/15/2016 03:41 PM, Ryan Burn wrote: 2016-01-15 Ryan Burn PR cilkplus/69267 * cilk.c (cilk_gimplify_call_params_in_spawned_fn): Change to use gimplify_arg. Removed superfluous post_p argument. * c-family.h (cilk_gimplify_call_params_in_spawned_fn): Remove

RE: [Patch,tree-optimization]: Add new path Splitting pass on tree ssa representation

-Original Message- From: Jeff Law [mailto:l...@redhat.com] Sent: Wednesday, January 27, 2016 12:48 PM To: Ajit Kumar Agarwal; Richard Biener Cc: GCC Patches; Vinod Kathail; Shail Aditya Gupta; Vidhumouli Hunsigida; Nagaraju Mekala Subject: Re: [Patch,tree-optimization]: Add new path Spl

Re: [PATCH, aarch64] Fix pr69305 -- addti miscompilation

On Sun, Jan 24, 2016 at 03:19:35AM -0800, Richard Henderson wrote: > As Jakub notes in the PR, the representation for add_compare and > sub_compare were wrong. And several of the add_carryin patterns > were duplicates. > > This adds a CC_Cmode for which only the Carry bit is valid. > > The patch

Re: Patch RFA: Add option -fcollectible-pointers, use it in ivopts

On Wed, Jan 27, 2016 at 7:24 AM, Bernd Schmidt wrote: > On 01/27/2016 04:18 PM, Ian Lance Taylor wrote: >> >> On Wed, Jan 27, 2016 at 7:16 AM, Bernd Schmidt >> wrote: >>> >>> >>> Still, I feel uncomfortable about making a promise we don't really expect >>> to >>> fully keep yet, so I would prefer

Re: [C/C++ PATCH] Don't emit invalid VEC_COND_EXPR for vector comparisons (PR c/68062)

On Wed, Jan 27, 2016 at 10:02:36AM -0700, Jeff Law wrote: > On 01/27/2016 12:26 AM, Marek Polacek wrote: > >Ping. > > > >On Wed, Jan 20, 2016 at 12:31:51PM +0100, Marek Polacek wrote: > >>On Wed, Jan 13, 2016 at 11:11:52PM +, Joseph Myers wrote: > >>>The C front-end changes are OK. > >> > >>Jas

[PATCH v3] PR48344: Fix unrecognizable insn error with -fstack-limit-register=r2

This patch has bootstrapped and tested on powerpc64le-unknown-linux-gnu with no regressions. Is this ok for the trunk? See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48344 for the original problem report. The error resulted because gcc's processing of command-line options within gcc initia

Re: [PATCH, aarch64] Fix pr69305 -- addti miscompilation

On 01/27/2016 09:31 AM, James Greenhalgh wrote: >> +(define_insn "*add3_compare1_cconly" > > I don't understand the naming scheme, it got me a wee bit confused with > add3_compare0 and friends, where the 0 indicates a comparison with > zero... Ah, well, I didn't get that 0 indicated comparison wi

Go patch committed: enable -fkeep-gc-roots-live for Go

This patch enables the new -fkeep-gc-roots-live option for Go. This fixes https://golang.org/issue/13662 . Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian 2016-01-27 Ian Lance Taylor * go-lang.c (go_langhook_init_options_struct): Default to -fkeep-gc-ro

[committed] Build sanitizer builtins in lto on demand (PR lto/69254)

Hi! On Tue, Jan 26, 2016 at 09:54:18PM +0100, Jakub Jelinek wrote: > On Tue, Jan 26, 2016 at 04:44:39PM +0100, Jakub Jelinek wrote: > > 2016-01-26 Jakub Jelinek > > > > PR lto/69254 > > * lto-opts.c (lto_write_options): Write also -f{,no-}sanitize= > > options. > > * lto-wrappe

Go patch committed: Accept map composite literals with omitted key types

In the Go 1.5 release, the language was changed slightly to permit omitting the type of a key in a composite literal of map type. This patch by Chris Manghane implements that in gccgo. This fixes https://golang.org/issue/10263 . Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committe

Re: [C PATCH] Fix -Wunused-function (PR debug/66869)

Hi! On Wed, Jan 27, 2016 at 11:17:18AM +0100, Richard Biener wrote: > No, simply warn and set TREE_NO_WARNING so cgraph doesn't warn again. This seems to work too, bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-01-25 Jakub Jelinek PR debug/66869 * c

[PATCH] Fix up a libstdc++ testsuite regression

Hi! I've noticed recent UNRESOLVED: libstdc++-prettyprinters/whatis.cc compilation failed to produce executable regression and I bet it is caused by the changes where it no longer includes . Tested on x86_64-linux, ok for trunk? 2016-01-27 Jakub Jelinek * testsuite/libstdc++-pretty

[P2][PR tree-optimization/68398] Refine when we allow the FSM threader to create irreducible inner loops

Right now we only allow the FSM threader to create an irreducible inner loop when it's able to eliminate a multiway branch. The theory being that the multiway branch is very expensive and potentially outweighs the value of loop optimizations. That was a fine start, but as seen in 68398, fur

[PATCH] Don't change stack_alignment_needed for __tls_get_addr

__tls_get_addr must be called with 16-byte aligned stack, which is guaranted by setting preferred_stack_boundary to 128 bits. There is no need to change stack_alignment_needed for __tls_get_addr. Tested on x86-64. OK for trunk? H.J. -- PR target/68986 * config/i386/i386.c (ix86

Re: [PATCH] Fix up a libstdc++ testsuite regression

On 01/27/2016 11:54 AM, Jakub Jelinek wrote: Hi! I've noticed recent UNRESOLVED: libstdc++-prettyprinters/whatis.cc compilation failed to produce executable regression and I bet it is caused by the changes where it no longer includes . Tested on x86_64-linux, ok for trunk? 2016-01-27 Jakub

Re: [C PATCH] Fix -Wunused-function (PR debug/66869)

On 01/27/2016 11:51 AM, Jakub Jelinek wrote: Hi! On Wed, Jan 27, 2016 at 11:17:18AM +0100, Richard Biener wrote: No, simply warn and set TREE_NO_WARNING so cgraph doesn't warn again. This seems to work too, bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-01-25 Jaku

Re: [PATCH 1/4] Make SRA scalarize constant-pool loads

The new sra-17.c and sra-18.c tests fail on AIX because the regex is too restrictive -- AIX labels don't have exactly the same format. On AIX, the labels in the dumps look like "LC..0" instead of ".LC0". This patch adds "*" and ".*" so that the "." prepended to LC is optional and to allow charact

Re: [P2][PR tree-optimization/68398] Refine when we allow the FSM threader to create irreducible inner loops

On January 27, 2016 8:20:47 PM GMT+01:00, Jeff Law wrote: > >This also fixes 3 minor issues Bernd spotted in the last round of >changes. Bernhard, not Bernd i suppose. Note that the !is_gimple_debug (stmt) should now be redundant in the hunk below. Thanks, @@ -280,33 +280,19 @@ fsm_find_contro

[PATCH, i386]: Fix PR69512: ICE when using avx with i586 (edit)

Hello! -march=i586 activates TARGET_ZERO_EXTEND_WITH_AND, which disables movz instructions. These targets have to use and instructions, and when flags are not allowed to be clobbered a sequence of register clear + movstrict. 2016-01-27 Uros Bizjak PR target/69512 * config/i386/i386.md

Re: [P2][PR tree-optimization/68398] Refine when we allow the FSM threader to create irreducible inner loops

On 01/27/2016 12:39 PM, Bernhard Reutner-Fischer wrote: On January 27, 2016 8:20:47 PM GMT+01:00, Jeff Law wrote: This also fixes 3 minor issues Bernd spotted in the last round of changes. Bernhard, not Bernd i suppose. Note that the !is_gimple_debug (stmt) should now be redundant in the h

Re: [PATCH] Don't change stack_alignment_needed for __tls_get_addr

On Wed, Jan 27, 2016 at 8:25 PM, H.J. Lu wrote: > > __tls_get_addr must be called with 16-byte aligned stack, which is > guaranted by setting preferred_stack_boundary to 128 bits. There > is no need to change stack_alignment_needed for __tls_get_addr. > > Tested on x86-64. OK for trunk? You kno

Re: new port: vn8

On Jan 26, 2016, at 10:33 PM, Nguyễn Sinh Ngọc wrote: > I wonder that what paper is? > Is it an introduction about new feature in our target? I was not able to make any sense of these two question. Likely a language barrier. If you can find a way to rephrase them… I can try and answer.

Re: [P2][PR tree-optimization/68398] Refine when we allow the FSM threader to create irreducible inner loops

On Wed, Jan 27, 2016 at 12:48:31PM -0700, Jeff Law wrote: > On 01/27/2016 12:39 PM, Bernhard Reutner-Fischer wrote: > >On January 27, 2016 8:20:47 PM GMT+01:00, Jeff Law wrote: > > > >> > >>This also fixes 3 minor issues Bernd spotted in the last round of > >>changes. > > > >Bernhard, not Bernd i

Re: [PATCH, testsuite] Fix g++.dg/pr67989.C test failure when running with -march or -mcpu

On Jan 26, 2016, at 10:35 PM, Thomas Preud'homme wrote: > On Monday, January 18, 2016 11:33:47 AM Thomas Preud'homme wrote: >> On Wednesday, January 13, 2016 06:39:20 PM Bernd Schmidt wrote: >>> On 01/12/2016 08:55 AM, Thomas Preud'homme wrote: On Monday, January 11, 2016 04:57:18 PM Bernd S

Re: [PATCH, testsuite]: Disable some tests in gcc.dg/torture/pr68264.c for older glibcs

On Jan 27, 2016, at 12:58 AM, Uros Bizjak wrote: > 2016-01-27 Uros Bizjak > >* gcc.dg/torture/pr68264.c: Disable log1p test for glibc < 2.22 >and expm1 test for glibc < 2.11. > > Tested on x86_64-linux-gnu, CentOS 5.11 and Fedora 23. > > OK for mainline? So, unless we have a glibc s

RFA: patch to fix PR69299

The following patch fixes PR69299. The details of the problem is described on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69299 The patch was successfully bootstrapped and tested on x86/x86-64. The patch introduces a new type of constraints define_special_memory_constraint for memory

Re: C++ PATCH for c++/69496 (ICE on VLA in constexpr function)

On 01/27/2016 11:52 AM, Martin Sebor wrote: I agree that there is some risk that it might break some working programs. I would expect the most common use of initialized VLAs be to set all elements to zero using the "= { }" or "= { 0 }" syntax. Initializers with more elements are, IMO, likely to

Re: Is it OK for rtx_addr_can_trap_p_1 to attempt to compute the frame layout? (was Re: [PATCH] Skip re-computing the mips frame info after reload completed)

On 26.01.2016 22:18, Richard Sandiford wrote: > [cc-ing Eric as RTL maintainer] > > Matthew Fortune writes: >> Bernd Edlinger writes: >>> Matthew Fortune writes: Has the patch been tested beyond just building GCC? I can do a test run for you if you don't have things set up to do one yo

Re: [PATCH] Low-hanging C++-lexer speedup (PR c++/24208)

On 01/25/2016 11:45 PM, Patrick Palka wrote: +/* This needs to be set to TRUE before the lexer-debugging infrastructure can + be used. The point of this flag is to help the compiler to fold away calls + to cp_lexer_debugging_p within this source file at compile time, when the + lexer is no

Re: [Patch AArch64] Restrict 16-bit sqrdml{sa}h instructions to FP_LO_REGS

On 01/26/16 10:04, James Greenhalgh wrote: Hi, In their forms using 16-bit lanes, the sqrdmlah and sqrdmlsh instruction available when compiling with -march=armv8.1-a are only usable with a register number in the range 0 to 15 for operand 3, as gas will point out: Error: register number out

RE: [PATCH] MIPS: Prevent the p5600-bonding.c test from being run for the n32 and 64 ABIs

> -Original Message- > From: Andrew Bennett [mailto:andrew.benn...@imgtec.com] > Sent: Wednesday, January 20, 2016 9:42 AM > To: Matthew Fortune; gcc-patches@gcc.gnu.org > Cc: Moore, Catherine > Subject: RE: [PATCH] MIPS: Prevent the p5600-bonding.c test from being run > for the n32 and 6

[lra, committed] Fix PR 69447

This PR appears to be related to PR 66424, which Vlad fixed back in September, but different in that the insn being rematerialized used the entire DImode pseudo instead of an SImode subreg of a DImode pseudo. The effect was the same, however, in that it lengthened the lifetime of one half of the d

Re: [PATCH] Low-hanging C++-lexer speedup (PR c++/24208)

On Wed, Jan 27, 2016 at 4:33 PM, Jason Merrill wrote: > On 01/25/2016 11:45 PM, Patrick Palka wrote: >> >> +/* This needs to be set to TRUE before the lexer-debugging infrastructure >> can >> + be used. The point of this flag is to help the compiler to fold away >> calls >> + to cp_lexer_debu

[PATCH] add test for target/17381 - Unnecessary register move for float extend

The attached patch adds a test for the apparently long fixed bug. FWIW, I've been trying to close out some of these old bugs and while it doesn't seem to be done consistently, it occurs to me that it might be nice to add tests for them. Please let me know if you don't think it's worth the troubl

[Patch, Fortran, committed] PR 69484: [5/6 Regression] documentation issue: -Wtabs and -Wall

Hi all, I have just committed a rather obvious documentation fix to trunk: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=232906 I'll also backport this to the gcc-5 branch soonish ... Cheers, Janus

Another suspicious code hunk in c-family/c-common.c

another chock with the static type code in c-family/c-common:handle_deprecated_attribute() around line 8919-8923 handle_deprecated_attribute (tree *node, tree name, tree args, int flags, bool *no_add_attrs) { <...> if (DECL_P (*node))

[PATCH, rs6000] Disable static branch prediction in absence of real profile data

The following patch prevents static prediction if we don't have real profile data. Testing on SPEC CPU2006 showed a couple improvements in specint and specfp neutral. Bootstrap/regtest on powerpc64 with no new regressions. Ok for trunk? -Pat 2016-01-27 Pat Haugen * config/rs6000/

Re: [PATCH][AArch64] Replace insn to zero up DF register

On 01/22/16 07:52, Wilco Dijkstra wrote: On 12/16/2015 03:30 PM, Evandro Menezes wrote: On 10/30/2015 05:24 AM, Marcus Shawcroft wrote: On 20 October 2015 at 00:40, Evandro Menezes wrote: In the existing targets, it seems that it's always faster to zero up a DF

Re: [Patch, fortran, GCC-5/6, PR62536, v1] ICE (segfault) for invalid END BLOCK statement

On 01/27/2016 08:25 AM, Andre Vehreschild wrote: > Hi all, > > attached are two patches one for trunk and one for the gcc-5-branch, > which fix an ICE when BLOCK statements are not closed correctly (too > many END BLOCKs). Unfortunately did the patch I tailored for gcc-5 not > work on trunk. > >

Re: Another suspicious code hunk in c-family/c-common.c

On 01/27/2016 03:41 PM, Andrew MacLeod wrote: another chock with the static type code in c-family/c-common:handle_deprecated_attribute() around line 8919-8923 handle_deprecated_attribute (tree *node, tree name, tree args, int flags,

Re: [PATCH] add test for target/17381 - Unnecessary register move for float extend

On 01/27/2016 03:38 PM, Martin Sebor wrote: The attached patch adds a test for the apparently long fixed bug. FWIW, I've been trying to close out some of these old bugs and while it doesn't seem to be done consistently, it occurs to me that it might be nice to add tests for them. Please let me

Re: [PATCH 1/4] Make SRA scalarize constant-pool loads

On 01/27/2016 12:39 PM, David Edelsohn wrote: The new sra-17.c and sra-18.c tests fail on AIX because the regex is too restrictive -- AIX labels don't have exactly the same format. On AIX, the labels in the dumps look like "LC..0" instead of ".LC0". This patch adds "*" and ".*" so that the "."

Re: Is it OK for rtx_addr_can_trap_p_1 to attempt to compute the frame layout? (was Re: [PATCH] Skip re-computing the mips frame info after reload completed)

> [cc-ing Eric as RTL maintainer] Sorry for the delay, the message apparently bounced] > IMO the problem is that rtx_addr_can_trap_p_1 duplicates a large > bit of LRA/reload logic: > > [...] > > Under the current interface macros like INITIAL_ELIMINATION_OFFSET > are expected to trigger the cal

Re: [PATCH 1/4] Make SRA scalarize constant-pool loads

On Wed, Jan 27, 2016 at 6:36 PM, Jeff Law wrote: > On 01/27/2016 12:39 PM, David Edelsohn wrote: >> >> The new sra-17.c and sra-18.c tests fail on AIX because the regex is >> too restrictive -- AIX labels don't have exactly the same format. On >> AIX, the labels in the dumps look like "LC..0" ins

  1   2   >