https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87035
--- Comment #3 from Andrew Pinski ---
(In reply to Nicolas Lesser from comment #2)
> Huh, interesting. TIL. Where's that rule in the standard? Because I can't
> find it in [class.mem]. Is it somewhere else or did I just overlook it?
C++98 paragr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87035
--- Comment #5 from Andrew Pinski ---
[basic.scope.class] p2:
"A name N used in a class S shall refer to the same declaration in its context
and when re-evaluated in the completed scope of S. No diagnostic is required
for a violation of this rul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87035
--- Comment #4 from Nicolas Lesser ---
Nice, thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86771
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86987
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86834
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86836
Richard Biener changed:
What|Removed |Added
Known to work||9.0
--- Comment #9 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86840
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
--- Comment #2 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86844
Richard Biener changed:
What|Removed |Added
Priority|P1 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87036
Bug ID: 87036
Summary: -O1/-O2 affects floating point precision on at least
i686 and ppc64el
Product: gcc
Version: 6.4.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86845
Richard Biener changed:
What|Removed |Added
Keywords||build
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87036
--- Comment #1 from Andrew Pinski ---
For powerpc at least this is due to fma. Use -ffp-contract=off to turn it off.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86834
Thomas Preud'homme changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87036
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87036
--- Comment #3 from Matthias Klose ---
On 21.08.2018 09:53, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87036
>
> --- Comment #1 from Andrew Pinski ---
> For powerpc at least this is due to fma. Use -ffp-con
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87037
Bug ID: 87037
Summary: vector :: erase return value should be marked "must
use"
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priorit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87037
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87035
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86121
--- Comment #4 from Bernd Edlinger ---
Author: edlinger
Date: Tue Aug 21 08:56:11 2018
New Revision: 263693
URL: https://gcc.gnu.org/viewcvs?rev=263693&root=gcc&view=rev
Log:
2018-08-21 Bernd Edlinger
PR middle-end/86121
* tr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87038
Bug ID: 87038
Summary: diagnostics: Please add warning for jumping over
initializers with switch/case in C mode
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87038
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87038
--- Comment #2 from Jonathan Wakely ---
And for the goto case Clang says:
87038.c:2:13: warning: variable 'foo' is used uninitialized whenever 'if'
condition is true [-Wsometimes-uninitialized]
if (x == 0) goto lbl;
^~
87
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86847
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86850
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86853
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86860
--- Comment #3 from Richard Biener ---
So INVALID?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87039
Bug ID: 87039
Summary: [8/9 Regression] DW_OP_fbreg used without a frame base
on a C++ code w/ -fopenmp
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86864
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87039
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87040
Bug ID: 87040
Summary: ICE in extract_constrain_insn_cached, at recog.c:2218
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86869
--- Comment #1 from Richard Biener ---
#ifndef POINTERS_EXTEND_UNSIGNED
gcc_assert (GET_MODE (x) == to_mode || GET_MODE (x) == VOIDmode);
return x;
#else /* defined(POINTERS_EXTEND_UNSIGNED) */
scalar_int_mode pointer_mode, address_mode, fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86990
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86875
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86877
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86991
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-valid-code
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86860
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87041
Bug ID: 87041
Summary: GCC 8 regression: -Wformat "reading through null
pointer" on unreachable code
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87041
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86900
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86902
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86905
Richard Biener changed:
What|Removed |Added
Keywords||ice-checking
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86907
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86850
--- Comment #2 from David Binderman ---
Indeed it does look like vectorizer code. Here are 20 frames,
found by using the UBSAN_OPTIONS=print_stacktrace=1 option:
../../trunk/gcc/vec.h:1688:5: runtime error: member call on null pointer of
type
'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86908
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86771
--- Comment #19 from Wilco ---
(In reply to Segher Boessenkool from comment #16)
> (In reply to Wilco from comment #14)
> > Note there is also an issue with costs, if the cost is zero then it seems to
> > behave like infinite cost.
>
> 0 means u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86850
--- Comment #3 from rguenther at suse dot de ---
On Tue, 21 Aug 2018, dcb314 at hotmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86850
>
> --- Comment #2 from David Binderman ---
> Indeed it does look like vectorizer code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86997
--- Comment #2 from Martin Liška ---
(In reply to Jonathan Wakely from comment #1)
> Looks like a dup of PR 59389
Any easy workaround for it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86997
--- Comment #3 from Jonathan Wakely ---
Don't write weird code?
Either of these works fine and is obvious what it is supposed to do:
NoDestructor b;
NoDestructor b{};
The original is weird. Is it trying to construct an 'a' object and pass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86908
--- Comment #7 from Jonathan Wakely ---
(In reply to Richard Biener from comment #6)
> (In reply to Jonathan Wakely from comment #1)
> > No, your program has undefined behaviour. To make it valid you either need
> > to use std::launder, or use th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86909
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
Joshua Green changed:
What|Removed |Added
CC||jvg1981 at aim dot com
--- Comment #17 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86914
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #18 from joseph at codesourcery dot com ---
On Tue, 21 Aug 2018, jvg1981 at aim dot com wrote:
> intptr_t pVal = ((uintptr_t) p)/(sizeof *p);
> intptr_t qVal = ((uintptr_t) q)/(sizeof *q);
Note that this can be expanded like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86917
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303
--- Comment #19 from Marc Glisse ---
This seems fixed in gcc-8, no?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86908
--- Comment #8 from Kostya Frumkin ---
> Either way you need to placement new the original type back again, otherwise
> the wrong destructor gets called on scope exit, which adds more undefined
> behaviour.
There should not be undefined behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86919
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86922
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic, wrong-code
--- Comment #1 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86924
Richard Biener changed:
What|Removed |Added
Target||x86_64-w64-mingw32
Status|U
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86926
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86932
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86908
--- Comment #9 from Jonathan Wakely ---
(In reply to Kostya Frumkin from comment #8)
> At the same time this design pattern (strategy) with placement-new is more
> efficient than with common new.
That's fine, but you can't use &strategy to acces
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87042
Bug ID: 87042
Summary: UBSAN: poly-int.h:1095:5: runtime error: signed
integer overflow: 9223372036854775807 * 8 cannot be
represented in type 'long int'
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86936
--- Comment #3 from Richard Biener ---
Note to GIMPLE &a[1][i_3(D)] is just address-computation and carries no
semantics so you can't assume that i_3(D) isn't negative and thus ends up
accessing "123". For the C testcase you of course can, but o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86943
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87043
Bug ID: 87043
Summary: maybe-uninitialized warning for initialized variable
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86945
Richard Biener changed:
What|Removed |Added
Priority|P4 |P2
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86945
--- Comment #7 from Richard Biener ---
With -fsanitize=undefined we get even at -O0
id= 1
: runtime error: signed integer overflow: 1 - -2147483647 cannot be
represented in type 'integer(kind=4)'
ierr1, OK =0 T
: runtime
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86924
--- Comment #2 from Mario Rohkrämer ---
Unfortunately, I do not have much experience in running a compile manually. I
only let the "media-autobuild suite" batch run.
https://github.com/jb-alvarado/media-autobuild_suite/
I would not know for sur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86945
--- Comment #8 from Richard Biener ---
C testcase:
void __attribute__((noinline,noipa))
foo(int id)
{
switch (id)
{
case (-__INT_MAX__ - 1)...-1:
__builtin_abort ();
default:;
}
}
int main()
{
foo(1);
return 0;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86924
--- Comment #3 from Mario Rohkrämer ---
Created attachment 44567
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44567&action=edit
Zipped temp output encoder.i by lupo...
This is the "-save-temps" output which user lupo... attached in comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87044
Bug ID: 87044
Summary: stl_construct.h not interoperable with allocators with
custom reference types
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65043
--- Comment #4 from Marek Polacek ---
Author: mpolacek
Date: Tue Aug 21 15:25:17 2018
New Revision: 263739
URL: https://gcc.gnu.org/viewcvs?rev=263739&root=gcc&view=rev
Log:
PR c++/65043
* call.c (standard_conversion): Set check_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65043
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86981
--- Comment #1 from Marek Polacek ---
Author: mpolacek
Date: Tue Aug 21 15:38:36 2018
New Revision: 263741
URL: https://gcc.gnu.org/viewcvs?rev=263741&root=gcc&view=rev
Log:
PR c++/86981, Implement -Wpessimizing-move.
* c.opt (Wp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87045
Bug ID: 87045
Summary: pointer to array of character
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86981
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87046
Bug ID: 87046
Summary: Incorrect vectorization of fma with -O3
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-opti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87046
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87044
--- Comment #1 from Jonathan Wakely ---
This is correct: custom reference types are not supported at all, and never
will be. And that's not a bug. The container requirements in the standard
require X::reference to be X::value_type&, and the alloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87014
--- Comment #8 from hjl at gcc dot gnu.org ---
Author: hjl
Date: Tue Aug 21 16:17:35 2018
New Revision: 263743
URL: https://gcc.gnu.org/viewcvs?rev=263743&root=gcc&view=rev
Log:
x86: Always update EH return address in word_mode
On x86, return a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87044
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87044
--- Comment #3 from Jonathan Wakely ---
See also https://cplusplus.github.io/LWG/lwg-closed.html#1318 which requested
that custom references be put back, and was closed as Not A Defect.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87014
--- Comment #9 from hjl at gcc dot gnu.org ---
Author: hjl
Date: Tue Aug 21 16:27:22 2018
New Revision: 263744
URL: https://gcc.gnu.org/viewcvs?rev=263744&root=gcc&view=rev
Log:
x86: Always update EH return address in word_mode
On x86, return a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87014
--- Comment #10 from hjl at gcc dot gnu.org ---
Author: hjl
Date: Tue Aug 21 16:38:17 2018
New Revision: 263745
URL: https://gcc.gnu.org/viewcvs?rev=263745&root=gcc&view=rev
Log:
x86: Always update EH return address in word_mode
On x86, return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87014
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87047
Bug ID: 87047
Summary: gcc 7 & 8 - performance regression because of
if-conversion
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86499
--- Comment #2 from Marek Polacek ---
Author: mpolacek
Date: Tue Aug 21 18:37:23 2018
New Revision: 263749
URL: https://gcc.gnu.org/viewcvs?rev=263749&root=gcc&view=rev
Log:
PR c++/86499
* parser.c (cp_parser_lambda_introducer):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86499
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829
--- Comment #55 from Nicolas Koenig ---
Author: koenigni
Date: Tue Aug 21 18:48:59 2018
New Revision: 263750
URL: https://gcc.gnu.org/viewcvs?rev=263750&root=gcc&view=rev
Log:
2018-08-21 Nicolas Koenig
Thomas Koenig
PR fortr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87008
--- Comment #1 from Marc Glisse ---
struct A { double a, b; };
struct B : A {};
templatevoid cp(T&a,T const&b){a=b;}
double f(B x){
B y; cp(y,x);
B z; cp(z,x);
return y.a - z.a;
}
This is not quite equivalent because RTL manages to optimiz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87048
Bug ID: 87048
Summary: [9 Regression] array_constructor_8.f90 failure on
armeb
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priorit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87048
Thomas Koenig changed:
What|Removed |Added
Blocks||25829
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87049
Bug ID: 87049
Summary: __clear_cache() prototype confusion
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79342
H.J. Lu changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment #8 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70578
H.J. Lu changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87008
--- Comment #2 from Marc Glisse ---
Or just:
struct A { double a, b; };
struct B : A {};
double f(B x){
B y;
A*px=&x;
A*py=&y;
*py=*px;
return y.a;
}
MEM[(struct A *)&y] = MEM[(const struct A &)&x];
y_6 = MEM[(struct A *)&y];
y
1 - 100 of 123 matches
Mail list logo