https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107360
Bug ID: 107360
Summary: ICE on sizeof(*f(x)) when f's (deduced) return type is
a pointer to VLA
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: norm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107359
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-10-23
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107360
Andrew Pinski changed:
What|Removed |Added
Keywords|ice-on-valid-code |
--- Comment #1 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107361
Bug ID: 107361
Summary: Why does -Wclass-memaccess require trivial types,
instead of trivially-copyable types?
Product: gcc
Version: 13.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107362
Bug ID: 107362
Summary: Segfault for recursive class
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107360
--- Comment #2 from Alexey Izbyshev ---
(In reply to Andrew Pinski from comment #1)
> Maybe this should be invalid code ...
Yes, I think it should be invalid. VLAs are not allowed in function return
types in C. VLAs in C++ are a GCC extension,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107363
Bug ID: 107363
Summary: Wrong caret location for "redundant move in return
statement"
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107364
Bug ID: 107364
Summary: ICE on Via Nehemiah with --march=native
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107365
Bug ID: 107365
Summary: ICE in verify_range, at value-range.cc:726
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107365
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-10-23
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107346
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107366
Bug ID: 107366
Summary: -fanalyzer with -fdiagnostics-format=sarif-file or
sarif-stderr
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107346
--- Comment #9 from avieira at gcc dot gnu.org ---
Hi Eric,
I realised the same, got a patch pending here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604139.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107365
--- Comment #1 from Aldy Hernandez ---
Ok, this is getting ridiculous. I'm tired of these weird finite-math-only
combinations in Vax and rx-elf. I think we should just test -ffinite-math-only
and -fno-finite-math-only in the self tests for all
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107365
--- Comment #2 from Aldy Hernandez ---
Created attachment 53761
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53761&action=edit
untested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #8 from Carlos E ---
Created attachment 53762
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53762&action=edit
preprocessed file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #9 from Carlos E ---
(In reply to Martin Liška from comment #7)
> (In reply to Carlos E from comment #6)
> > (In reply to Martin Liška from comment #4)
> > > > When you say to attach a preprocessed source, what would be the most
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107363
--- Comment #1 from Andrew Pinski ---
The wrong caret comes from named return value optimization iirc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105774
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107362
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105633
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:e3c997824f17dd6a4f7eb8d668b9ed2ef84408fc
commit r12-8860-ge3c997824f17dd6a4f7eb8d668b9ed2ef84408fc
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105633
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:c6ff6ca2fcefdd5edc37011a2ba8412a466d9b0b
commit r11-10330-gc6ff6ca2fcefdd5edc37011a2ba8412a466d9b0b
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105633
--- Comment #8 from CVS Commits ---
The releases/gcc-10 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:910156619c93ff988587762b446542c4dfbb00a2
commit r10-11055-g910156619c93ff988587762b446542c4dfbb00a2
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107361
--- Comment #1 from Andrew Pinski ---
https://gcc.gnu.org/legacy-ml/gcc-patches/2017-04/msg01571.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107364
Andrew Pinski changed:
What|Removed |Added
Host|X86_64 |i?86-linux-gnu
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106081
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367
Bug ID: 107367
Summary: All standard library algorithms should detect whether
they are contiguous iterators after C++20
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107367
--- Comment #1 from cqwrteur ---
This optimization will prevent duplications of templates over iterators and
pointers. (vector::iterator and int* duplications for example)
For example:
https://godbolt.org/z/9zEajxxa8
vs
https://godbolt.org/z/n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85043
--- Comment #17 from Eric Gallager ---
(In reply to Marek Polacek from comment #16)
> Should be fixed now.
It seems the fix just silenced the -Wuseless-cast false positive without also
adding the separate -Wcast-to-the-same-type flag to cover th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106076
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106076
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc 13.0.0
NCONFIRMED
Keywords: ice-on-invalid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc 13.0.0 20221023 s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107370
Bug ID: 107370
Summary: long double precision is wrong in ARM 64
Product: gcc
Version: 10.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107361
--- Comment #2 from Carlos Galvez ---
I understand the motivation and I think the warning makes a lot of sense!
However I don't see how it could possibly be dangerous in the provided example.
Would it suffice to trigger the warning only when a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107370
--- Comment #1 from jacob navia ---
This program produces correct results:
#include
#include
long double nsqrt(long double x)
{
double m = sqrt(x);
long double r = m;
r = (r+x/r)/2.0L;
r = (r+x/r)/2.0L;
36 matches
Mail list logo