Re: [gomp4, PR68977, Committed] Don't gimplify in ssa mode if seen_error in oacc_xform_loop

On Thu, Jan 28, 2016 at 6:49 PM, Tom de Vries wrote: > On 28/01/16 14:32, Richard Biener wrote: >> >> On Mon, Jan 25, 2016 at 12:00 PM, Tom de Vries >> wrote: >>> >>> On 14/01/16 10:43, Richard Biener wrote: On Wed, Jan 13, 2016 at 9:04 PM, Tom de Vries wrote: > > >>>

Re: [PATCH] Use vm in sse2_cvtps2pd

On Fri, Jan 29, 2016 at 5:01 AM, H.J. Lu wrote: > sse2_cvtps2pd has > > (define_insn "sse2_cvtps2pd" > [(set (match_operand:V2DF 0 "register_operand" "=v") > (float_extend:V2DF > (vec_select:V2SF > (match_operand:V4SF 1 "vector_operand" "vBm") > (paralle

[gomp4] Merge trunk r232931 (2016-01-28) into gomp-4_0-branch

Hi! Committed to gomp-4_0-branch in r232967: commit 5999e6842d3f9cecc5cb500ebf692f54158e8017 Merge: 9cfa5d5 b547a9b Author: tschwinge Date: Fri Jan 29 06:46:35 2016 + svn merge -r 232548:232931 svn+ssh://gcc.gnu.org/svn/gcc/trunk git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc

[PATCH] Use vm in sse2_cvtps2pd

sse2_cvtps2pd has (define_insn "sse2_cvtps2pd" [(set (match_operand:V2DF 0 "register_operand" "=v") (float_extend:V2DF (vec_select:V2SF (match_operand:V4SF 1 "vector_operand" "vBm") (parallel [(const_int 0) (const_int 1)]] The memory operand size

Re: C++ PATCH for c++/69509 and c++/69516 (infinite recursion with invalid VLAs in constexpr functions)

On 01/28/2016 01:33 PM, Marek Polacek wrote: This patch fixes some problems with VLAs and constexprs. (The runtime aspect of this matter is being tracked in PR69517.) It does two things: 1) Changes build_vec_init slightly to prevent the compiler from getting into infinite recursion. Curre

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

On 01/28/2016 03:27 PM, Marek Polacek wrote: On Wed, Jan 27, 2016 at 09:52:13AM -0700, Martin Sebor wrote: This happens to work but I suspect it's only by accident. When the number of elements in the initializer is increased to exceed the number of elements in the VLA GCC gets into infinite rec

Re: [PATCH] target/68972 - g++.dg/cpp1y/vla-initlist1.C test case fails on powerpc64le

Other than that, I did notice one thing that doesn't look right. There's an empty loop for the no-op initializer_list ctor to initialize the rest of the array. I should open a bug for that. But that's not a unique to the powerpc64 back end. The x86_64 code has the same empty loop. I raised bug

Re: [PATCH] target/68972 - g++.dg/cpp1y/vla-initlist1.C test case fails on powerpc64le

On 01/28/2016 03:53 PM, Jason Merrill wrote: On 01/28/2016 02:48 PM, Martin Sebor wrote: The g++.dg/cpp1y/vla-initlist1.C test relies on undefined behavior (reading an uninitialized array element) to verify that two VLAs are allocated in memory starting at the same address. The test has been se

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 01/28/2016 12:36 AM, Eric Botcazou wrote: [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_OFFSE

Re: [C++ patch] report better diagnostic for static following '[' in parameter declaration

On Fri, Jan 29, 2016 at 04:46:56AM +0530, Prathamesh Kulkarni wrote: > @@ -19016,10 +19017,22 @@ cp_parser_direct_declarator (cp_parser* parser, > cp_lexer_consume_token (parser->lexer); > /* Peek at the next token. */ > token = cp_lexer_peek_token (parser->lexer); > + > +

[C++ patch] report better diagnostic for static following '[' in parameter declaration

Hi, For the test-case, void f(int a[static 10]); g++ gives following errors: test-foo.cpp:1:14: error: expected primary-expression before ‘static’ void f(int a[static 10]); ^ test-foo.cpp:1:14: error: expected ‘]’ before ‘static’ test-foo.cpp:1:14: error: expected ‘)’ before ‘static

Re: C++ PATCH for c++/69509 and c++/69516 (infinite recursion with invalid VLAs in constexpr functions)

On Thu, Jan 28, 2016 at 05:51:30PM -0500, Jason Merrill wrote: > OK. I suppose we should also catch the out-of-bounds store in > cxx_eval_store_expression... Thanks, I'll look into that as a follow-up. Marek

Re: [google gcc-4_9]: Backport trunk:r232727 fix for PR/69403.

LGTM thanks Carrot On Thu, Jan 28, 2016 at 11:53 AM, Han Shen wrote: > Backport trunk:r232727 fix for PR/69403 - wrong > thumb2_ior_scc_strict_it insn pattern. > > Note this only affect armv7-a tuned for armv8 arch, tested / booted > affected ChromeOS book. > > Ok for google/gcc-4_9 branch? > >

Re: [PATCH] target/68972 - g++.dg/cpp1y/vla-initlist1.C test case fails on powerpc64le

On 01/28/2016 02:48 PM, Martin Sebor wrote: The g++.dg/cpp1y/vla-initlist1.C test relies on undefined behavior (reading an uninitialized array element) to verify that two VLAs are allocated in memory starting at the same address. The test has been seen to fail on powerpc64-*-linux-gnu and spu-*-

Re: C++ PATCH for c++/69509 and c++/69516 (infinite recursion with invalid VLAs in constexpr functions)

OK. I suppose we should also catch the out-of-bounds store in cxx_eval_store_expression... Jason

[PATCH, i386]: Fix PR69549, wrong code with -O2 and vector arithmetics @ x86_64

Hello! Attached patch corrects "C" constraint to accept only SSE constant zero operand and introduces new "BC" constraint to accept all SSE constant operands (all bits 0 and all bits 1). As discussed in the PR, the compiler ICEs when "C" constraint is used non-zero vector operands, so it is still

[PATCH, rs6000] Fix PR65546

Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65546 identifies a failure in gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c. The test case hasn't kept up with changes in the vectorizer, so it's looking for the wrong error message. Also, the error message should be conditioned by a check for su

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

On Wed, Jan 27, 2016 at 09:52:13AM -0700, Martin Sebor wrote: > This happens to work but I suspect it's only by accident. When > the number of elements in the initializer is increased to exceed > the number of elements in the VLA GCC gets into infinite recursion. > (I opened bug 69516 with a test

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)

Bernd Edlinger writes: > 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'

Re: [PATCH] Fix PCH on systems where stdc-predef.h includes other headers (PR pch/68176)

On Thu, Jan 28, 2016 at 03:32:39PM +0100, Jakub Jelinek wrote: > Hi! > > As mentioned in the PR, most of the pch tests fail if stdc-predef.h header > includes other headers. I don't have such a system, but changed my > stdc-predef.h to include a dummy header bits/predef.h and this patch fixes > a

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

On Thu, 2016-01-28 at 14:59 -0500, David Malcolm wrote: > On Thu, 2016-01-28 at 14:48 -0500, David Malcolm wrote: > > On Thu, 2016-01-28 at 11:12 -0800, Steve Ellcey wrote: > > > David, > > > > > > This patch has broken the top-of-tree glibc build > > > > Bother; sorry. FWIW, I'm about to get on

Re: [PATCH 1/3] [graphite] assert instead of silently failing code gen

On Thu, Jan 28, 2016 at 8:24 AM, Sebastian Pop wrote: > * graphite-isl-ast-to-gimple.c (get_rename_from_scev): Assert instead > of > setting codegen_error to fail codegen. This may have caused: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69545 -- H.J.

Re: [PATCH] Fix bootstrap on i686 (PR middle-end/69542)

On 01/28/2016 12:17 PM, Jakub Jelinek wrote: > The recent lra-remat.c change broke bootstrap for me on i686, > with comparison failure on simplify-rtx.o. > Below is a reduced testcase. debug insns really should not affect > remat decisions, before the recent changes set_bb_regs should be always a

Re: [PATCH] New flag for dumping information about constexpr function calls memoization (GCC 5.2.0)

Any patch adding a new option needs to add documentation for it to invoke.texi (both substantive documentation, and inclusion in the summary lists of options). -- Joseph S. Myers jos...@codesourcery.com

C++ PATCH for c++/69509 and c++/69516 (infinite recursion with invalid VLAs in constexpr functions)

This patch fixes some problems with VLAs and constexprs. (The runtime aspect of this matter is being tracked in PR69517.) It does two things: 1) Changes build_vec_init slightly to prevent the compiler from getting into infinite recursion. Currently, we emit the following sequence when we're

[PATCH] New flag for dumping information about constexpr function calls memoization (GCC 5.2.0)

Hi, This patch adds a flag (-fdump-memoization-hits) in order to dump information about wich constexpr functions calls are memoized. This is patch is for gcc-5.2.0. If OK, please commit it for me since I don't have write access. patch: diff --git a/gcc/common.opt b/gcc/common.opt index 1218a71..

[PATCH] Fix bootstrap on i686 (PR middle-end/69542)

Hi! The recent lra-remat.c change broke bootstrap for me on i686, with comparison failure on simplify-rtx.o. Below is a reduced testcase. debug insns really should not affect remat decisions, before the recent changes set_bb_regs should be always a nop on debug insns (they don't change any regist

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

On Wed, Jan 27, 2016 at 12:28:58PM -0700, Jeff Law wrote: > On 01/27/2016 11:51 AM, Jakub Jelinek wrote: > >2016-01-25 Jakub Jelinek > > > > PR debug/66869 > > * c-decl.c (c_write_global_declarations_1): Warn with > > warn_unused_function if static prototype without definition > >

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

On Thu, 2016-01-28 at 14:48 -0500, David Malcolm wrote: > On Thu, 2016-01-28 at 11:12 -0800, Steve Ellcey wrote: > > David, > > > > This patch has broken the top-of-tree glibc build > > Bother; sorry. FWIW, I'm about to get on a plane (for FOSDEM), so > I'm > not in a great position to tackle th

[google gcc-4_9]: Backport trunk:r232727 fix for PR/69403.

Backport trunk:r232727 fix for PR/69403 - wrong thumb2_ior_scc_strict_it insn pattern. Note this only affect armv7-a tuned for armv8 arch, tested / booted affected ChromeOS book. Ok for google/gcc-4_9 branch? -- Han Shen Index: gcc/ChangeLog =

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

On Thu, 2016-01-28 at 11:12 -0800, Steve Ellcey wrote: > David, > > This patch has broken the top-of-tree glibc build Bother; sorry. FWIW, I'm about to get on a plane (for FOSDEM), so I'm not in a great position to tackle this yet. > I get an error on an > undef that is supposed to be protected

[PATCH] target/68972 - g++.dg/cpp1y/vla-initlist1.C test case fails on powerpc64le

The g++.dg/cpp1y/vla-initlist1.C test relies on undefined behavior (reading an uninitialized array element) to verify that two VLAs are allocated in memory starting at the same address. The test has been seen to fail on powerpc64-*-linux-gnu and spu-*-elf. The attached patch removes the undefined

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

On Thu, Jan 28, 2016 at 04:47:04AM -0800, H.J. Lu wrote: > I got > > FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for > warnings, line 17) > FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for > warnings, line 18) > FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (

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

David, This patch has broken the top-of-tree glibc build. I get an error on an undef that is supposed to be protected by Pragmas. It happens when compiling intl/plural.c in glibc. I created a preprocessed source file but when I compile it, the error doesn't happen. I will try to create a small

Re: [PATCH] Fix use of declare'd vars by routine procedures.

Jakub, On 01/22/2016 04:39 AM, Jakub Jelinek wrote: As for the extra error, I think it would be better to diagnose this during gimplification, that way you do it for all FEs, plus you have the omp context in there, etc. The error wording is weird, the diagnostic should make it clear use of wha

Re: [PATCH] [graphite] make debug comment more explicit

On Thu, Jan 28, 2016 at 8:32 AM, Sebastian Pop wrote: > 2016-01-28 Abderrazek Zaafrani > > * graphite-optimize-isl.c (optimize_isl): Print a different debug > message when isl does not return a valid schedule. > --- > gcc/graphite-optimize-isl.c | 11 +-- > 1 file chang

Re: [PATCH, rs6000] Partial fix for PR65546 (GCC 6)

Actually, please hold off on this. The test in general is just faulty. I'll get something more complete later on. Sorry for the noise, Bill On Thu, 2016-01-28 at 11:45 -0600, Bill Schmidt wrote: > Hi, > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65546 discusses the failure > of gcc.dg/vect/

Re: [PATCH, gcc7, aarch64] Add arithmetic overflow patterns

On 01/28/2016 01:50 AM, Michael Collison wrote: > Hi Richard, > > Note that this patch appears to depend on your previous patch: > > https://gcc.gnu.org/ml/gcc-patches/2016-01/txtDPaXOBMuOB.txt > > for the definition of define_mode_attr DWI. I was looking at this patch as I > was working on Bugz

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

Here's the patch as committed. It includes a few name changes from the addv patch I posted, which correspond nicely with a name clarification that James requested during feedback. r~ PR target/69305 * config/aarch64/aarch64-modes.def (CC_Cmode): New * config/aarch64/aarch

Re: [gomp4, PR68977, Committed] Don't gimplify in ssa mode if seen_error in oacc_xform_loop

On 28/01/16 14:32, Richard Biener wrote: On Mon, Jan 25, 2016 at 12:00 PM, Tom de Vries wrote: On 14/01/16 10:43, Richard Biener wrote: On Wed, Jan 13, 2016 at 9:04 PM, Tom de Vries wrote: Hi, At r231739, there was an ICE when checking code generated by oacc_xform_loop, in case the source

[PATCH, rs6000] Partial fix for PR65546 (GCC 6)

Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65546 discusses the failure of gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c. The test fails differently on GCC 4.9 and 5 than it does on GCC 6. For GCC 6, the test case is faulty, as we only expect to see the "vectorization not profitable" state

Re: RFA: patch to fix PR69299

On 01/28/2016 08:05 AM, Jakub Jelinek wrote: On Wed, Jan 27, 2016 at 04:01:23PM -0500, Vladimir Makarov wrote: 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

Re: new port: vn8

On Wed, 27 Jan 2016, Sandra Loosemore wrote: > On 01/27/2016 08:47 PM, Nguyễn Sinh Ngọc wrote: > > > Where is the patch under discussion here? I can't find it in the > > > archives. > > > > This is the source code of VN8 target: > > https://drive.google.com/file/d/0B169XTHeyQCfb2ZVak5VRm4tcHc/vi

[PATCH] [graphite] make debug comment more explicit

2016-01-28 Abderrazek Zaafrani * graphite-optimize-isl.c (optimize_isl): Print a different debug message when isl does not return a valid schedule. --- gcc/graphite-optimize-isl.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/gcc/graphite-optim

RE: [Patch, MIPS] Patch for PR 68400, a mips16 bug

> -Original Message- > From: Steve Ellcey [mailto:sell...@imgtec.com] > Sent: Tuesday, January 26, 2016 3:43 PM > To: gcc-patches@gcc.gnu.org > Cc: matthew.fort...@imgtec.com; Moore, Catherine > Subject: [Patch, MIPS] Patch for PR 68400, a mips16 bug > > Here is a patch for PR6400. The

[PATCH 2/3] [graphite] use codegen_error_p

* graphite-isl-ast-to-gimple.c (binary_op_to_tree): Call codegen_error_p. (ternary_op_to_tree): Same. (unary_op_to_tree): Same. (nary_op_to_tree): Same. (gcc_expression_from_isl_expr_op): Same. (gcc_expression_from_isl_expression): Same. (gra

[PATCH 3/3] [graphite] remove out of sync comments

* graphite-isl-ast-to-gimple.c (class translate_isl_ast_to_gimple): Remove comments from class declarations: they are already in the code close by the defs. --- gcc/graphite-isl-ast-to-gimple.c | 437 --- 1 file changed, 83 insertions(+),

[PATCH 1/3] [graphite] assert instead of silently failing code gen

* graphite-isl-ast-to-gimple.c (get_rename_from_scev): Assert instead of setting codegen_error to fail codegen. --- gcc/graphite-isl-ast-to-gimple.c | 26 ++ 1 file changed, 6 insertions(+), 20 deletions(-) diff --git a/gcc/graphite-isl-ast-to-gimple.c b/gc

Re: RFA (tree.h): C++ PATCH for c++/67407 (ICE with protected access)

On 01/28/2016 10:09 AM, Jakub Jelinek wrote: On Thu, Jan 28, 2016 at 10:03:59AM -0500, Jason Merrill wrote: In this testcase, the problem was that we were checking DERIVED_FROM_P, which uses dfs_walk_once and thus BINFO_MARKED, in the middle of a dfs_walk_once_accessible, which also uses BINFO_M

Re: [PATCH] Fix cp_binding_level reuse logic

On 01/27/2016 07:44 PM, Patrick Palka wrote: In begin_scope(), we are accidentally clearing the entire free_binding_level store whenever we reuse a single GC-alloced cp_binding_level structure from it. This happens because we erroneously update free_binding_level _after_ the pointer pointing to

Default compute dimensions

This patch adds default compute dimension handling. Users rarely specify compute dimensions, expecting the toolchain to DTRT. More savvy users would like to specify global defaults. This patch permits both. While the vector and worker dimensions are constrained by the target CPU implementat

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

Hi Martin, On Wed, 27 Jan 2016, Martin Jambor wrote: > So what would you think about the following? Perhaps it is too > verbose but I wanted to mention the few areas users should know > have changed, if they happen to try HSA out. I can certainly > cut it down a bit. I like this. In fact, in

RFA (tree.h): C++ PATCH for c++/67407 (ICE with protected access)

In this testcase, the problem was that we were checking DERIVED_FROM_P, which uses dfs_walk_once and thus BINFO_MARKED, in the middle of a dfs_walk_once_accessible, which also uses BINFO_MARKED, and the marks from one walk were confusing the other walk. Fixed by moving these binfo walking func

Re: [wwwdocs] Convert gcc-4.9/porting_to.html to using gcc.css (instead of individual style= clauses)

On Sun, 24 Jan 2016, Gerald Pfeifer wrote: > With this, like similar pages, we now have the colors back. A friendly sole pointed out a mistake I had made in this conversation. Fixed thusly. Gerald Index: gcc-4.9/porting_to.html ===

Re: RFA (tree.h): C++ PATCH for c++/67407 (ICE with protected access)

On Thu, Jan 28, 2016 at 10:03:59AM -0500, Jason Merrill wrote: > In this testcase, the problem was that we were checking DERIVED_FROM_P, > which uses dfs_walk_once and thus BINFO_MARKED, in the middle of a > dfs_walk_once_accessible, which also uses BINFO_MARKED, and the marks from > one walk were

Re: [PATCH] PR c++/69462: Provide FLT_EVAL_METHOD and DECIMAL_DIG in float.h.

On Thu, Jan 28, 2016 at 01:40:12PM +0100, Dominik Vogt wrote: > PR c++/69462 > * ginclude/float.h: Also provide FLT_EVAL_METHOD and DECIMAL_DIG for > C++-11. > >From 3b74be3a03105d608609f35b33bcf2ba43c0b5b9 Mon Sep 17 00:00:00 2001 > From: Dominik Vogt > Date: Mon, 25 Jan 2016 1

Re: [PATCH] PR c++/69462: Provide FLT_EVAL_METHOD and DECIMAL_DIG in float.h.

On Thu, Jan 28, 2016 at 01:32:18PM +, Jonathan Wakely wrote: > On 28/01/16 13:40 +0100, Dominik Vogt wrote: > >The attached patch (written by Jonathan, not me) makes > >FLT_EVAL_METHOD and DECIMAL_DIG available in C++-11 as they should > >be. > > > >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=

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

On Sun, Jan 17, 2016 at 09:09:53AM -0500, David Malcolm wrote: > libcpp/ChangeLog: > PR preprocessor/69126 > * directives.c (destringize_and_run): Add expansion_loc param; use > it when handling unexpanded pragmas to fixup the locations of the > synthesized tokens. This cha

Re: [PATCH 4/4][AArch64] Cost CCMP instruction sequences to choose better expand order

On Mon, Jan 25, 2016 at 08:09:39PM +, Wilco Dijkstra wrote: > Andreas Schwab wrote: > > > FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler-times \tcmp\tw[0-9]+, 0 4 > > FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler adds\t > > FAIL: gcc.target/aarch64/ccmp_1.c scan-assembler-times fccmpe\t.

[PATCH] Fix PCH on systems where stdc-predef.h includes other headers (PR pch/68176)

Hi! As mentioned in the PR, most of the pch tests fail if stdc-predef.h header includes other headers. I don't have such a system, but changed my stdc-predef.h to include a dummy header bits/predef.h and this patch fixes all the tests that failed because of that. AFAIK file->implicit_preinclude f

Re: [PATCH PR68542]

On Thu, Jan 28, 2016 at 2:37 PM, Yuri Rumyantsev wrote: > Thanks Richard. > > Uros, > > Could you please review back-end part of this patch? No problem, but please in future CC me on the x86 patches, so I won't forgot. +(define_expand "cbranch4" + [(set (reg:CC FLAGS_REG) +(compare:CC (matc

[PATCH] Fix PR69537

I am fixing the missed optimization / bogus warning with relaxing the guard around "old" fold_{widened,sing_changing}_comparison which is now in match.pd. Bootstrap and regtest running on x86_64-unknown-linux-gnu. I'm curious if any issues with casts-to-BOOLEAN_TYPE show up in our testsuite (and

Re: [PATCH PR68542]

Thanks Richard. Uros, Could you please review back-end part of this patch? Thanks. Yuri. 2016-01-28 16:26 GMT+03:00 Richard Biener : > On Fri, Jan 22, 2016 at 3:29 PM, Yuri Rumyantsev wrote: >> Richard, >> >> I fixed all remarks pointed by you in vectorizer part of patch. Could >> you take a l

Re: [gomp4, PR68977, Committed] Don't gimplify in ssa mode if seen_error in oacc_xform_loop

On Mon, Jan 25, 2016 at 12:00 PM, Tom de Vries wrote: > On 14/01/16 10:43, Richard Biener wrote: >> >> On Wed, Jan 13, 2016 at 9:04 PM, Tom de Vries >> wrote: >>> >>> Hi, >>> >>> At r231739, there was an ICE when checking code generated by >>> oacc_xform_loop, in case the source contained an erro

Re: [PATCH] PR c++/69462: Provide FLT_EVAL_METHOD and DECIMAL_DIG in float.h.

On 28/01/16 13:40 +0100, Dominik Vogt wrote: The attached patch (written by Jonathan, not me) makes FLT_EVAL_METHOD and DECIMAL_DIG available in C++-11 as they should be. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69462 Can this be committed (should it wait for stage1)? I've just noticed we

Re: [PATCH PR68542]

On Fri, Jan 22, 2016 at 3:29 PM, Yuri Rumyantsev wrote: > Richard, > > I fixed all remarks pointed by you in vectorizer part of patch. Could > you take a look on modified patch. + if (is_gimple_call (stmt1)) + lhs = gimple_call_lhs (stmt1); + else +

Re: [wwwdocs] gcc-6/changes.html: diagnostics, Levenshtein, -Wmisleading-indentation, jit (v2)

On Thu, Jan 28, 2016 at 02:19:09PM +0100, Markus Trippelsdorf wrote: > > Move the boldred class from gcc-6/changes.html to gcc.css. > > Introduce boldcyan and boldmagenta classes and use them in > > gcc-6/changes.html. > > > > Index: gcc.css > >

Re: [wwwdocs] gcc-6/changes.html: diagnostics, Levenshtein, -Wmisleading-indentation, jit (v2)

On 2016.01.20 at 18:38 +0100, Gerald Pfeifer wrote: > On Wed, 20 Jan 2016, Jakub Jelinek wrote: > >> Content-Security-Policy: default-src 'self' http: https: > >> > >> So either we get the configuration of the web server changed, or > >> indeed we need to touch all those existing pages. > > At l

Re: RFA: patch to fix PR69299

On Wed, Jan 27, 2016 at 04:01:23PM -0500, Vladimir Makarov wrote: > 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 patc

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

On Wed, Jan 27, 2016 at 9:45 AM, Marek Polacek wrote: > 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

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

On Thu, Jan 28, 2016 at 2:06 AM, Ilya Enkovich wrote: > 2016-01-28 9:00 GMT+03:00 H.J. Lu : >> On Wed, Jan 27, 2016 at 8:36 AM, H.J. Lu wrote: >>> 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 Enko

[PATCH] PR c++/69462: Provide FLT_EVAL_METHOD and DECIMAL_DIG in float.h.

The attached patch (written by Jonathan, not me) makes FLT_EVAL_METHOD and DECIMAL_DIG available in C++-11 as they should be. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69462 Can this be committed (should it wait for stage1)? Ciao Dominik ^_^ ^_^ -- Dominik Vogt IBM Germany gcc/ChangeLog

[Ada] Rename enumeration type

PR bootstrap/69513 incidentally reports a -Wodr warning during LTO bootstrap: ../../../../../../../opt/devel/gnu/src/gcc/gcc-6.0.0-test/gcc/ada/gcc- interface/gigi.h:345:6: warning: type ‘attr_type’ violates the C++ One Definition Rule [-Wodr] enum attr_type ^ ./insn-attr-common.h:8:0: not

Partial Offloading (was: [hsa merge 07/10] IPA-HSA pass)

Hi! > [...] I made an attempt to capture the recent discussion (plus my own ideas/understanding) in this new section: . Please change/extend, as required. Grüße Thomas signature.asc Description: PGP signature

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

Hi Jerry, hi all, thanks for the fast review. Committed as r232918 for gcc-5-branch, and r232919 for trunk. Thanks again Jerry and regards, Andre On Wed, 27 Jan 2016 15:19:32 -0800 Jerry DeLisle wrote: > On 01/27/2016 08:25 AM, Andre Vehreschild wrote: > > Hi all, > > > > attached

Re: [PATCH] Fix libstdc++-v3/include/math.h:66:1 2: error: 'constexpr bool std::isnan(double)' conflicts with a previous declaration

On 27/01/16 19:49 -0500, John David Anglin wrote: The attached patch fixes a stage1 build error compiling genautomata.c on hpux. We need to test for obsolete XOPEN declarations of isinf and isnan on hpux. Further, we need to check individually for isinf and isnan on hpux11 since only isnan ha

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

2016-01-28 9:00 GMT+03:00 H.J. Lu : > On Wed, Jan 27, 2016 at 8:36 AM, H.J. Lu wrote: >> 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:

Re: [PATCH, gcc7, aarch64] Add arithmetic overflow patterns

Hi Richard, Note that this patch appears to depend on your previous patch: https://gcc.gnu.org/ml/gcc-patches/2016-01/txtDPaXOBMuOB.txt for the definition of define_mode_attr DWI. I was looking at this patch as I was working on Bugzilla 68543 which this will address. Regards, Michael Collis

[PATCH] Fix PR69466

The following fixes PR69466 - we try to make our lives easier in vectorization loop manip by duplicating PHIs to random BBs but fail to realize we can't do that for PHIs with constant args. The fix for this PR is to simply skip those we can't duplicate when later lock-step iterating over the sour