[PATCH, v4] Fix PR51513, switch statement with default case containing __builtin_unreachable leads to wild branch

Here is the updated patch to use gimple_seq_unreachable_p() which scans the sequence backwards so it bails out earlier in the common case (ie, no call to __builtin_unreachable). As discussed in the previous thread, we remove case statement labels from the jump table that lead to unreachable

Re: [RFC]: Fix Ada boostrap failure on S/390 with -mzarch

On Tue, Apr 4, 2017 at 4:46 AM, Andreas Krebbel wrote: > On 04/03/2017 06:18 PM, Eric Botcazou wrote: >>> On S/390 UNITS_PER_WORD is: >>> 8 with -m64 >>> 4 with -m31 >>> 8 with -m31 -mzarch >>> >>> This has been chosen to support use of 64 bit registers also in 32 bit

[Bug ada/80626] [7/8 Regression] Ada x32 multilib build failure for a-cfinve.ads

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80626 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[PATCH 2/3] (v3) C++ template type diff printing

Changes in v3: - Merge bodies of type_to_string_with_compare and print_template_tree_comparison into a new function, print_template_differences. Use simpler comma-insertion criterion. - Cleanup assertions in cxx_format_postprocessor::handle. Would it make sense to rename "m_type_a"/"m_type_b" to

[PATCH 1/3] (v3) Non-C++ parts of template type diff printing

This patch is broken out from the C++ patch, for ease of review. I believe I can self-approve this one, assuming the other patches in the kit are OK. The patch: - adds the bool and const char ** params to the pp_format_decoder callback - adds the format_postprocessor class - adds the "type-diff"

[PATCH 3/3] (v3) Use %qH and %qI throughout C++ frontend

(unchanged in v3) Changed in v2: use %qH and %qI rather than %H and %I. This is the second half of the kit, which uses %qH and %qI throughout the C++ frontend whenever describing type mismatches between a pair of %qT. gcc/cp/ChangeLog: * call.c (print_conversion_rejection): Replace

[PATCH 0/3] v3 of C++ template type diffing

On Tue, 2017-05-09 at 10:52 -0400, Nathan Sidwell wrote: > On 05/09/2017 10:07 AM, David Malcolm wrote: > > > > +static const char * > > +type_to_string_with_compare (tree type, tree peer, bool verbose, > > +bool show_color) > > +{ > > > + for (int idx = 0; idx <

Re: Backporting Patches to GCC 7

On Tue, 09 May 2017 01:50:42 PDT (-0700), richard.guent...@gmail.com wrote: > On Mon, May 8, 2017 at 10:00 PM, Jonathan Wakely > wrote: >> On 5 May 2017 at 21:35, Palmer Dabbelt wrote: >>> I just submitted two patches against trunk. I'd like to also have them on >>> the

Move myself to Write After Approval section

Hi all, I am stepping down as the SH backend maintainer for personal reasons. I might still send tiny SH patches and sh-linux testresults if the HDD of my SH machine can be recovered. I've moved myself to write after approval section. I didn't think that I could be involved with such huge and

Move myself to Write After Approval section

Hi all, I am stepping down as the SH backend maintainer for personal reasons. I might still send tiny SH patches and sh-linux testresults if the HDD of my SH machine can be recovered. I've moved myself to write after approval section. I didn't think that I could be involved with such huge and

[Bug libstdc++/79135] null pointer dereference in std::_Bit_reference::operator=(bool) (stl_bvector.h:87)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79135 Brian 'geeknik' Carpenter changed: What|Removed |Added Status|WAITING |RESOLVED

[Bug libstdc++/79136] read outside of buffer in char* std::__copy_move<false, false, std::random_access_iterator_tag>::__copy_m(unsigned char const*, unsigned char const*,

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79136 Brian 'geeknik' Carpenter changed: What|Removed |Added Status|WAITING |RESOLVED

[PATCH] RISC-V: Add Sign/Zero extend patterns for PIC loads

Loads on RISC-V are sign-extending by default, but we weren't telling GCC this in our PIC load patterns. This corrects the problem, and adds a zero-extending pattern as well. gcc/ChangeLog 2017-05-09 Palmer Dabbelt * config/riscv/riscv.md (ZERO_EXTEND_LOAD):

[Bug target/79038] Improve PowerPC ISA 3.0 conversion between integers and hardware _Float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79038 --- Comment #8 from Michael Meissner --- Author: meissner Date: Tue May 9 23:49:37 2017 New Revision: 247820 URL: https://gcc.gnu.org/viewcvs?rev=247820=gcc=rev Log: [gcc] 2017-05-09 Michael Meissner

[Bug target/79203] Update PowerPC double->int conversions to know about -mvsx-small-integer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79203 --- Comment #3 from Michael Meissner --- Author: meissner Date: Tue May 9 23:49:37 2017 New Revision: 247820 URL: https://gcc.gnu.org/viewcvs?rev=247820=gcc=rev Log: [gcc] 2017-05-09 Michael Meissner

[Bug target/79202] On Power8, consider using vupkhsw/xxpermdi to sign extend an int in a vector register instead of mfvsrwz/mtvsrwa

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79202 --- Comment #7 from Michael Meissner --- Author: meissner Date: Tue May 9 23:49:37 2017 New Revision: 247820 URL: https://gcc.gnu.org/viewcvs?rev=247820=gcc=rev Log: [gcc] 2017-05-09 Michael Meissner

[Bug libstdc++/79136] read outside of buffer in char* std::__copy_move<false, false, std::random_access_iterator_tag>::__copy_m(unsigned char const*, unsigned char const*,

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79136 --- Comment #3 from Jonathan Wakely --- Be sure to include which version of the draco code to check out; master?

[Bug lto/59000] lto can't merge user-defined weak builtin functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59000 wgh at beyondunreal dot com changed: What|Removed |Added CC||wgh at beyondunreal dot com

[Bug libstdc++/79135] null pointer dereference in std::_Bit_reference::operator=(bool) (stl_bvector.h:87)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79135 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug libstdc++/79136] read outside of buffer in char* std::__copy_move<false, false, std::random_access_iterator_tag>::__copy_m(unsigned char const*, unsigned char const*,

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79136 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

Re: [PATCH, GCC/LTO, ping3] Fix PR69866: LTO with def for weak alias in regular object file

> Ping? Sorry for late reply > >Hi, > > > >This patch fixes an assert failure when linking one LTOed object file > >having a weak alias with a regular object file containing a strong > >definition for that same symbol. The patch is twofold: > > > >+ do not add an alias to a partition if it is

gcc-5-20170509 is now available

Snapshot gcc-5-20170509 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20170509/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5

[Bug target/80697] New: On PowerPC, the spec 2006 benchmark milc had a 5.6% regression under GCC 7.1 compared to GCC 6.3.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80697 Bug ID: 80697 Summary: On PowerPC, the spec 2006 benchmark milc had a 5.6% regression under GCC 7.1 compared to GCC 6.3. Product: gcc Version: 8.0 Status: UNCONFIRMED

Re: [PATCH, rs6000] Fix vec_xl and vec_xst intrinsics for P8

On Tue, May 09, 2017 at 01:44:35PM -0500, Bill Schmidt wrote: > I forgot to ask -- this fix is needed for GCC 6 and 7 as well. Is this ok > for backport > after the usual burn-in? Sure! Segher

Fwd: [patch, fortran] PR 80687, 80696

... forgot to copy in gcc-patches here... Weitergeleitete Nachricht Betreff: [patch, fortran] PR 80687, 80696 Datum: Tue, 9 May 2017 23:14:30 +0200 Von: Thomas Koenig An: fort...@gcc.gnu.org Hello world, it appears that using

OpenACC C front end maintenance: c_parser_oacc_single_int_clause (was: [OpenACC] num_gangs, num_workers and vector_length in c++)

Hi! On Wed, 4 Nov 2015 14:10:29 -0800, Cesar Philippidis wrote: > > [...] > > Thanks. I've applied this patch to trunk. > gcc/cp/ > * (cp_parser_oacc_single_int_clause): New function. > (cp_parser_oacc_clause_vector_length): Delete. >

[Bug target/68163] GCC on power8 does not issue the stxsspx instruction on power8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68163 --- Comment #3 from Michael Meissner --- Author: meissner Date: Tue May 9 21:25:23 2017 New Revision: 247819 URL: https://gcc.gnu.org/viewcvs?rev=247819=gcc=rev Log: [gcc] 2017-05-09 Michael Meissner PR

Re: Record equivalences for spill registers

On Sun, May 7, 2017 at 11:47 PM, Andrew Pinski wrote: > On Sun, May 7, 2017 at 11:37 PM, Richard Sandiford > wrote: >> Really sorry for the breakage. I'd forgotten that this depended on: >> >>

Re: [1/2] PR 78736: New warning -Wenum-conversion

On 05/09/2017 07:04 PM, Martin Sebor wrote: >>> > > -Wassign-enum is a Clang warning too, it just isn't included in > either -Wall or -Wextra. It warns when a constant is assigned > to a variable of an enumerated type and is not representable in > it. I enhanced it for GCC to also warn when the

Re: [PATCH 1/2] C++ template type diff printing

On 08/05/17 17:51, David Malcolm wrote: So I think it can work if we add a "needs quoting" flag to the postprocessing phase, if we need to handle the case where %H and %I ever appear without 'q' (and have the delayed handling stash that flag, and do the quoting there). I'll look at implementing

Re: [PATCH, rs6000] Add x86 instrinsic headers to GCC PPC64LE taget

On Tue, May 09, 2017 at 02:33:00PM -0500, Steven Munroe wrote: > On Tue, 2017-05-09 at 12:23 -0500, Segher Boessenkool wrote: > > On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote: > > > Thus I would like to restrict this support to PowerPC > > > targets that support VMX/VSX and

[Bug fortran/37336] [F03] Finish derived-type finalization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336 Bug 37336 depends on bug 79311, which changed state. Bug 79311 Summary: [OOP] ICE in generate_finalization_wrapper, at fortran/class.c:1992 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79311 What|Removed

[Bug fortran/79311] [OOP] ICE in generate_finalization_wrapper, at fortran/class.c:1992

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79311 janus at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

Re: [Patch, Fortran, OOP] PR 79311: ICE in generate_finalization_wrapper, at fortran/class.c:1992

2017-05-09 18:18 GMT+02:00 Jerry DeLisle : > On 05/08/2017 02:16 PM, Janus Weil wrote: >> Hi all, >> >> the attached patch fixes an ICE-on-valid problem with finalization by >> making sure that the finalization procedures are properly resolved. >> >> In the test case, the

Use "oacc kernels parallelized" attribute for parallelized OpenACC kernels (was: Use "oacc kernels" attribute for OpenACC kernels)

Hi! On Mon, 08 May 2017 21:29:28 +0200, I wrote: > On Thu, 4 Aug 2016 16:07:00 +0200, I wrote: > > Ping. > > > > On Wed, 27 Jul 2016 12:06:59 +0200, I wrote: > > > On Mon, 25 Jan 2016 16:09:14 +0100, Jakub Jelinek > > > wrote: > > > > On Mon, Jan 25, 2016 at 10:06:50AM -0500,

[Bug fortran/79311] [OOP] ICE in generate_finalization_wrapper, at fortran/class.c:1992

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79311 --- Comment #8 from janus at gcc dot gnu.org --- Author: janus Date: Tue May 9 20:55:38 2017 New Revision: 247818 URL: https://gcc.gnu.org/viewcvs?rev=247818=gcc=rev Log: 2017-05-09 Janus Weil PR fortran/79311

Re: [PATCH v2,rs6000] Add built-in function support for compare bytes instruction

Hi Kelvin, On Mon, May 08, 2017 at 11:04:59AM -0600, Kelvin Nilsen wrote: > + /* If any supplied arguments are wider than 32 bits, resolve to > + 64-bit variant of built-in function. */ > + if ((arg1_mode == TImode) || (arg1_mode == DImode) || > + (arg2_mode == TImode) ||

[PATCH 13/13] make inverted_post_order_compute() operate on a vec

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * cfganal.c (inverted_post_order_compute): Change argument type to vec *. * cfganal.h (inverted_post_order_compute): Adjust prototype. *

[PATCH 09/13] use auto_bitmap more with alternate obstacks

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * df-core.c (df_set_blocks): Start using auto_bitmap. (df_compact_blocks): Likewise. * df-problems.c (df_rd_confluence_n): Likewise. *

[PATCH 07/13] use auto_bitmap more

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * bt-load.c (combine_btr_defs): Use auto_bitmap to manage bitmap lifetime. (migrate_btr_def): Likewise. * cfgloop.c

[PATCH 12/13] make depth_first_search_ds a class

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * cfganal.c (connect_infinite_loops_to_exit): Adjust. (depth_first_search::depth_first_search): Change structure init function to this constructor.

[PATCH 11/13] make more vars auto_sbitmaps

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * ddg.c (find_nodes_on_paths): Use auto_sbitmap. (longest_simple_path): Likewise. * shrink-wrap.c (spread_components): Likewise.

[PATCH 08/13] move several bitmaps from gc memory to the default obstack and use auto_bitmap

From: Trevor Saunders These places where probably trying to use the default bitmap obstack, but passing 0 to bitmap_initialize actually uses gc allocation. In any case they are all cleaned up before going out of scope so using auto_bitmap should be fine.

[PATCH 10/13] make a member an auto_sbitmap

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * tree-ssa-dse.c (dse_dom_walker): Make m_live_byes a auto_sbitmap. --- gcc/tree-ssa-dse.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-)

[PATCH 04/13] allow auto_bitmap to use other bitmap obstacks

From: Trevor Saunders gcc/ChangeLog: 2017-05-07 Trevor Saunders * bitmap.h (class auto_bitmap): New constructor taking bitmap_obstack * argument. --- gcc/bitmap.h | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/bitmap.h

[PATCH 06/13] replace some manual stacks with auto_vec

From: Trevor Saunders gcc/ChangeLog: 2017-05-09 Trevor Saunders * cfganal.c (mark_dfs_back_edges): Replace manual stack with auto_vec. (post_order_compute): Likewise. (inverted_post_order_compute):

[PATCH 05/13] allow constructing a auto_vec with a preallocation, and a possibly larger actual allocation size

From: Trevor Saunders This allows us to set the capacity of the vector when we construct it, and still use a stack buffer when the size is small enough. gcc/ChangeLog: 2017-05-09 Trevor Saunders * genrecog.c (int_set::int_set):

[PATCH 03/13] store the bitmap_head within the auto_bitmap

From: Trevor Saunders This gets rid of one allocation per bitmap. Often the bitmap_head is now on the stack, when it isn't its part of some other struct on the heap instead of being refered to by that struct. On 64 bit platforms this will increase the size of such

[PATCH 00/13] misc data structure stuff

From: Trevor Saunders Hi, this is sort of a grab bag, but mostly improving bitmaps and auto_vec, and then using them in more places. Individually patches commit messages should explain in more detail where needed. patches individually bootstrapped and regtested on

[PATCH 02/13] improve bitmap / sbitmap compatability of bitmap_set_bit

From: Trevor Saunders This make the sbitmap version return true if the bit was previously unset to make it similar to the bitmap version. gcc/ChangeLog: 2017-05-09 Trevor Saunders * sbitmap.h (bitmap_set_bit): Return bool

[PATCH 01/13] improve safety of freeing bitmaps

From: Trevor Saunders There's two groups of changes here, first taking a sbitmap &, so that we can assign null to the pointer after freeing the sbitmap to prevent use after free through that pointer. Second we define overloads of sbitmap_free and bitmap_free taking

[Bug libstdc++/79136] read outside of buffer in char* std::__copy_move<false, false, std::random_access_iterator_tag>::__copy_m(unsigned char const*, unsigned char const*,

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79136 --- Comment #1 from Jonathan Wakely --- Are you sure this is not just a bug in Draco's use of the std::lib? I'll try checking out the code and building it with _GLIBCXX_DEBUG defined, and see if I can reproduce the crash.

[Patch, fortran] PR80442 Handle DATA statement with iteration var in array slice

Hello everyone, since everybody seems to be submitting patches the last few days, I thought I might as well :) Attached is a patch that makes the compiler capable of dealing with implied do variables in array slices in data statements. The copying of the expressions is necessary since

Re: [PATCH] prevent -Wno-system-headers from suppressing -Wstringop-overflow (PR 79214)

On 05/09/2017 02:01 PM, Rainer Orth wrote: Andreas Schwab writes: I see these regressions on ia64: FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c -std=gnu++11 (test for excess errors) Excess errors:

[Bug c++/70979] [C++14] g++ falsely accepts constexpr function returning a lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70979 --- Comment #7 from Jason Merrill --- Author: jason Date: Tue May 9 20:37:51 2017 New Revision: 247814 URL: https://gcc.gnu.org/viewcvs?rev=247814=gcc=rev Log: PR c++/70979 - literal class and closure types * class.c

[Bug c++/66297] [C++14] [DR 1684] constexpr non-static member functions of non-literal types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66297 --- Comment #7 from Jason Merrill --- Author: jason Date: Tue May 9 20:37:44 2017 New Revision: 247813 URL: https://gcc.gnu.org/viewcvs?rev=247813=gcc=rev Log: PR c++/66297, DR 1684 - literal class and constexpr member fns *

C++ PATCH for testsuite failures with -std=c++17

For C++17 aggregate bases, we have started adding base fields for empty bases. The code for calculating whether a class is standard layout needs to ignore these. The C++17 mode diagnostic for direct-enum-init1.C was incorrect. Tested x86_64-pc-linux-gnu, applying to trunk. commit

C++ PATCHes for c++/66297 and 70979, literal type issues

66297: C++14 removed the requirement that a constexpr member function must be a member of a literal class. 70979: We were failing to treat a C++14 lambda as non-literal; they are only literal with the constexpr lambda addition in C++17. Tested x86_64-pc-linux-gnu, applying to trunk. commit

Trivial iter_swap cleanup

Hi A trivial code simplification in a pre-C++11 piece of code. Ok to commit ? François diff --git a/libstdc++-v3/include/bits/stl_algobase.h b/libstdc++-v3/include/bits/stl_algobase.h index d15be63..a33dde2 100644 --- a/libstdc++-v3/include/bits/stl_algobase.h +++

[Bug c++/66297] [C++14] [DR 1684] constexpr non-static member functions of non-literal types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66297 --- Comment #6 from Jason Merrill --- (In reply to Freddie Chopin from comment #5) > Any chance for merging the fix for GCC 7? It would be a pity to wait for a > fixed release for another year... I'll put it in 7.2.

[Bug c++/80670] Member specialization of alias declaration from different namespace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80670 TC changed: What|Removed |Added CC||rs2740 at gmail dot com --- Comment #2 from TC

avoid remove of call when splitting block for inlining

We used to split the inlined-into block at (= after) the call, and then remove the call from the first block to insert it in the second. The removal may cause unnecessary and unrecoverable resetting of debug insns: we do not generate debug temps for calls. Avoid the remove-and-reinsert dance by

Re: Bump version namespace and remove _Rb_tree useless template parameter

On 05/05/2017 15:08, Jonathan Wakely wrote: On 04/05/17 22:16 +0200, François Dumont wrote: Hi Here is the patch to remove the useless _Is_pod_comparator _Rb_tree_impl template parameter. As this is an ABI breaking change it is limited to the versioned namespace mode and the patch also

Re: [PATCH] prevent -Wno-system-headers from suppressing -Wstringop-overflow (PR 79214)

Andreas Schwab writes: > I see these regressions on ia64: > > FAIL: c-c++-common/Wsizeof-pointer-memaccess2.c -std=gnu++11 (test for > excess errors) > Excess errors: > /usr/local/gcc/gcc-20170508/gcc/testsuite/c-c++-common/Wsizeof-pointer-memaccess2.c:11:53: > warning: 'void*

Re: [PATCH, rs6000] Add x86 instrinsic headers to GCC PPC64LE taget

On Tue, 2017-05-09 at 12:23 -0500, Segher Boessenkool wrote: > Hi! > > On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote: > > Thus I would like to restrict this support to PowerPC > > targets that support VMX/VSX and PowerISA-2.07 (power8) and later. > > What happens if you run it on

[Bug c/35443] [4.2/4.3/4.4 regression] Completely broken diagnostic with bind_expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35443 Bug 35443 depends on bug 35441, which changed state. Bug 35441 Summary: pretty-printer cannot handle some expressions https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441 What|Removed |Added

[Bug c/35442] [4.2/4.3/4.4 Regression] Completely broken diagnostic with view_convert_expr

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35442 Bug 35442 depends on bug 35441, which changed state. Bug 35441 Summary: pretty-printer cannot handle some expressions https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441 What|Removed |Added

[Bug c/35742] [4.3 regression] Broken diagnostic: 'goto_expr' not supported by pp_c_expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35742 Bug 35742 depends on bug 35441, which changed state. Bug 35441 Summary: pretty-printer cannot handle some expressions https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441 What|Removed |Added

[Bug c/35441] pretty-printer cannot handle some expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441 Volker Reichelt changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/35441] pretty-printer cannot handle some expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35441 --- Comment #11 from Volker Reichelt --- Author: reichelt Date: Tue May 9 19:09:22 2017 New Revision: 247810 URL: https://gcc.gnu.org/viewcvs?rev=247810=gcc=rev Log: PR c/35441 * c-pretty-print.c (c_pretty_printer::expression):

[PATCH] make RTL/TREE/IPA dump kind an index

Currently, the TDF_foo flags serve 3 purposes: 1) what kind of dump 2) how detailed to print it 3) auxiliary message control This addresses #1, which currently uses a bit mask of TDF_{TREE,RTL,IPA}, of which exactly one must be set. The patch changes things so that these are now an index

Re: [PATCH, rs6000] Fix vec_xl and vec_xst intrinsics for P8

On May 9, 2017, at 9:58 AM, Segher Boessenkool wrote: > > Hi! > > On Thu, May 04, 2017 at 04:35:10PM -0500, Bill Schmidt wrote: >> In an earlier patch, I changed vec_xl and vec_xst to make use of new >> POWER9 instructions when loading or storing vector short/char

[Bug target/80695] gratuitous use of stxvx to store multiple pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80695 --- Comment #1 from acsawdey at gcc dot gnu.org --- Note that compiling with -fno-tree-slp-vectorize results in this much better code: _IO_new_file_overflow: ld 9,8(3) ld 10,64(3) cmpld 7,9,10 beq 7,.L2 ld

[Bug target/80695] gratuitous use of stxvx to store multiple pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80695 Bill Schmidt changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot gnu.org

[Bug target/80695] gratuitous use of stxvx to store multiple pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80695 Bill Schmidt changed: What|Removed |Added Target Milestone|7.2 |8.0

[Bug fortran/80696] New: [8 Regression] New Failures to do with matmul

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80696 Bug ID: 80696 Summary: [8 Regression] New Failures to do with matmul Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [1/2] PR 78736: New warning -Wenum-conversion

On 05/09/2017 07:24 AM, Prathamesh Kulkarni wrote: ping https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00161.html Thanks, Prathamesh On 3 May 2017 at 11:30, Prathamesh Kulkarni wrote: On 3 May 2017 at 03:28, Martin Sebor wrote: On 05/02/2017

Re: [patch, libfortran] Fix PR 80687l build failure on nvptx

On Tue, May 9, 2017 at 8:35 PM, Thomas Koenig wrote: > Hello world, > > the attached patch hopefully fixes the build failure on nvptx introduced > by my recent matmul library patch. It uses malloc/free if VLAs do not > work. > > Thomas S., does this fix the problem? > >

[Bug target/80695] New: gratuitous use of stxvx to store multiple pointers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80695 Bug ID: 80695 Summary: gratuitous use of stxvx to store multiple pointers Product: gcc Version: 7.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[patch, libfortran] Fix PR 80687l build failure on nvptx

Hello world, the attached patch hopefully fixes the build failure on nvptx introduced by my recent matmul library patch. It uses malloc/free if VLAs do not work. Thomas S., does this fix the problem? Tested on x86_64 to make sure that the matmul tests still pass; full regression test still in

[Bug testsuite/80643] NA->FAIL: gcc.dg/pr79214.c gcc.dg/pr79222.c gcc.dg/pr79223.c gcc.dg/tree-ssa/builtins-folding-gimple-ub.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80643 --- Comment #6 from Martin Sebor --- Author: msebor Date: Tue May 9 17:32:59 2017 New Revision: 247808 URL: https://gcc.gnu.org/viewcvs?rev=247808=gcc=rev Log: gcc/testsuite/ChangeLog: PR testsuite/80643 *

[Bug testsuite/80643] NA->FAIL: gcc.dg/pr79214.c gcc.dg/pr79222.c gcc.dg/pr79223.c gcc.dg/tree-ssa/builtins-folding-gimple-ub.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80643 Martin Sebor changed: What|Removed |Added Keywords||diagnostic Status|ASSIGNED

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #10 from Marek Polacek --- Removing the fold() call doesn't regress anything, btw.

Re: [PATCH, rs6000] Add x86 instrinsic headers to GCC PPC64LE taget

Hi! On Mon, May 08, 2017 at 09:49:57AM -0500, Steven Munroe wrote: > Thus I would like to restrict this support to PowerPC > targets that support VMX/VSX and PowerISA-2.07 (power8) and later. What happens if you run it on an older machine, or as BE or 32-bit, or with vectors disabled? > So I

Re: [patch, fortran] Reduce stack use in blocked matmul

Am 09.05.2017 um 12:43 schrieb Andreas Schwab: On Mai 05 2017, Thomas Koenig wrote: @@ -227,6 +226,17 @@ sinclude(`matmul_asm_'rtype_code`.m4')dnl if (m == 0 || n == 0 || k == 0) return; + /* Adjust size of t1 to what is needed. */ +

[Bug sanitizer/80386] UBSAN: false positive - constant folding and reassosiation before instrumentation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80386 Marek Polacek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #9 from Marek Polacek --- Well, I hope we're not. Very much related: PR80386.

[Bug c++/80186] ICE on C++ code with invalid constructor: Segmentation fault (program cc1plus)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80186 Paolo Carlini changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/80186] ICE on C++ code with invalid constructor: Segmentation fault (program cc1plus)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80186 --- Comment #3 from paolo at gcc dot gnu.org --- Author: paolo Date: Tue May 9 16:56:34 2017 New Revision: 247807 URL: https://gcc.gnu.org/viewcvs?rev=247807=gcc=rev Log: /cp 2017-05-09 Paolo Carlini PR

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #8 from Jakub Jelinek --- But we ideally shouldn't be folding anything until we actually c_fully_fold or cp_fold recursively, starting with the leafs. Most of the folders heavily rely on that.

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #7 from Marek Polacek --- I.e. I'm worried we could trigger the endless recursion also if we happen to call fold() on that expression via a different path than from save_expr.

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #6 from Marek Polacek --- Yeah, it helps with this particular testcase (and I agree we want to get rid of that fold() call in save_expr -- I'll take care of it), but I wonder if this issue is something separate: starting with r230506

Re: [Patch, Fortran, OOP] PR 79311: ICE in generate_finalization_wrapper, at fortran/class.c:1992

On Tue, May 09, 2017 at 09:18:42AM -0700, Jerry DeLisle wrote: > > Yes Ok and thanks for patch. The lock_7 is fixed today and I did not see the > mvbits fail yesterday. Regardlessm unrelated. > mvbits_7 is a victim of stupid by non-Fortran committers.

Re: [PATCH, Fortran] PR 80668: wrong error message with -finit-derived

> Le 9 mai 2017 à 18:15, Fritz Reese a écrit : > >> (1) you don’t need the lines (as in "please don’t use them") >> >> + >> +! { dg-final { cleanup-modules "pr80668" } } > > I will remove the "dg-final" lines. > >> >> (2) I don’t understand the comments after

Re: [PATCH, GCC/ARM, Stage 1] Enable Purecode for ARMv8-M Baseline

Hi, On 4 May 2017 at 11:05, Ramana Radhakrishnan wrote: > On Thu, May 04, 2017 at 09:50:42AM +0100, Prakhar Bahuguna wrote: > > >> > >> > Otherwise ok. Please respin and test with an armhf thumb32 bootstrap >> > and regression test run. >> > >> > regards >> >

Re: [PATCH, Fortran] PR 80668: wrong error message with -finit-derived

On 05/09/2017 08:37 AM, Fritz Reese wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80668 > > All, > > The following fixes a bug exposed in PR 80668 in which the compiler > attempted to generate an initializer for components of derived types > with the POINTER attribute when compiling with

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #5 from Jakub Jelinek --- To expand on that, I think we want to drop that call from there and instead be able to simplify somehow a SAVE_EXPR if after c_fully_fold or cp_fold it becomes simple enough not to require any saving.

[Bug sanitizer/80536] [6/7/8 Regression] UBSAN: compile time segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80536 --- Comment #4 from Jakub Jelinek --- Would dropping the fold call from save_expr fix this?

Re: [Patch, Fortran, OOP] PR 79311: ICE in generate_finalization_wrapper, at fortran/class.c:1992

On 05/08/2017 02:16 PM, Janus Weil wrote: > Hi all, > > the attached patch fixes an ICE-on-valid problem with finalization by > making sure that the finalization procedures are properly resolved. > > In the test case, the finalizer of the component type was not being > resolved if the

Re: [PATCH, Fortran] PR 80668: wrong error message with -finit-derived

> (1) you don’t need the lines (as in "please don’t use them") > > + > +! { dg-final { cleanup-modules "pr80668" } } I will remove the "dg-final" lines. > > (2) I don’t understand the comments after 'INTEGER,DIMENSION(:),POINTER :: > dist’. (2) Sorry, the comments were meant to show the error

  1   2   3   >