https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #5 from Martin Sebor -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #3 from Yuri Gribov ---
It seems these lines in is_masked_range_test should be removed:
if (wi::neg_p (val, TYPE_SIGN (type)))
std::swap (*low, *high);
Sadly there were no tests which tested negative constants. I'll bootstrap an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492
--- Comment #10 from Andrew Waterman ---
Thanks for the suggestion. Let's go with the CFI-directive approach.
On Sat, Apr 28, 2018 at 5:45 AM, aurelien at aurel32 dot net
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492
>
> --- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85825
Bug ID: 85825
Summary: Incorrect selection of method in template class
specialization.
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
Jonathan Wakely changed:
What|Removed |Added
CC||redi at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85803
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
--- Comment #2 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Yuri Gribov changed:
What|Removed |Added
CC||tetra2005 at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #2 from Wanying Luo ---
(In reply to Wanying Luo from comment #0)
> When I ran this test on a Linux machine with GCC 4.9.2, glibc's strxfrm()
> converts 0x80 to 6 bytes.
Pasting my test on Linux with the same version of GCC for compl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #1 from Wanying Luo ---
Here's GDB backtrace at the time of crash.
#0 0xf56fe7a0 in __lwp_sigqueue () from /lib/libc.so.1
#1 0xf56a1e90 in raise () from /lib/libc.so.1
#2 0xf567a274 in abort () from /lib/libc.so.1
#3 0xff2f2d70
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
Bug ID: 85824
Summary: regex constructor crashes under UTF-8 locale on
Solaris-sparc when parsing a simple character class
Product: gcc
Version: 4.9.2
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #1 from Marc Glisse ---
_2 = x.0_1 & -281474976710656;
if (_2 == -281474976710656)
goto ; [20.24%]
[...]
x.0_11 = ASSERT_EXPR ;
x.0_12 = ASSERT_EXPR ;
x.0_13 = ASSERT_EXPR = -1>;
y_7 = (unsigned intD.9) x.0_13;
Thos
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82229
--- Comment #28 from krzysio.kurek at wp dot pl ---
I mean the relative performance is worse but still Profiled GCC6 is faster than
GCC 7 or GCC 8.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Bug ID: 85823
Summary: Boost.Tribool fails to compile: error:
'(tribool::dummy::nonnull != 0)' is not a constant
expression
Product: gcc
Version: 8.1.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Bug ID: 85822
Summary: [8/9 Regression] Maybe wrong code in VRP since r249150
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
Martin Sebor changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41475
Andrey Tarasevich changed:
What|Removed |Added
CC||atarasevich at comcast dot net
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #5 from Jonathan Wakely ---
Author: redi
Date: Thu May 17 17:26:44 2018
New Revision: 260331
URL: https://gcc.gnu.org/viewcvs?rev=260331&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821
--- Comment #1 from Jonathan Wakely ---
The simple answer is of course "don't do that". Writing 1s works fine, or if
you want to be explicit, std::chrono::seconds(1).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #8 from Jonathan Wakely ---
(In reply to Mathias Stearn from comment #7)
> > Simply returning an empty exception_ptr is what happened before the PR 64241
> > change, so what we do now retains that behaviour. That might be the main
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #7 from Mathias Stearn ---
> Simply returning an empty exception_ptr is what happened before the PR 64241
> change, so what we do now retains that behaviour. That might be the main
> reason for it.
Silently dropping errors always ske
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821
Bug ID: 85821
Summary: Chrono literal operators do not follow the standard
declarataions
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
--- Comment #3 from Jonathan Wakely ---
OK thanks for following up.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #5 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Mathias Stearn from comment #3)
> > My assumption was that if E(...) throws and it can't be caught, it should be
> > treated as any other case wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
This is most likely dup of PR85817. Could you check if the fix in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817#c1 works ?
Thanks,
Prathamesh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #4 from Jonathan Wakely ---
(In reply to Mathias Stearn from comment #3)
> My assumption was that if E(...) throws and it can't be caught, it should be
> treated as any other case when an -fno-exceptions TU calls a throwing
> function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Pat Haugen changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #9 from Pat Haugen ---
Author: pthaugen
Date: Thu May 17 16:19:16 2018
New Revision: 260329
URL: https://gcc.gnu.org/viewcvs?rev=260329&root=gcc&view=rev
Log:
PR target/85698
* config/rs6000/rs6000.c (rs6000_output_mo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
Bug ID: 85820
Summary: [9 Regression] internal compiler error: Segmentation
fault
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Thu May 17 16:10:26 2018
New Revision: 260328
URL: https://gcc.gnu.org/viewcvs?rev=260328&root=gcc&view=rev
Log:
PR libstdc++/85818 ensure path::preferred_separator is defined
Because p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Thu May 17 16:10:20 2018
New Revision: 260327
URL: https://gcc.gnu.org/viewcvs?rev=260327&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #1 from Jonathan Wakely ---
Author: redi
Date: Thu May 17 15:36:25 2018
New Revision: 260326
URL: https://gcc.gnu.org/viewcvs?rev=260326&root=gcc&view=rev
Log:
PR libstdc++/85818 ensure path::preferred_separator is defined
Because p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
Paul Thomas changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
--- Comment #7 from Paul Thomas ---
Author: pault
Date: Thu May 17 15:31:42 2018
New Revision: 260325
URL: https://gcc.gnu.org/viewcvs?rev=260325&root=gcc&view=rev
Log:
2017-05-17 Paul Thomas
PR fortran/82814
* gfortran.dg/su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57160
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
Dominique d'Humieres changed:
What|Removed |Added
CC||Joost.VandeVondele at mat dot
eth
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
--- Comment #6 from Paul Thomas ---
Author: pault
Date: Thu May 17 15:17:43 2018
New Revision: 260324
URL: https://gcc.gnu.org/viewcvs?rev=260324&root=gcc&view=rev
Log:
2017-05-17 Paul Thomas
PR fortran/82814
* gfortran.dg/su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #2 from Dominique d'Humieres ---
This PR seems fixed by the patch at
https://gcc.gnu.org/ml/fortran/2018-05/msg00046.html, likely a duplicate of
pr82923.
On darwin the executable hangs due to pr30617.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
Josh Marshall changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
--- Comment #2 from Josh Marshall ---
Created attachment 44143
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44143&action=edit
Example file
I got to making an example, but it seems that this is no longer a problem. I'm
going to close thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
--- Comment #5 from Vittorio Zecca ---
I confirm I get the ICE on trunk 260152 and on a sanitized version I also get
../../gcc/gcc/tree-ssa-strlen.c:721:11: runtime error: member access
within null pointer of type 'struct strinfo'
Thank you for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Thu May 17 15:03:29 2018
New Revision: 260323
URL: https://gcc.gnu.org/viewcvs?rev=260323&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783
Martin Sebor changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #3 from Mathias Stearn ---
My assumption was that if E(...) throws and it can't be caught, it should be
treated as any other case when an -fno-exceptions TU calls a throwing function.
In this case that would mean calling terminate() d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85819
Bug ID: 85819
Summary: conversion from __v[48]su to __v[48]sf should use FMA
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #29 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #27)
> > If an impure function is found (recursively) in the operands of an .AND.
> > expression, issue a
> >
> > gfc_warning(OPT_Wsurprising, "Impure funct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81652
Bug 81652 depends on bug 85620, which changed state.
Bug 85620 Summary: Missing ENDBR after swapcontext
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
H.J. Lu changed:
What|Removed |Added
Resolution|FIXED |WONTFIX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #9 from Eric Botcazou ---
> OH! I thought you meant here. I wasn't sure this was the same bug
> internally. They have different results in the two different versions of
> GNAT. The AdaCore GNAT Community put out a crash report whi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
Dominique d'Humieres changed:
What|Removed |Added
Keywords|wrong-code |
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #10 from Martin Jambor ---
Author: jamborm
Date: Thu May 17 12:23:34 2018
New Revision: 260320
URL: https://gcc.gnu.org/viewcvs?rev=260320&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-17 Martin Jambo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #9 from Martin Jambor ---
Author: jamborm
Date: Thu May 17 12:18:06 2018
New Revision: 260319
URL: https://gcc.gnu.org/viewcvs?rev=260319&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-17 Martin Jambor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Bug ID: 85818
Summary: [8/9 Regression] undefined reference to
`std::experimental::filesystem::v1::__cxx11::path::pre
ferred_separator'
Product: gcc
Version: 8.1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #27 from Thomas Koenig ---
[Replying to myself now]
> A front end pass (what else did you expect? :-)
>
> If an impure function is found (recursively) in the operands of an .AND.
> expression, issue a
>
> gfc_warning(OPT_Wsurprisin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85804
bin cheng changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #8 from Jere ---
OH! I thought you meant here. I wasn't sure this was the same bug internally.
They have different results in the two different versions of GNAT. The
AdaCore GNAT Community put out a crash report while the FSF GNAT
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85793
--- Comment #3 from bin cheng ---
Author: amker
Date: Thu May 17 11:25:43 2018
New Revision: 260317
URL: https://gcc.gnu.org/viewcvs?rev=260317&root=gcc&view=rev
Log:
PR tree-optimization/85793
* tree-vect-stmts.c (vectorizable_l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77810
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
Created attachment 44142
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44142&action=edit
Untested fix
Oops, sorry about that.
I put the condition
if (integer_zerop (retval))
conti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
Bug ID: 85817
Summary: [9 Regression] ICE in expand_call at gcc/calls.c:4291
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69905
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Thu May 17 10:07:12 2018
New Revision: 260313
URL: https://gcc.gnu.org/viewcvs?rev=260313&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c (ix86_fold_builtin):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84671
Jonathan Wakely changed:
What|Removed |Added
CC||alisdairm at me dot com
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Thu May 17 10:01:33 2018
New Revision: 260312
URL: https://gcc.gnu.org/viewcvs?rev=260312&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c (ix86_fold_builtin):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu May 17 09:54:36 2018
New Revision: 260311
URL: https://gcc.gnu.org/viewcvs?rev=260311&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c: Include tree-vector-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #26 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #25)
> > We do have problems with compiler-dependent behavior already. The behavior
> > I'm proposing is consistent with what ifort, PGI and flang do.
>
> B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85815
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69905
--- Comment #8 from Jonathan Wakely ---
The testcase in comment 2 (the only one in the bug that's actually correct!)
works now, fixed by r258157 for Bug 84671.
The problem in comment 7 still exists, the corrected testcase is:
#include
int main
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #2 from Jonathan Wakely ---
... because if that constructor throws and the current translation unit is
built without exceptions, we can't catch it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85713
--- Comment #8 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Thu May 17 09:17:56 2018
New Revision: 260308
URL: https://gcc.gnu.org/viewcvs?rev=260308&root=gcc&view=rev
Log:
2018-05-17 Paolo Carlini
PR c++/85713
* g++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #1 from Jonathan Wakely ---
As you pointed out in PR 85812 the constructor of the exception can throw. That
can happen even if the current translation unit is not built with exceptions,
if the constructor is defined in a different tra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Martin Liška changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Martin Liška changed:
What|Removed |Added
Keywords|needs-reduction |
--- Comment #3 from Martin Liška ---
Re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #9 from rguenther at suse dot de ---
On Thu, 17 May 2018, sch...@linux-m68k.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
>
> --- Comment #8 from Andreas Schwab ---
> > Is there sth like -NaN?!
>
> signbit can te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #9 from Richard Biener ---
So the following incomplete patch solves the value-numbering issue in FRE2.
diff --git a/gcc/tree-dfa.c b/gcc/tree-dfa.c
index a121b880bb0..745d60cbda5 100644
--- a/gcc/tree-dfa.c
+++ b/gcc/tree-dfa.c
@@ -5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #8 from Andreas Schwab ---
> Is there sth like -NaN?!
signbit can tell you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #8 from Richard Biener ---
comment#5 runs into the fact that we cannot reliably compute kills for
loop-variant stores and thus we give up completely:
if (gimple_code (temp) == GIMPLE_PHI)
{
/* If we visit this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85815
Bug ID: 85815
Summary: incorrect "invalid use of incomplete type" in a lambda
on valid code
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
1 - 100 of 109 matches
Mail list logo