Re: [PATCH] Fix result for conditional reductions matching at index 0 (PR tree-optimization/80631)

On Mon, 11 Dec 2017, Jakub Jelinek wrote: > On Mon, Dec 11, 2017 at 06:00:11PM +0100, Kilian Verhetsel wrote: > > Jakub Jelinek writes: > > > Of course it can be done efficiently, what we care most is that the body > > > of > > > the vectorized loop is efficient. > > > >

Re: [AArch64] Fix ICEs in aarch64_print_operand_internal (PR target/83335)

On Tue, Dec 12, 2017 at 06:21:37AM +, Richard Sandiford wrote: > Jakub Jelinek writes: > > Hi! > > > > On Fri, Dec 08, 2017 at 08:10:08PM +0100, Christophe Lyon wrote: > >> >> Can you check? > >> > > >> > I think that's a separate preexisting problem. Could you file a PR? >

Re: [AArch64] Fix ICEs in aarch64_print_operand_internal (PR target/83335)

Jakub Jelinek writes: > Hi! > > On Fri, Dec 08, 2017 at 08:10:08PM +0100, Christophe Lyon wrote: >> >> Can you check? >> > >> > I think that's a separate preexisting problem. Could you file a PR? >> > >> >> Sure, I filed: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83335

Re: [PATCH][i386,AVX] Enable VAES support [2/5]

Hello Julia, On 08 Nov 12:32, Koval, Julia wrote: > Hi, this patch enables VAESDEC instruction from VAES isaset, defined here: > https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf > > Ok for trunk? Patch is OK. Checked

Re: [PATCH][i386,AVX] Enable VAES support [1/5]

Hello Julia, On 25 Oct 12:02, Koval, Julia wrote: > Hi, > This patch enables VAES isaset option. The doc for isaset and instruction: > https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf > > Ok for trunk? Your patch is

Re: [PR81165] discount killed stmts when sizing blocks for threading

On Dec 11, 2017, Jeff Law wrote: >> + gcc_assert (path->length () == 0 || path->last ()->e == e); >> + if (path->length () == 0) >> +return estimate_threading_killed_stmts (e->dest); >> + >> + int total = 0; >> + int i = 0; >> + jump_thread_edge *je; >> +

Re: [PR81165] discount killed stmts when sizing blocks for threading

On Dec 7, 2017, Richard Biener wrote: >> + FOR_EACH_SSA_USE_OPERAND (use_p, stmt, iter, SSA_OP_ALL_USES) > SSA_OP_USE avoids walking virtual uses and we don't want to walk those because we already know writes to memory are not going to be dead anyway, I

Re: [PATCH] Fix broken capitalization in aarch64 diagnostics

On 12/11/2017 10:29 AM, Jakub Jelinek wrote: Hi! Diagnostics should not start with capital letters unless the first word is capitalized that way even in the middle of a sentence. Fixed thusly, ok for trunk? 2017-12-11 Jakub Jelinek * config/aarch64/aarch64.c

Re: [SFN+LVU+IEPM v4 1/9] [SFN] adjust RTL insn-walking API

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> This patch removes unused RTL functions, introduces alternate ones for >> use in a later SFN patch, and regroups other related functions so that >> they appear in a more consistent order. >> >>

Re: [SFN+LVU+IEPM v4 2/9] [SFN] boilerplate changes in preparation to introduce nonbind markers

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> This patch introduces a number of new macros and functions that will > OK. Again, I think this can probably go in as-is. Thanks, FTR here's the installed patch: >From

Re: [SFN+LVU+IEPM v4 9/9] [IEPM] Introduce inline entry point markers

On Nov 10, 2017, Alexandre Oliva wrote: > Output DW_AT_entry_pc based on markers. Here's an updated version of the patch. [IEPM] Introduce inline entry point markers Output DW_AT_entry_pc based on markers. Introduce DW_AT_GNU_entry_view as a DWARF extension. If views are

Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views

On Dec 11, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> This patch introduces an option to enable the generation of location >> views along with location lists. The exact format depends on the >> void >> +dw2_asm_output_symname_uleb128 (const char

Re: [SFN+LVU+IEPM v4 8/9] [IEPM] Introduce debug hook for inline entry point markers

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> The inline_entry hook will be given a definition in a later patch. >> >> for gcc/ChangeLog >> >> * debug.h (gcc_debug_hooks): Add inline_entry. >> * dbxout.c (dbx_debug_hooks,

Re: [SFN+LVU+IEPM v4 6/9] [SFN] Introduce -gstatement-frontiers option, enable debug markers

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> Introduce a command line option to enable statement frontiers, enabled >> by default in optimized builds with DWARF2+ debug information. > OK once all prereqs are ack'd. Thanks, here's what's

Re: [SFN+LVU+IEPM v4 5/9] [SFN] introduce statement frontier notes, still disabled

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> This patch completes the infrastructure for the introduction of >> statement frontiers in C-family languages. > Note I expect minor updates will be necessary due to the Cilk+ removal. > Such

Re: [SFN+LVU+IEPM v4 4/9] [SFN] stabilize find_bb_boundaries

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> * cfgbuild.c (find_bb_boundaries): Don't purge dead edges if, >> without debug insns, we wouldn't, but clean up debug insns >> after a control flow insn nevertheless. > OK. Seems to me like

Re: [SFN+LVU+IEPM v4 3/9] [SFN] not-quite-boilerplate changes in preparation to introduce nonbind markers

On Dec 7, 2017, Jeff Law wrote: > On 11/09/2017 07:34 PM, Alexandre Oliva wrote: >> This patch adjusts numerous parts of the compiler that would > OK. > I'll note you may need minor tweaks due to the Cilk+ removal. THose > changes are pre-approved. Thanks, here's what I've

Re: [PATCH 03/14] C++: add location_t wrapper nodes during parsing (minimal impl)

On 11/10/2017 04:45 PM, David Malcolm wrote: The initial version of the patch kit added location wrapper nodes around constants and uses-of-declarations, along with some other places in the parser (typeid, alignof, sizeof, offsetof). This version takes a much more minimal approach: it only adds

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

On Mon, 2017-12-11 at 15:18 -0700, Martin Sebor wrote: > On 12/11/2017 02:08 PM, David Malcolm wrote: > > On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: > > > Bug 83369 - Missing diagnostics during inlining, notes that when > > > -Wnonnull is issued for an inlined call to a built-in

Re: Add support for masked load/store_lanes

On 11/17/2017 02:36 AM, Richard Sandiford wrote: > Richard Sandiford writes: >> This patch adds support for vectorising groups of IFN_MASK_LOADs >> and IFN_MASK_STOREs using conditional load/store-lanes instructions. >> This requires new internal functions to

[PATCH] avoid alignment error for attribute warn_if_not_aligned

My enhancement to improve the detection of attribute collisions introduced a regression of sorts in the g++.dg/pr53037-4.C test on ia64. https://gcc.gnu.org/ml/gcc-testresults/2017-12/msg00672.html The regression hasn't been noticed anywhere else only because all the other targets apparently

Re: [PATCH] Fix Bug 83237 - Values returned by std::poisson_distribution are not distributed correctly

Hi, On 11/12/2017 23:16, Michele Pezzutti wrote: I lowered to N = 250 and still fails with a good margin. Good. At the moment however, I think we need a bit of rationale for the change that you are proposing, what would you put in a comment in the code? It's been a while since the last

Re: [PATCH][Middle-end]79538 missing -Wformat-overflow with %s and non-member array arguments

On 12/04/2017 08:34 AM, Qing Zhao wrote: Hi, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79538 missing -Wformat-overflow with %s and non-member array arguments -Wformat-overflow uses the routine "get_range_strlen" to decide the maximum

Re: [PATCH 14/14] pp_c_cast_expression: don't print casts for location wrappers

On 11/10/2017 04:45 PM, David Malcolm wrote: This patch suppresses the user-visible printing of location wrappers for "%E" (and "%qE"), adding test coverage via selftests. OK. Jason

Re: [PATCH 13/14] c-format.c: handle location wrappers

On 11/10/2017 04:45 PM, David Malcolm wrote: gcc/c-family/ChangeLog: * c-format.c (check_format_arg): Strip any location wrapper around format_tree. --- gcc/c-family/c-format.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/gcc/c-family/c-format.c

Re: [PATCH 12/14] C++: introduce null_node_p

On 11/10/2017 04:45 PM, David Malcolm wrote: Eschew comparison with null_node in favor of a new null_node_p function, which strips any location wrappers. OK. Jason

Re: [PATCH 11/14] Handle location wrappers in string_conv_p

On 11/10/2017 04:45 PM, David Malcolm wrote: gcc/cp/ChangeLog: * typeck.c (string_conv_p): Strip any location wrapper from "exp". OK. Jason

Re: [PATCH 10/14] warn_for_memset: handle location wrappers

On 11/10/2017 04:45 PM, David Malcolm wrote: gcc/c-family/ChangeLog: * c-warn.c (warn_for_memset): Strip any location wrappers from arg0 and arg2. gcc/cp/ChangeLog: * parser.c (cp_parser_postfix_expression): Before warn_for_memset, strip any wrapper around "arg2"

Re: [PATCH 08/14] cp/tree.c: strip location wrappers in lvalue_kind

On 11/10/2017 04:45 PM, David Malcolm wrote: Without this, then lvalue_p returns false for decls, and hence e.g. uses of them for references fail. Stripping location wrappers in lvalue_kind restores the correct behavior of lvalue_p etc. gcc/cp/ChangeLog: * tree.c (lvalue_kind): Strip

Re: [PATCH 09/14] Strip location wrappers in null_ptr_cst_p

On 11/10/2017 04:45 PM, David Malcolm wrote: Without this, "NULL" fails to be usable in C++11 onwards. gcc/cp/ChangeLog: * call.c (null_ptr_cst_p): Strip location wrappers when converting from '0' to a pointer type in C++11 onwards. OK. Jason

Re: [PATCH 07/14] reject_gcc_builtin: strip any location wrappers

On 11/10/2017 04:45 PM, David Malcolm wrote: Otherwise pr70144-1.c breaks. gcc/c-family/ChangeLog: * c-common.c (reject_gcc_builtin): Strip any location from EXPR. --- gcc/c-family/c-common.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/c-family/c-common.c

Re: [PATCH 06/14] Fix Wsizeof-pointer-memaccess*.c

On 11/10/2017 04:45 PM, David Malcolm wrote: gcc/c-family/ChangeLog: * c-warn.c (sizeof_pointer_memaccess_warning): Strip any location wrappers from src and dest. Here the existing calls to tree_strip_nop_conversions ought to handle the wrappers. Jason

Re: [PATCH 05/14] tree.c: strip location wrappers from integer_zerop etc

On 11/10/2017 04:45 PM, David Malcolm wrote: We need to strip away location wrappers in tree.c predicates like integer_zerop, otherwise they fail when they're called on wrapped INTEGER_CST; an example can be seen for c-c++-common/Wmemset-transposed-args1.c in g++.sum, where the

[PATCH] Fix the new pr83361.c testcase

It needs the following. Sorry for that. Committing. Segher 2017-12-11 Segher Boessenkool gcc/testsuite/ * gcc.dg/pr83361.c: Add -Wno-div-by-zero to dg-options. --- gcc/testsuite/gcc.dg/pr83361.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH 01/14] C++: preserve locations within build_address

On 11/10/2017 04:45 PM, David Malcolm wrote: This is needed for the locations of string literals to be usable, otherwise the ADDR_EXPR has UNKNOWN_LOCATION, despite wrapping a node with a correct location_t. gcc/cp/ChangeLog: * typeck.c (build_address): Use location of operand when

Re: [PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

On 11/28/2017 12:31 PM, David Malcolm wrote: > This patch adds selftest coverage for the fix for PR c/82050 (r255214). > > The selftest iterates over various "interesting" column and line-width > values to try to shake out bugs in the fix-it printing routines, a kind > of "torture" selftest. > >

Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views

On 11/09/2017 07:34 PM, Alexandre Oliva wrote: > This patch introduces an option to enable the generation of location > views along with location lists. The exact format depends on the > DWARF version: it can be a separate attribute (DW_AT_GNU_locviews) or > (DW_LLE_view_pair) entries in DWARF5+

Re: Handle more SLP constant and extern definitions for variable VF

On 11/09/2017 07:20 AM, Richard Sandiford wrote: > This patch adds support for vectorising SLP definitions that are > constant or external (i.e. from outside the loop) when the vectorisation > factor isn't known at compile time. It can only handle cases where the > number of SLP statements is a

Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files

On Mon, Dec 11, 2017 at 2:16 PM, Stephen Crane wrote: > Thanks for committing the GCC portion and following up on this. I had > been meaning to write and ask. I don't have commit privs for binutils, > so either you or Cary will have to commit the binutils patch as well, > if

[PATCH] avoid false negatives in attr-nonstring-3.c (PR 83131)

The attr-nonstring-3.c test fails on targets that expand the calls to some of the tested string functions in builtins.c, before they reach the checker in calls.c. The failures were reported on powrrpc64le but tests can be constructed that fail even on other targets (including x86_64). To fix

Re: C PATCH for c/82679 (rejects-valid with _Atomic and arrays)

On 12/10/2017 10:48 AM, Marek Polacek wrote: > We were wrongly rejecting code in the attached test because the check > in grokdeclarator is wrong: we only want to check whether the user is > trying to apply _Atomic to an array type, i.e. this: > > typedef int T[10]; > _Atomic T a; > >

Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files

On Mon, Dec 11, 2017 at 2:16 PM, Stephen Crane wrote: > Thanks for committing the GCC portion and following up on this. I had > been meaning to write and ask. I don't have commit privs for binutils, > so either you or Cary will have to commit the binutils patch as well, > if

Re: [PING 2][PATCH] enhance -Wrestrict to handle string built-ins (PR 78918)

On 12/08/2017 12:19 PM, Martin Sebor wrote: > Attached is revision 8 of the patch with the changes suggested > and/or requested below. [ Big snip. ] > > > gcc-78918.diff > > > PR tree-optimization/78918 - missing -Wrestrict on memcpy copying over self > > gcc/c-family/ChangeLog: > >

Re: [PATCH] C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR c++/80567)

On Wed, Nov 22, 2017 at 10:36 AM, David Malcolm wrote: > PR c++/81610 and PR c++/80567 report problems where the C++ frontend > suggested "if", "for" and "else" as corrections for misspelled variable > names. Hmm, what about cases where people are actually misspelling

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

On 12/11/2017 02:08 PM, David Malcolm wrote: On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is issued for an inlined call to a built-in function, GCC doesn't print the inlining stack, making it hard to debug

Re: [PATCH] Fix Bug 83237 - Values returned by std::poisson_distribution are not distributed correctly

I lowered to N = 250 and still fails with a good margin. On 12/11/2017 09:58 PM, Michele Pezzutti wrote: I apologize as I am unable to run the test suite in its full form. Nevertheless, I locally tested the following patch for the test suite:

Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files

Thanks for committing the GCC portion and following up on this. I had been meaning to write and ask. I don't have commit privs for binutils, so either you or Cary will have to commit the binutils patch as well, if it's not too much trouble. I think much has changed to need a rebase? Thanks,

Re: [PATCH] [GOLD] Add plugin API for processing plugin-added input files

On Thu, Nov 9, 2017 at 9:04 PM, Cary Coutant wrote: >> include/ChangeLog: >> 2017-11-09 Stephen Crane >> >> * plugin-api.h: Add new plugin hook to allow processing of input >> files added by a plugin. >>

[PATCH, rs6000] Fix PR83332 (missing vcond patterns)

Hi, A new test case introduced for PR81303 failed on powerpc64 (BE, LE). This turns out to be due to a missing standard pattern (vcondv2div2df). This and a couple of other patterns are easy to support with existing logic by just adding new patterns with appropriate modes. That's all this patch

Re: [Patch combine] Don't create vector mode ZERO_EXTEND from subregs

On 12/11/2017 07:18 AM, James Greenhalgh wrote: > > Hi, > > In simplify_set we try transforming the paradoxical subreg expression: > > (set FOO (subreg:M (mem:N BAR) 0)) > > in to: > > (set FOO (zero_extend:M (mem:N BAR))) > > However, this code does not consider the case where M is a

[PATCH] Fix result for conditional reductions matching at index 0 (PR tree-optimization/80631)

On Mon, Dec 11, 2017 at 06:00:11PM +0100, Kilian Verhetsel wrote: > Jakub Jelinek writes: > > Of course it can be done efficiently, what we care most is that the body of > > the vectorized loop is efficient. > > That's fair, I was looking at the x86 assembly being generated

Re: [PATCH] Allow USE in PARALLELs in store_data_bypass_p (take 2)

> The old code was inconsistent, had return false; in one case and assert in > the remaining two spots. If you are not against it, I'd use return false; > in both cases if we want consistency. Sure, thanks. -- Eric Botcazou

Re: Ping ^2 [PATCH], Add rounding built-ins to the _Float and _FloatX built-in functions

On Fri, Oct 27, 2017 at 06:39:21PM -0400, Michael Meissner wrote: > The power9 (running PowerPC ISA 3.0) has a round to integer instruction > (XSRQPI) that does various flavors of round an IEEE 128-bit floating point to > integeral values. This patch adds the support to the machine independent >

Re: [PATCH] ifcvt: Call fixup_partitions (PR83361)

On 12/11/2017 08:49 AM, Segher Boessenkool wrote: > After converting a conditional branch to an unconditional trap to a > conditional trap, if the original trap is still reachable from another > path, it may be that it is in a hot basic block and only reachable from > cold blocks. Fix that up. >

[PATCH] Handle LOOP_DIST_ALIAS ifns in move_sese_region_to_fn (PR tree-optimization/83359)

Hi! Unlike LOOP_VECTORIZED ifns, LOOP_DIST_ALIAS is added by the ldist pass and needs to be maintained until the vectorizer, and parloops in between that. Earlier I've added code to update or drop orig_loop_num during move_sese_region_to_fn, but that is not sufficient. If we move the whole pair

Re: [PATCH] have -Wnonnull print inlining stack (PR 83369)

On Mon, 2017-12-11 at 09:51 -0700, Martin Sebor wrote: > Bug 83369 - Missing diagnostics during inlining, notes that when > -Wnonnull is issued for an inlined call to a built-in function, > GCC doesn't print the inlining stack, making it hard to debug > where the problem comes from. > > When the

Re: [PATCH] Fix Bug 83237 - Values returned by std::poisson_distribution are not distributed correctly

I apologize as I am unable to run the test suitein its full form. Nevertheless, I locally tested the following patch for the test suite: *26_numerics/random/poisson_distribution/operators/values.cc     Add additional test to cover bin 'floor(mu) + 1' by compiling locally values.cc and running

Re: [PATCH] PR libgcc/83112, Fix warnings on libgcc float128-ifunc.c

On Fri, Dec 01, 2017 at 05:53:55PM -0600, Segher Boessenkool wrote: > On Fri, Dec 01, 2017 at 12:40:22AM -0500, Michael Meissner wrote: > > After committing the previous patch, I noticed that it was now generating > > warnings for __{mul,div}kc3_{sw,hw} not having a prototype that I hadn't > >

[PATCH] testsuite: add coverage for diagnostics relating to inlining (PR tree-optimization/83336)

In theory, the diagnostics subsystem can print context information on code inlining when diagnostics are emitted by the middle-end, describing the chain of inlined callsites that led to a particular warning, but PR tree-optimization/83336 describes various issues with this. An underlying issue is

[patch, fortran, doc, committed] Update description of MINLOC and MAXLOC

Hi, I have just committed the attached doc patch as obvious after "make dvi" and "make pdf". 2017-12-11 Thomas Koenig * intrinsic.texi (MAXLOC): Update documentation for character arrays and KIND argument. (MINLOC): Likewise. Regards

Re: [PR81165] discount killed stmts when sizing blocks for threading

On 12/07/2017 05:04 AM, Alexandre Oliva wrote: > We limit the amount of copying for jump threading based on counting > stmts. This counting is overly pessimistic, because we will very > often delete stmts as a consequence of jump threading: when the final > conditional jump of a block is removed,

Re: [PATCH][RFA][P1 PR tree-optimization/83298] Avoid over-optimistic result range for COND_EXPR

On 12/08/2017 04:17 AM, Richard Biener wrote: > > I'm not convinced that when you look forward past the dominance frontier > and do VRP analysis on stmts without analyzing all intermediate > stmts on the path (or at least push all defs on that path temporarily > to VR_VARYING) is fixed by this

Re: [RFA][PATCH] 8/n Pull evrp range analyzer into its own file

On 12/09/2017 02:19 PM, Gerald Pfeifer wrote: > On Wed, 22 Nov 2017, Jeff Law wrote: * gimple-ssa-evrp-analyze.c: New file pulled from gimple-ssa-evrp.c. >>> >>> With the move to C++, wasn't there a policy to name new files *.cc >>> instead of *.c? >> I'm happy to use .cc if that's where we

Re: [PATCH][RFA][P1 PR tree-optimization/83298] Avoid over-optimistic result range for COND_EXPR

On 12/08/2017 04:17 AM, Richard Biener wrote: > On Fri, Dec 8, 2017 at 1:18 AM, Jeff Law wrote: >> >> So the underlying issue here is quite simple. Given something like >> >> x = (cond) ? res1 : res2; >> >> EVRP analysis will compute the resultant range using vrp_meet of the >>

Re: [PATCH 3/3] diagnose attribute aligned conflicts (PR 81566)

http://gcc.gnu.org/ml/gcc-testresults/2017-12/msg00672.html Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."

Re: [PATCH 3/3] diagnose attribute aligned conflicts (PR 81566)

On 12/09/2017 04:40 AM, Andreas Schwab wrote: That requires updates to gcc.dg/pr53037-4.c and g++.dg/pr53037-4.C. I don't see these failures in my own test result or in those reported for common targets. Would you mind providing some details about where this output came from? Martin FAIL:

Re: [patch, fortran] Implement maxval for characters

I have created https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83379 and assigned it to myself. This should be easy to fix. OK, I have updated the test cases in question. They pass for me at least. I'll keep the PR open for a couple of days to make sure this is really fixed. Regards

Re: [PATCH] Fix broken capitalization in aarch64 diagnostics

On December 11, 2017 6:29:07 PM GMT+01:00, Jakub Jelinek wrote: >Hi! > >Diagnostics should not start with capital letters unless the first word >is >capitalized that way even in the middle of a sentence. > >Fixed thusly, ok for trunk? OK. Richard. >2017-12-11 Jakub

Re: [patch, fortran] Implement maxval for characters

Christophe and James (and everybody else), I have created https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83379 and assigned it to myself. This should be easy to fix. Regards Thomas

[AArch64] Fix ICEs in aarch64_print_operand_internal (PR target/83335)

Hi! On Fri, Dec 08, 2017 at 08:10:08PM +0100, Christophe Lyon wrote: > >> Can you check? > > > > I think that's a separate preexisting problem. Could you file a PR? > > > > Sure, I filed: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83335 > > > Personally I'd just remove the assert, but I'm

[PATCH] Fix broken capitalization in aarch64 diagnostics

Hi! Diagnostics should not start with capital letters unless the first word is capitalized that way even in the middle of a sentence. Fixed thusly, ok for trunk? 2017-12-11 Jakub Jelinek * config/aarch64/aarch64.c (aarch64_print_operand): Don't start

[PATCH] RL78 movdi improvement

Hello, The following patch improves 64 bit operations by instructing GCC to use 16 bit movw instead of 8 bit mov. On the following test case the patch reduces the code size from 323 bytes to 245 bytes. unsigned long long my_anddi3(unsigned long long x, unsigned long long y){ return x & y; } I

Re: [PATCH][ARM][gcc-7] Fix wrong code by arm_final_prescan with fp16 move instructions

On 30/11/17 16:01, Sudakshina Das wrote: Hi This patch is the fix for gcc-7 for the same issue as mentioned in: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02209.html For the following test case: __fp16 test_select (__fp16 a, __fp16 b, __fp16 c) {   return (a < b) ? b : c; } when compiled

Re: [PATCH] Fix result for conditional reductions matching at index 0

On Mon, Dec 11, 2017 at 06:00:11PM +0100, Kilian Verhetsel wrote: > Jakub Jelinek writes: > > Of course it can be done efficiently, what we care most is that the body of > > the vectorized loop is efficient. > > That's fair, I was looking at the x86 assembly being generated

Re: [PATCH] Fix result for conditional reductions matching at index 0

Jakub Jelinek writes: > Of course it can be done efficiently, what we care most is that the body of > the vectorized loop is efficient. That's fair, I was looking at the x86 assembly being generated when a single vectorized iteration was enough (because that is the context in

[PATCH] have -Wnonnull print inlining stack (PR 83369)

Bug 83369 - Missing diagnostics during inlining, notes that when -Wnonnull is issued for an inlined call to a built-in function, GCC doesn't print the inlining stack, making it hard to debug where the problem comes from. When the -Wnonnull warning was introduced into the middle-end the

Re: [PATCH, rs6000] (v2) Gimple folding of splat_uX

Hi! On Fri, Dec 08, 2017 at 11:08:26AM -0600, Will Schmidt wrote: > Add support for gimple folding of splat_u{8,16,32}. > Testcase coverage is primarily handled by existing tests > testsuite/gcc.target/powerpc/fold-vec-splat_*.c > > One new test added to verify we continue to receive > an

PING: Re: [PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

Ping: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02459.html On Tue, 2017-11-28 at 14:31 -0500, David Malcolm wrote: > This patch adds selftest coverage for the fix for PR c/82050 > (r255214). > > The selftest iterates over various "interesting" column and line- > width > values to try to

Re: [PATCH #2], PR target/81959, Fix ++int to _Float128 conversion on power9

On Mon, Dec 04, 2017 at 04:31:55PM -0500, Michael Meissner wrote: > On Fri, Dec 01, 2017 at 05:33:39PM -0600, Segher Boessenkool wrote: > > Okay for trunk. Further improvements welcome ;-) Thanks! > > Here is the patch for GCC 7 (the bug shows up in GCC 7). It is slightly > different due to

PING: [PATCH] C++: avoid most reserved words as misspelling suggestions (PR c++/81610 and PR c++/80567)

Ping: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02048.html On Wed, 2017-11-22 at 10:36 -0500, David Malcolm wrote: > lookup_name_fuzzy can offer some reserved words as suggestions for > misspelled words, helping with "singed"/"signed" typos. > > PR c++/81610 and PR c++/80567 report problems

[PING ^ 2] Re: [PATCH v2: 00/14] Preserving locations for variable-uses and constants (PR 43486)

Ping for this patch kit: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00880.html (and thanks again for looking at patch 2 earlier) On Thu, 2017-11-30 at 14:17 -0500, David Malcolm wrote: > Ping for the rest of this kit: > https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00880.html > >

[PATCH] ifcvt: Call fixup_partitions (PR83361)

After converting a conditional branch to an unconditional trap to a conditional trap, if the original trap is still reachable from another path, it may be that it is in a hot basic block and only reachable from cold blocks. Fix that up. This fixes PR83361. Bootstrapping on powerpc64-linux

[PATCH, rs6000] generate loop code for memcmp inline expansion

This patch builds on two previously posted patches: https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01216.html https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02599.html The previous patches allow the use of bdnzt. This patch allows the cmpstrsi pattern expansion to handle longer blocks without

[patch AArch64] Do not perform a vector splat for vector initialisation if it is not useful

Hi, In the testcase in this patch we create an SLP vector with only two elements. Our current vector initialisation code will first duplicate the first element to both lanes, then overwrite the top lane with a new value. This duplication can be clunky and wasteful. Better would be to simply

RE: [PATCH] rl78 anddi3 improvement

Hello Jeff, Thank you for your comments. >>So I think you're ultimately far better off determining why GCC does not >>generate efficient code for 64bit logicals on the rl78 target. I totally agree with you, this is why: 1. I have another patch: I define_expand movdi in which I instruct GCC to

Re: [PATCH] Fix segfault in inliner with attribute flatten

On Mon, Dec 11, 2017 at 8:01 AM, Andi Kleen wrote: > From: Andi Kleen > > This fixes a segfault in gcc 7/8 when building turicreate. > > For some reason the node has no decl here, and there is a > crash when checking for attribute flatten. As said in

Re: [PATCH] Fix stack overflow with autofdo (PR83355)

On Mon, Dec 11, 2017 at 8:01 AM, Andi Kleen wrote: > From: Andi Kleen > > g++.dg/bprob* is failing currently with autofdo. > > Running in gdb shows that there is a very deep recursion in get_index_by_decl > until it > overflows the stack. > > This

[PR83370][AARCH64]Use tighter register constraints for sibcall patterns.

Hi all, In aarch64 backend, ip0/ip1 register will be used in the prologue/epilogue as temporary register. When the compiler is performing sibcall optimization. It has the chance to use ip0/ip1 register for indirect function call to hold the address. However, those two register might be

[PATCH] Fix PR81889

Unrolling often has only rudimentary info for the upper bound of a loop even though VRP would compute reasonable bounds for the variables participating in the loop exit test. This causes excessive peeling and thus warnings from array bound and uninit warning code. The following mitigates

Re: [PATCH] annotate vector::_M_default_append fo better codegen (PR 83229)

On 05/12/17 20:44 -0700, Martin Sebor wrote: Bug 83239 - False positive from -Wstringop-overflow on simple std::vector code, besides pointing out the warning, suggests a missed optimization opportunity. This is the second report involving for vector (the last one was pr79095) with the same

[Patch combine] Don't create vector mode ZERO_EXTEND from subregs

Hi, In simplify_set we try transforming the paradoxical subreg expression: (set FOO (subreg:M (mem:N BAR) 0)) in to: (set FOO (zero_extend:M (mem:N BAR))) However, this code does not consider the case where M is a vector mode, allowing it to construct (for example): (zero_extend:V4SI

Re: [patch, fortran] Implement maxval for characters

On Wed, Dec 06, 2017 at 11:38:21AM +, Christophe Lyon wrote: > Hi, > > > On 28 November 2017 at 19:40, Thomas Koenig wrote: > > Hello world, > > > > the attached patch implements maxval for characters, an F2003 feature > > that we were missing up to now. > > > >

Re: [PATCH] Fix result for conditional reductions matching at index 0

On Mon, Dec 11, 2017 at 02:11:34PM +0100, Jakub Jelinek wrote: > Thanks, it applies cleanly now > > + else if ((STMT_VINFO_VEC_REDUCTION_TYPE (stmt_info) == COND_REDUCTION > > + || (STMT_VINFO_VEC_REDUCTION_TYPE (stmt_info) > > + == INTEGER_INDUC_COND_REDUCTION)) > > + &&

[PATCH][AArch64] Specify fp16 support for Cortex-A55 and Cortex-A75

Hi all, The Cortex-A55 and Cortex-A75 processors support the fp16 extension. We already specify them as such in the arm port. This patch makes aarch64 consistent on this front. Bootstrapped and tested on aarch64-none-linux-gnu. Manually checked that compiling with aarch64-none-linux-gnu-gcc

Re: [PATCH] Fix result for conditional reductions matching at index 0

On Mon, Dec 11, 2017 at 11:56:55AM +0100, Kilian Verhetsel wrote: > Jakub Jelinek writes: > > As it doesn't apply, I can't easily check what the patch generates > > on the PR80631 testcases vs. my thoughts on that; though, if it emits > > something more complicated for the

Re: [PATCH] Allow USE in PARALLELs in store_data_bypass_p (take 2)

On Mon, Dec 11, 2017 at 01:26:42PM +0100, Eric Botcazou wrote: > > Ah, that makes a lot of sense. So like this? > > > > 2017-12-11 Jakub Jelinek > > > > * recog.c (store_data_bypass_p_1): New function. > > (store_data_bypass_p): Handle USE in a PARALLEL like

Re: [PATCH] Allow USE in PARALLELs in store_data_bypass_p (take 2)

> Ah, that makes a lot of sense. So like this? > > 2017-12-11 Jakub Jelinek > > * recog.c (store_data_bypass_p_1): New function. > (store_data_bypass_p): Handle USE in a PARALLEL like CLOBBER. Use > store_data_bypass_p_1 to avoid code duplication.

Re: [PATCH][GCC][ARM] Fix failing testcase pragma_fpu_attribute.c

On 11 December 2017 at 12:56, Tamar Christina wrote: >> > > >> > > It also works when I build natively using just configure && make. >> > > Could be >> > something in the configure flags. >> > > Looking back at it, if the vanilla compiler doesn't support neon I >> > > can

RE: [PATCH][GCC][ARM] Fix failing testcase pragma_fpu_attribute.c

> > > > > > It also works when I build natively using just configure && make. > > > Could be > > something in the configure flags. > > > Looking back at it, if the vanilla compiler doesn't support neon I > > > can see the test failing. But fixing it means Turning on neon and > > > then turning it

[PATCH] Allow USE in PARALLELs in store_data_bypass_p (take 2)

On Mon, Dec 11, 2017 at 12:09:14PM +0100, Eric Botcazou wrote: > > Is that long enough to be worth it? I mean, in all other places (rtlanal.c, > > recog.c, ...) we use similar code in all spots where it is needed, adding > > an inline would just mean yet another thing to remember. Or do you mean

  1   2   >