https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69009
--- Comment #8 from Jason Merrill ---
Author: jason
Date: Mon Feb 8 19:22:57 2016
New Revision: 233226
URL: https://gcc.gnu.org/viewcvs?rev=233226&root=gcc&view=rev
Log:
PR c++/69009
* pt.c (partial_specialization_p, impartial_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10200
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69009
Jason Merrill changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69657
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
--- Comment #3 from Peter VARGA ---
Dear Jakob,
thank you for the explanation. But honestly, the "definition" when to warn is
in my eyes wrong. Even var++ is reading and then setting the variable in this
case it does NOT make sense!
Just imagin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
--- Comment #8 from Jeffrey A. Law ---
I'd have to look at the current DCE implementation to if it's still relevant --
in the past we used to emit clobbers like this to tell DCE that the clobbered
value is totally written when the writes were spl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68541
--- Comment #9 from Jeffrey A. Law ---
Author: law
Date: Mon Feb 8 19:52:50 2016
New Revision: 233227
URL: https://gcc.gnu.org/viewcvs?rev=233227&root=gcc&view=rev
Log:
PR tree-optimization/68541
* gcc.dg/tree-ssa/split-path-1.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10200
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2016-01-22 00:00:00 |2016-2-8
--- Comment #32 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69209
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Mon Feb 8 20:07:56 2016
New Revision: 233228
URL: https://gcc.gnu.org/viewcvs?rev=233228&root=gcc&view=rev
Log:
PR tree-optimization/69209
* ipa-split.c (split_function):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68721
Bug 68721 depends on bug 69209, which changed state.
Bug 69209 Summary: [6 Regression] ICE at -Os and above on x86_64-linux-gnu
(verify_gimple failed)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69209
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69209
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69139
Adam Butcher changed:
What|Removed |Added
Assignee|abutcher at gcc dot gnu.org|unassigned at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68654
--- Comment #23 from Jeffrey A. Law ---
I don't think it's worth the effort to try and keep that list sorted. I think
we can get what we want with a single walk over the IL just before coalescing.
That addresses the stability issue.
Then we w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69599
--- Comment #8 from vries at gcc dot gnu.org ---
update patch: https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00598.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69707
--- Comment #5 from vries at gcc dot gnu.org ---
updated patch: https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00596.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67153
--- Comment #23 from Nathan Kurz ---
> 1. As a correction: *without* the count takes twice as long to run as with,
>or when using bitset<>.
Oops, I did say that backwards. My tests agree with what you say.
> 2. As a heuristic, favoring a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69657
--- Comment #10 from Jason Merrill ---
Author: jason
Date: Mon Feb 8 22:07:54 2016
New Revision: 233229
URL: https://gcc.gnu.org/viewcvs?rev=233229&root=gcc&view=rev
Log:
PR c++/69657
* name-lookup.c (do_nonmember_using_decl): L
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69657
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69706
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69706
Eric Botcazou changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69283
--- Comment #2 from Patrick Palka ---
Author: ppalka
Date: Mon Feb 8 23:02:50 2016
New Revision: 233230
URL: https://gcc.gnu.org/viewcvs?rev=233230&root=gcc&view=rev
Log:
Fix PR c++/69283 (auto deduction fails when ADL is required)
gcc/cp/Chan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67835
--- Comment #2 from Patrick Palka ---
Author: ppalka
Date: Mon Feb 8 23:02:50 2016
New Revision: 233230
URL: https://gcc.gnu.org/viewcvs?rev=233230&root=gcc&view=rev
Log:
Fix PR c++/69283 (auto deduction fails when ADL is required)
gcc/cp/Chan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69283
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69139
--- Comment #7 from Patrick Palka ---
Author: ppalka
Date: Mon Feb 8 23:06:21 2016
New Revision: 233231
URL: https://gcc.gnu.org/viewcvs?rev=233231&root=gcc&view=rev
Log:
Fix PR c++/69139 (deduction failure with trailing return type)
gcc/cp/Ch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67835
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69139
Patrick Palka changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
--- Comment #14 from Michael Meissner ---
Created attachment 37634
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37634&action=edit
Proposed patch to fix the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
--- Comment #5 from Peter VARGA ---
I do not understand what you mean with "Replace unused++ with unused = unused
+ 1".
How ever. I checked my example code in Compiler Explorer with clang and clang
generates a warning as it should be.
OK. You
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
--- Comment #15 from Michael Meissner ---
Markus Trippelsdorf: Could you try the patch that I attached to the bug? I get
past the point that was failing before, but I get new errors (lto type not the
same in the decnumber library), so I suspect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
--- Comment #16 from Markus Trippelsdorf ---
(In reply to Michael Meissner from comment #15)
> Markus Trippelsdorf: Could you try the patch that I attached to the bug? I
> get past the point that was failing before, but I get new errors (lto typ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
--- Comment #17 from Markus Trippelsdorf ---
And the "lto type not the same in decnumber" issue should go away with
--disable-werror.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69714
--- Comment #6 from dave.anglin at bell dot net ---
On 2016-02-08, at 1:48 PM, pinskia at gcc dot gnu.org wrote:
> Do you know if it fails on the trunk?
I retested trunk (revision 233199). My statement in comment #2 about trunk was
incorrect.
T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69714
Andrew Pinski changed:
What|Removed |Added
Summary|[5 Regression] ffmpeg crc.c |[5/6 Regression] ffmpeg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69714
--- Comment #8 from dave.anglin at bell dot net ---
On 2016-02-08, at 7:07 PM, pinskia at gcc dot gnu.org wrote:
> This might be reproducible on a PowerPC machine too (big-endian rather than
> the
> little-endian version). As it was mentioned i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69724
Bug ID: 69724
Summary: Unnecessary temporary object during std::thread
construction
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69357
--- Comment #3 from ian at gcc dot gnu.org ---
Author: ian
Date: Tue Feb 9 00:34:55 2016
New Revision: 233235
URL: https://gcc.gnu.org/viewcvs?rev=233235&root=gcc&view=rev
Log:
PR go/69537
runtime: Don't refer to _end symbol in shar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69537
--- Comment #8 from ian at gcc dot gnu.org ---
Author: ian
Date: Tue Feb 9 00:34:55 2016
New Revision: 233235
URL: https://gcc.gnu.org/viewcvs?rev=233235&root=gcc&view=rev
Log:
PR go/69537
runtime: Don't refer to _end symbol in shar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69723
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
Manuel López-Ibáñez changed:
What|Removed |Added
CC||developm...@faf-ltd.com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69713
--- Comment #6 from Kazumoto Kojima ---
(In reply to Oleg Endo from comment #5)
> Anyway, I think this could be applied to GCC 5 and GCC 6. Kaz, what do you
> think?
Looks fine to me. Please go ahead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69357
Ian Lance Taylor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69725
Bug ID: 69725
Summary: profiledbootstrap failure due to unsats for isl
functions
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priori
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69722
--- Comment #1 from sandra at gcc dot gnu.org ---
Created attachment 37635
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37635&action=edit
patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69726
Bug ID: 69726
Summary: Bogus warnings with -O3 -Wuninitialized
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69722
--- Comment #2 from sandra at gcc dot gnu.org ---
I'm not seeing the warnings (different version of texinfo?), but I think I've
tracked down the problem to incorrect sectioning added in r225122:
r225122 | rth | 2015-06-29 07:35:19 -0700 (Mon, 29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69722
--- Comment #3 from H.J. Lu ---
(In reply to sandra from comment #2)
> I'm not seeing the warnings (different version of texinfo?), but I think
I am using texinfo-6.0-1.fc23.x86_64.
> Can you verify that the attached patch fixes the warnings?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69722
--- Comment #4 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Tue Feb 9 03:25:30 2016
New Revision: 233236
URL: https://gcc.gnu.org/viewcvs?rev=233236&root=gcc&view=rev
Log:
2016-02-08 Sandra Loosemore
PR other/69722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
Michael Meissner changed:
What|Removed |Added
Assignee|wschmidt at gcc dot gnu.org|meissner at gcc dot
gnu.org
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
Michael Meissner changed:
What|Removed |Added
Attachment #37634|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69727
Bug ID: 69727
Summary: ICE in profiledbootstrap in reg_save_code at
../../gcc/caller-save.c:141
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69707
--- Comment #6 from vries at gcc dot gnu.org ---
Author: vries
Date: Tue Feb 9 07:04:08 2016
New Revision: 233237
URL: https://gcc.gnu.org/viewcvs?rev=233237&root=gcc&view=rev
Log:
Handle -fdiagnostics-color in lto
2016-02-09 Tom de Vries
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69707
vries at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68404
--- Comment #20 from Markus Trippelsdorf ---
Your patch fixes the problem for me. Thanks.
I've also successfully build Firefox and run the Boost testsuite with it.
(the Boost testsuite hit the PR68973 ICE once with -mlra.
I will reduce a testca
101 - 155 of 155 matches
Mail list logo