[Bug fortran/70233] New: Missing diagnostic in array constructor, different size strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70233 Bug ID: 70233 Summary: Missing diagnostic in array constructor, different size strings Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal

[PATCH] Fix 70199

The problem here is that void* labels[] = { &, &, & }; gets gimplified to labels = *.LC0; but .LC0 is not in the set of local decls, so that when copy_forbidden is called during sra versioning we fail to forbid the copy. We could set a different flag, but I think it's easiest to

[Bug middle-end/70199] [5/6 Regression] Crash at -O2 when using labels.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70199 Richard Henderson changed: What|Removed |Added Status|NEW |ASSIGNED CC|

[Bug c++/15272] lookup, dependent base

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15272 Martin Sebor changed: What|Removed |Added Last reconfirmed|2013-01-19 00:00:00 |2016-3-14 CC|

[Bug c++/55992] constexpr static member function not recognised in templated using statement

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55992 Martin Sebor changed: What|Removed |Added Last reconfirmed|2013-01-15 00:00:00 |2016-3-14 CC|

[Bug sanitizer/70147] [6 Regression] testcase from hana testsuite gets miscompiled with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70147 --- Comment #15 from Bernd Edlinger --- Yep, maybe this would be a compromise: Index: cp-ubsan.c === --- cp-ubsan.c (revision 234184) +++ cp-ubsan.c (working copy) @@ -285,6

[Bug rtl-optimization/69941] bogus zero_extend transformation in postreload on aarch64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69941 --- Comment #7 from Bernd Schmidt --- Author: bernds Date: Tue Mar 15 03:14:38 2016 New Revision: 234210 URL: https://gcc.gnu.org/viewcvs?rev=234210=gcc=rev Log: Backport PR69941 patch from mainline. PR rtl-optimization/69941 *

[Bug rtl-optimization/69941] bogus zero_extend transformation in postreload on aarch64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69941 --- Comment #6 from Bernd Schmidt --- Author: bernds Date: Tue Mar 15 03:10:31 2016 New Revision: 234209 URL: https://gcc.gnu.org/viewcvs?rev=234209=gcc=rev Log: Backport PR69941 patch from mainline. PR rtl-optimization/69941 *

[Bug c++/55004] [meta-bug] constexpr issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004 Bug 55004 depends on bug 53792, which changed state. Bug 53792 Summary: [C++11] improving compiler-time constexpr evaluation https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53792 What|Removed |Added

[Bug c++/53792] [C++11] improving compiler-time constexpr evaluation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53792 Martin Sebor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/53792] [C++11] improving compiler-time constexpr evaluation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53792 --- Comment #10 from Martin Sebor --- Author: msebor Date: Tue Mar 15 03:05:17 2016 New Revision: 234208 URL: https://gcc.gnu.org/viewcvs?rev=234208=gcc=rev Log: PR c++/53792 - [C++11] improving compiler-time constexpr evaluation

[Bug c++/53792] [C++11] improving compiler-time constexpr evaluation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53792 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Known to

Re: C++ PATCH for range-for tweak

On 03/14/2016 05:30 PM, Florian Weimer wrote: * Jason Merrill: P08184R0: Generalizing the Range-Based For Loop How can one resolve this reference? It's obviously not a PR number in GCC Bugzilla. I found this after some searching:

Re: [PATCH] PR69195, Reload confused by invalid reg equivs

On Mon, Mar 14, 2016 at 01:00:39PM -0600, Jeff Law wrote: > Right. Tolerant as in not crash. So can someone please approve my ira.c:indirect_jump_optimize patch? I'm not quite audacious enough to claim it is obvious. The original is at https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00720.html,

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #15 from Wink Saville --- (In reply to H.J. Lu from comment #14) > (In reply to Wink Saville from comment #13) > > > Compiler should be free to use rbp in anyway it sees fit. Spec shouldn't > > > say anything other than rbp is

[Bug target/70188] [4.9/5/6 Regression] gcc 4.9+ miscompiles code on hppa

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70188 John David Anglin changed: What|Removed |Added Component|ipa |target --- Comment #8 from John

[Bug fortran/70231] Runtime error: Different CHARACTER lengths in array constructor with allocatable array and -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70231 Jerry DeLisle changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

Re: [RFA][PATCH][PR tree-optimization/64058] Improve and stabilize sorting of coalesce pairs

On Mon, Mar 14, 2016 at 04:32:06PM -0600, Jeff Law wrote: > On 03/11/2016 03:02 AM, Richard Biener wrote: > > > > > >For the other part I noticed a few things > > 1) having a bitmap_count_ior_bits () would be an improvement > Yea, I almost built one. That's easy enough to add. > > > 2) you

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #14 from H.J. Lu --- (In reply to Wink Saville from comment #13) > > Compiler should be free to use rbp in anyway it sees fit. Spec shouldn't > > say anything other than rbp is special to compiler. > > If the compiler does decide to

[Bug target/70232] excessive stack usage with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70232 --- Comment #1 from Andrew Pinski --- >I have only tested on 32-bit ARM, Looks only to be an 32bit ARM issue. AARCH64 both LP64 and ILP32 does not have a stack size issue. For both of those we get: stp x29, x30, [sp, -128]! So

[Bug c/70232] New: excessive stack usage with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70232 Bug ID: 70232 Summary: excessive stack usage with -O2 Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

Re: [PATCH] genrecog: Fix crash on invalid input

On 03/14/2016 09:00 PM, Segher Boessenkool wrote: There is just the single caller, and pred is set right before the call there. How about this patch, then? Looks alright. Bernd

Re: [PATCH, testsuite] Fix ifcvt-4.c for PowerPC

On Mon, Mar 14, 2016 at 7:35 PM, Jeff Law wrote: > On 03/14/2016 02:23 PM, Pat Haugen wrote: >> >> As stated in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68232, this >> test needs -misel on powerpc to pass. Verified the following fixes the >> test on both

[Bug rtl-optimization/70224] [6 regression] ICE: RTL flag check: CROSSING_JUMP_P used with unexpected rtx code 'insn' in relax_delay_slots, at reorg.c:3310

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70224 --- Comment #8 from Jeffrey A. Law --- I've got the obvious patch bootstrap testing on sparc linux via qemu in progress. It'll be interesting to see how long this takes.

Re: [PATCH, testsuite] Fix ifcvt-4.c for PowerPC

On 03/14/2016 02:23 PM, Pat Haugen wrote: As stated in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68232, this test needs -misel on powerpc to pass. Verified the following fixes the test on both powerpc64/powerpc64le. Ok for trunk? -Pat testsuite/ChangeLog: 2016-03-14 Pat Haugen

[Bug c++/70182] c++filt fails to demangle _ZNSt17_Function_handlerIFSt4pairImjEjEZN5folly12addBenchmarkI3$_0EENSt9enable_ifIXeqsr5boost14function_types14function_arityIDTadsrT_onclEEE5valueLi2EEvE4typ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182 --- Comment #9 from Ian Lance Taylor --- Yes. The relevant bits in the mangling ABI are ::= [gs] ::= sr ::= srN + E ::= [gs] sr + E ::= ::= on ::= on ::= dn ::= ::= [ ] ::= srT_ must be sr ,

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #13 from Wink Saville --- (In reply to H.J. Lu from comment #12) > (In reply to Wink Saville from comment #11) > > > > The rsp is always saved/restored by the hardware, and your struct frame > > > > pointer provides access to it so

Re: [PATCH, 4/16] Implement -foffload-alias

On 14/03/16 14:16, Tom de Vries wrote: On 02/12/15 10:58, Jakub Jelinek wrote: On Fri, Nov 27, 2015 at 01:03:52PM +0100, Tom de Vries wrote: Handle non-declared variables in kernels alias analysis 2015-11-27 Tom de Vries * gimplify.c (gimplify_scan_omp_clauses):

[Bug sanitizer/70147] [6 Regression] testcase from hana testsuite gets miscompiled with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70147 --- Comment #14 from Bernd Edlinger --- Hi Jakub, I played a bit with your proposed patch. consider this test case: cat test2.cc struct A { ~A() {} A () {} A (int x) : a (x) {} virtual void f () {} virtual int i () { return 0; } int a; };

Re: [PATCH] Fix PR56365

On March 14, 2016 9:21:25 PM GMT+01:00, Richard Biener wrote: >On March 14, 2016 7:25:31 PM GMT+01:00, Bernhard Reutner-Fischer > wrote: >>On March 14, 2016 12:58:20 PM GMT+01:00, Richard Biener >> wrote: >>>+ >>>+ int

Re: [RFA][PATCH][PR tree-optimization/64058] Improve and stabilize sorting of coalesce pairs

On 03/11/2016 03:02 AM, Richard Biener wrote: For the other part I noticed a few things 1) having a bitmap_count_ior_bits () would be an improvement Yea, I almost built one. That's easy enough to add. 2) you might end up with redundant work(?) as you are iterating over SSA name

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #12 from H.J. Lu --- (In reply to Wink Saville from comment #11) > > > The rsp is always saved/restored by the hardware, and your struct frame > > > pointer provides access to it so no problem there. It is special because > > > when

[Bug middle-end/70219] [6 Regression] ICE: in delete_move_and_clobber, at lra-constraints.c:5864 with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70219 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/70219] [6 Regression] ICE: in delete_move_and_clobber, at lra-constraints.c:5864 with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70219 --- Comment #5 from Jakub Jelinek --- Author: jakub Date: Mon Mar 14 22:19:32 2016 New Revision: 234201 URL: https://gcc.gnu.org/viewcvs?rev=234201=gcc=rev Log: PR middle-end/70219 * lra-constraints.c (delete_move_and_clobber):

[Bug sanitizer/70147] [6 Regression] testcase from hana testsuite gets miscompiled with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70147 --- Comment #13 from Jakub Jelinek --- See my mail to gcc-patches. According to Jonathan, calling i() is invalid, which your patch would not catch. And, the virtual vptrs should be at least initialized in the in-chrg ctor even if we'd want to

[Bug libgcc/66382] POWER8 Vector optimized implementation of __float128 (IEEE754 128-bit Binary Floating Point)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66382 --- Comment #4 from joseph at codesourcery dot com --- On Mon, 14 Mar 2016, dan.parrot at mail dot com wrote: > However, I am still unable to get gcc to compile a very simple program > when passed the -msoft-float option. Here is the program

Re: [PATCH] extend.texi: Expand on the perils of using the 'leaf' attribute.

On 03/14/2016 12:40 PM, Carlos O'Donell wrote: Using the 'leaf' attribute is difficult in certain use cases, and the documentation rightly points out that signals is one such problem. We should additionally document the following caveats: * Indirect function resolvers (thanks to Florian Weimer

Re: [PATCH] c++/67376 Comparison with pointer to past-the-end, of array fails inside constant expression

On Mon, Mar 14, 2016 at 03:25:07PM -0600, Martin Sebor wrote: > PR c++/67376 - [5/6 regression] Comparison with pointer to past-the-end > of array fails inside constant expression > PR c++/70170 - [6 regression] bogus not a constant expression error comparing > pointer to array to null

[Bug target/70117] ppc long double isinf() is wrong?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70117 --- Comment #11 from joseph at codesourcery dot com --- On Mon, 14 Mar 2016, rguenth at gcc dot gnu.org wrote: > but it will end up with libcalls for isinf, isfinite and isnormal for > IBM extended double. I'm told glibc does the right thing

[Bug c++/53181] static_assert sees as non constant the comparison between a constexpr and a template argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53181 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org Known to

[Bug fortran/70231] New: Runtime error: Different CHARACTER lengths in array constructor with allocatable array and -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70231 Bug ID: 70231 Summary: Runtime error: Different CHARACTER lengths in array constructor with allocatable array and -O0 Product: gcc Version: 5.3.0 Status: UNCONFIRMED

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #11 from Wink Saville --- (In reply to H.J. Lu from comment #10) > (In reply to Wink Saville from comment #9) > > (In reply to H.J. Lu from comment #8) > > > (In reply to Wink Saville from comment #7) > > > > > > > > In my opinion,

Re: [PATCH] Fix LRA ICE (PR middle-end/70219)

On 03/14/2016 03:32 PM, Jakub Jelinek wrote: Hi! The newly added assert in delete_move_and_clobber requires dregno > 0, but dregno == 0 is also normal (e.g. in the testcase below we get dregno == 0, because it uses %rax). Only dregno < 0 is special and we shouldn't see it here.

[C++ PATCH] Fix -fsanitize=vptr (PR c++/70147)

Hi! My recent patch for PR70035 broke -fsanitize=vptr, the early clearing of _vptr.* pointers in the objects can crash in constructors with _vtt_parm parameter. This patch arranges to use in them *_vtt_parm instead the base vptr (which we clear, instead of initialize). The first testcase is

[Bug tree-optimization/68714] [6 Regression] less folding of vector comparison

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68714 Richard Henderson changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[PATCH] Fix LRA ICE (PR middle-end/70219)

Hi! The newly added assert in delete_move_and_clobber requires dregno > 0, but dregno == 0 is also normal (e.g. in the testcase below we get dregno == 0, because it uses %rax). Only dregno < 0 is special and we shouldn't see it here. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for

[Bug c++/70228] insufficient detail in diagnostics for a constexpr out of bounds array subscript

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70228 --- Comment #2 from Martin Sebor --- Patch posted for review: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00796.html

[Bug c++/60760] arithmetic on null pointers should not be allowed in constant expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60760 --- Comment #6 from Martin Sebor --- Patch posted for review: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00796.html

[Bug c++/70172] incorrect reinterpret_cast from integer to pointer error on invalid constexpr initialization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70172 --- Comment #4 from Martin Sebor --- Patch posted for review: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00796.html

[Bug c++/70170] [6 regression] bogus not a constant expression error comparing pointer to array to null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70170 Martin Sebor changed: What|Removed |Added Assignee|mpolacek at gcc dot gnu.org|msebor at gcc dot gnu.org ---

Re: C++ PATCH for range-for tweak

* Jason Merrill: > P08184R0: Generalizing the Range-Based For Loop How can one resolve this reference? It's obviously not a PR number in GCC Bugzilla. I found this after some searching: But it lacks the additional

[Bug c++/67376] [5/6 regression] Comparison with pointer to past-the-end of array fails inside constant expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67376 --- Comment #16 from Martin Sebor --- Patch for the outstanding issues noted in comment #10 has been posted for review: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00796.html

Re: [PATCH] 69517 - [5/6 regression] SEGV on a VLA with excess initializer elements

Ping: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00441.html On 03/06/2016 06:38 PM, Martin Sebor wrote: GCC 4.9 had added support for C++ VLAs as specified in WG21 document N3639 expected to be included in C++ 14. However, WG21 ultimately decided not to include N3639 in C++ 14 and the G++

[PATCH] c++/67376 Comparison with pointer to past-the-end, of array fails inside constant expression

The attached patch fixes the outstanding cases mentioned in comment 10 on bug c++/67376. While testing the fix I uncovered a number of other related problems without which the test would have been incomplete. They include: PR c++/70170 - [6 regression] bogus not a constant expression error

[Bug bootstrap/67728] Build fails when cross-compiling with in-tree GMP and ISL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67728 --- Comment #14 from Marc Glisse --- Note that I don't think we ever got a proper bug report for GMP. Verified instructions on how to reproduce the issue with just the latest version of GMP (without having to download the sources of mpfr, mpc,

[Bug libgcc/66382] POWER8 Vector optimized implementation of __float128 (IEEE754 128-bit Binary Floating Point)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66382 --- Comment #3 from dan.parrot at mail dot com --- I am trying to configure gcc so that instead of generating instructions that use the hardware floating point unit, it will generate instructions that utilize integer operations to emulate

[Bug regression/70230] New: 11 test regressions when building GCC 6 with --enable-default-ssp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70230 Bug ID: 70230 Summary: 11 test regressions when building GCC 6 with --enable-default-ssp Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/68714] [6 Regression] less folding of vector comparison

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68714 --- Comment #8 from Richard Henderson --- Author: rth Date: Mon Mar 14 20:48:15 2016 New Revision: 234196 URL: https://gcc.gnu.org/viewcvs?rev=234196=gcc=rev Log: PR tree-opt/68714 * tree-ssa-reassoc.c (ovce_extract_ops,

[Bug bootstrap/67728] Build fails when cross-compiling with in-tree GMP and ISL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67728 --- Comment #13 from Brett Neumeier --- OK, then it would make sense to have a documentation fix for GCC that specifies those exact versions for GMP, MPC, and MPFR as the versions that must be used, rather than claiming -- inaccurately! --

[Bug libgcc/66382] POWER8 Vector optimized implementation of __float128 (IEEE754 128-bit Binary Floating Point)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66382 --- Comment #2 from Steven Munroe --- What is the issue? You want to configure __float128 without also configuring altivec/VMX/VSX? The PowerPC 64-bit ABI is defined to pass __float128 values in 128-bit vector registers and return _float128

[Bug c++/70229] error: constexpr constructor does not have empty body

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70229 --- Comment #1 from baoshan --- The error is triggered by the typedef clause, but it is valid according standard C++11 http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3376.pdf: ... — either its function-body shall be = default, or the

[Bug c++/70182] c++filt fails to demangle _ZNSt17_Function_handlerIFSt4pairImjEjEZN5folly12addBenchmarkI3$_0EENSt9enable_ifIXeqsr5boost14function_types14function_arityIDTadsrT_onclEEE5valueLi2EEvE4typ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182 --- Comment #8 from Markus Trippelsdorf --- (In reply to Ian Lance Taylor from comment #7) > For the record, I've fixed these cases in > github.com/ianlancetaylor/demangle. Looking at the patch there should show > how to fix it elsewhere. > >

[Bug c++/70229] New: error: constexpr constructor does not have empty body

es not have empty body } | ^ $ ./xgcc -v Using built-in specs. COLLECT_GCC=./xgcc Target: x86_64-pc-linux-gnu Configured with: ../gcc/configure --enable-languages=c,c++ Thread model: posix gcc version 6.0.0 20160314 (experimental) (GCC)

[Bug c++/70228] insufficient detail in diagnostics for a constexpr out of bounds array subscript

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70228 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug c++/70228] New: insufficient detail in diagnostics for a constexpr out of bounds array subscript

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70228 Bug ID: 70228 Summary: insufficient detail in diagnostics for a constexpr out of bounds array subscript Product: gcc Version: 6.0 Status: UNCONFIRMED Severity:

[PATCH, testsuite] Fix ifcvt-4.c for PowerPC

As stated in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68232, this test needs -misel on powerpc to pass. Verified the following fixes the test on both powerpc64/powerpc64le. Ok for trunk? -Pat testsuite/ChangeLog: 2016-03-14 Pat Haugen * gcc.dg/ifcvt-4.c:

Re: [PATCH] Fix PR56365

On March 14, 2016 7:25:31 PM GMT+01:00, Bernhard Reutner-Fischer wrote: >On March 14, 2016 12:58:20 PM GMT+01:00, Richard Biener > wrote: >> >>I am testing the following patch to fix the regression in min/max >>detection introduced by comparison

[Bug target/70179] PPC64 ICE with -mabi=ieeelongdouble and long double complex

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70179 David Edelsohn changed: What|Removed |Added Target|powerpc64* |powerpc64*-linux

[Bug target/70131] PowerPC ISA 2.07 is inefficient at doint (float)(int)x.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70131 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: [PATCH] genrecog: Fix crash on invalid input

On Mon, Mar 14, 2016 at 01:41:38PM -0500, Segher Boessenkool wrote: > On Mon, Mar 14, 2016 at 06:39:12PM +0100, Bernd Schmidt wrote: > > On 03/14/2016 04:38 PM, Segher Boessenkool wrote: > > >If your machine description refers to a non-existent predicate genrecog > > >crashes. This fixes it. > >

[Bug sanitizer/70147] [6 Regression] testcase from hana testsuite gets miscompiled with -fsanitize=undefined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70147 --- Comment #12 from Bernd Edlinger --- I think it is normal, that A's vptr is initialized first to an A which means that f points to A::f and i points to A::i. these overloads are usable while A's constructor runs. The vptr is later changed to

C++ PATCH for range-for tweak

A proposal accepted at the last meeting allows the deduced iterator and end variables in range-based for to have different types, as long as they can be compared. This is a very simple change, limited to C++1z mode, and desired by some of the heaviest users of concepts, so I'm going to go

[Bug target/70220] [x86] interrupt attribute optionally needs to provide read, write and control the set of saved registers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220 --- Comment #10 from H.J. Lu --- (In reply to Wink Saville from comment #9) > (In reply to H.J. Lu from comment #8) > > (In reply to Wink Saville from comment #7) > > > > > > In my opinion, even if rbp is special, it still needs to be available

[Bug c++/70182] c++filt fails to demangle _ZNSt17_Function_handlerIFSt4pairImjEjEZN5folly12addBenchmarkI3$_0EENSt9enable_ifIXeqsr5boost14function_types14function_arityIDTadsrT_onclEEE5valueLi2EEvE4typ

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70182 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com --- Comment #7

Re: [AArch64] Emit square root using the Newton series

Evandro Menezes wrote: > > I got the scalar version going, but I'm stuck with the vector version. > As you can see above, I need to use the complement of the mask produced > by FCMEQ to squelch the offending vector element. However, the way in > which FCMEQ is defined in

[Bug bootstrap/67728] Build fails when cross-compiling with in-tree GMP and ISL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67728 --- Comment #12 from Bernd Edlinger --- It is on purpose that the in-tree gmp is configured to use no assembly, but the in-tree configuration does not really work with gmp-6.1.0, and apparently disables the assembly only half-way. It is not

[Bug c++/70194] [6 regression] missing -Waddress on constexpr pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70194 --- Comment #5 from Marek Polacek --- This patch fixes the missing warning: --- a/gcc/cp/typeck.c +++ b/gcc/cp/typeck.c @@ -4520,14 +4520,16 @@ cp_build_binary_op (location_t location, else result_type = type0; - if

Re: [PATCH] PR69195, Reload confused by invalid reg equivs

On 03/14/2016 03:56 AM, Richard Biener wrote: Undefined? Most likely. But we still have to do something sensible. As Jakub noted, a user could create the problematic code just as easily as DCE/DSE, so IRA probably needs to be tolerant of this situation. So it seems like you're suggesting we

[Bug c++/68722] [4.9/5/6 Regression] internal compiler error: in merge_exception_specifiers, at cp/typeck2.c:2108

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68722 --- Comment #2 from Paolo Carlini --- I wonder if in such cases, where we run out of tokens and we issue: error_at (token->location, "file ends in default argument"); from cp_parser_cache_defarg we should instead use something like a

[Bug fortran/69423] [6 Regression] Invalid optimization with deferred-length character

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69423 Paul Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/68241] [meta-bug] Deferred-length character

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68241 Bug 68241 depends on bug 69423, which changed state. Bug 69423 Summary: [6 Regression] Invalid optimization with deferred-length character https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69423 What|Removed |Added

Re: [PATCH] genrecog: Fix crash on invalid input

On Mon, Mar 14, 2016 at 06:39:12PM +0100, Bernd Schmidt wrote: > On 03/14/2016 04:38 PM, Segher Boessenkool wrote: > >If your machine description refers to a non-existent predicate genrecog > >crashes. This fixes it. > > Might be better to fix the caller? Yeah maybe. The next function that

[PATCH] extend.texi: Expand on the perils of using the 'leaf' attribute.

Using the 'leaf' attribute is difficult in certain use cases, and the documentation rightly points out that signals is one such problem. We should additionally document the following caveats: * Indirect function resolvers (thanks to Florian Weimer for catching this). * Indirect function

Re: [PATCH][PR rtl-optimization/69307] Handle hard registers in modes that span more than one register properly

On 03/14/2016 03:56 AM, Andrey Belevantsev wrote: Thank you for checking this in. I've also tested this patch in the similar way (forcing selective scheduling for 2nd and both schedulers) both on x86-64 and ia64. I've posted the patches for remaining sel-sched PRs just now -- it took some

Re: [gimplefe] [gsoc16] Gimple Front End Project

Hi, On Thu, 10 Mar 2016, Richard Biener wrote: > Then I'd like to be able to re-construct SSA without jumping through > hoops (usually you can get close but if you require copies propagated in > a special way you are basically lost for example). > > Thus my proposal to make the GSoC student

[Bug target/70123] [5 Regression] Miscompilation of cfitsio testcase on s390x-linux starting with r222144

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70123 --- Comment #8 from Bernd Schmidt --- I'll take your comment as approval and install on gcc-5 as well.

Re: [PATCH] Fix PR56365

On March 14, 2016 12:58:20 PM GMT+01:00, Richard Biener wrote: > >I am testing the following patch to fix the regression in min/max >detection introduced by comparison canonicalization like a < 267 >to a <= 266. The patch allows us to identify all four min/max >cases in the

[Bug target/70168] [5 Regression] Wrong code generation in __sync_val_compare_and_swap on PowerPC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70168 --- Comment #7 from Michael Meissner --- Author: meissner Date: Mon Mar 14 18:18:45 2016 New Revision: 234188 URL: https://gcc.gnu.org/viewcvs?rev=234188=gcc=rev Log: [gcc] 2016-03-14 Michael Meissner

[Bug target/70131] PowerPC ISA 2.07 is inefficient at doint (float)(int)x.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70131 --- Comment #4 from Michael Meissner --- Author: meissner Date: Mon Mar 14 18:18:45 2016 New Revision: 234188 URL: https://gcc.gnu.org/viewcvs?rev=234188=gcc=rev Log: [gcc] 2016-03-14 Michael Meissner

[Bug fortran/45076] [OOP] gfortran.dg/dynamic_dispatch_6.f03 ICEs with -fprofile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45076 --- Comment #12 from Michael Meissner --- Author: meissner Date: Mon Mar 14 18:18:45 2016 New Revision: 234188 URL: https://gcc.gnu.org/viewcvs?rev=234188=gcc=rev Log: [gcc] 2016-03-14 Michael Meissner

[Bug target/62281] gcc doesn't conform to Solaris 32-bit ABI by expecting 16-byte stack alignment

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62281 --- Comment #18 from Michael Meissner --- Author: meissner Date: Mon Mar 14 18:18:45 2016 New Revision: 234188 URL: https://gcc.gnu.org/viewcvs?rev=234188=gcc=rev Log: [gcc] 2016-03-14 Michael Meissner

Re: [04/05] Fix PR 69032

On Mon, 14 Mar 2016, Andrey Belevantsev wrote: > We fail to find the proper seqno for the fresh bookkeeping copy in this PR. > The problem is that in get_seqno_by_preds we are iterating over bb from the > given insn backwards up to the first bb insn. We skip the initial insn when > iterating over

[Bug target/70131] PowerPC ISA 2.07 is inefficient at doint (float)(int)x.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70131 --- Comment #3 from Michael Meissner --- Author: meissner Date: Mon Mar 14 18:06:45 2016 New Revision: 234186 URL: https://gcc.gnu.org/viewcvs?rev=234186=gcc=rev Log: [gcc] 2016-03-11 Michael Meissner PR

[Bug rtl-optimization/70224] [6 regression] ICE: RTL flag check: CROSSING_JUMP_P used with unexpected rtx code 'insn' in relax_delay_slots, at reorg.c:3310

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70224 --- Comment #7 from Jakub Jelinek --- rtx_jump_insn *delay_jump_insn = dyn_cast (delay_insn); if (! delay_jump_insn || !(condjump_p (delay_jump_insn) || condjump_in_parallel_p (delay_jump_insn)))

Re: Is test case with 700k lines of code a valid test case?

On March 14, 2016 4:31:57 PM GMT+01:00, Andrey Tarasevich wrote: >Hi, > >I have a source file with 700k lines of code 99% of which are printf() >statements. Compiling this test case crashes GCC 5.3.0 with >segmentation fault. >Can such test case be considered

[Bug bootstrap/67728] Build fails when cross-compiling with in-tree GMP and ISL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67728 --- Comment #11 from Andrew Roberts --- On Native ARM platform the bootstrap does work with the old in tree GMP 4.3.2, regardless of wether you use none-linux-gnu or armv7l-linux-gnu when configuring GMP. Bulding by patching toplevel Makefile

[Bug rtl-optimization/70224] [6 regression] ICE: RTL flag check: CROSSING_JUMP_P used with unexpected rtx code 'insn' in relax_delay_slots, at reorg.c:3310

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70224 --- Comment #6 from Jeffrey A. Law --- Ah, nevermind, I see where we filter out non-jump insns.

[Bug rtl-optimization/70224] [6 regression] ICE: RTL flag check: CROSSING_JUMP_P used with unexpected rtx code 'insn' in relax_delay_slots, at reorg.c:3310

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70224 --- Comment #5 from Jeffrey A. Law --- Also note that delay_insn may be an INSN or CALL_INSN AFAICT here. So just setting it blindly on DELAY_INSN may not be correct either. I'm still looking at those possibilities.

[Bug driver/70192] -fno-pic doesn't work with --enable-default-pie

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70192 --- Comment #5 from psturm at computervoice dot com --- Created attachment 37962 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37962=edit gcc6 --enable-default-pie I built GCC6 snapshot 03132016 after applying the PIC patch. The test

[Bug bootstrap/67728] Build fails when cross-compiling with in-tree GMP and ISL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67728 --- Comment #10 from Brett Neumeier --- Bernd, I don't think there is any argument that those specific versions of the library dependencies work. My sense is that it is a bug to assert "GNU Multiple Precision Library (GMP) version 4.3.2 (or

  1   2   3   >