https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120363
Bug ID: 120363
Summary: internal compiler error: in tree_node, at
cp/module.cc:9956
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #11 from Robin Dapp ---
> Yes. I am sure. And SPIKE and QEMU have no problem.
So vlre/vsre should execute despite a VILL in VTYPE? At first sight I don't
find any specifics in the vector spec.
qemu is not very pedantic in that res
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #3 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120365
Bug ID: 120365
Summary: Flag/skip torture testing in presence of explicit '-O'
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: internal-improvement
Severity: en
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120366
Bug ID: 120366
Summary: __PRETTY_FUNCTION__ is sometimes an array of unknown
bound
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
James K. Lowden changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #13 from Li Pan ---
Spec has two sentences about this:
[1] These instructions are intended to be used to save and restore vector
registers when the type or length of the current contents of the
vector register is not known, or where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99912
Martin Jambor changed:
What|Removed |Added
CC||19373742 at buaa dot edu.cn
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
Martin Jambor changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
--- Comment #23 from Sam James ---
Thanks Martin.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #19 from GCC Commits ---
The releases/gcc-15 branch has been updated by Martin Jambor
:
https://gcc.gnu.org/g:c1db46f7e51d4a546ca536f7f10e548f02e5cc12
commit r15-9717-gc1db46f7e51d4a546ca536f7f10e548f02e5cc12
Author: Martin Jambor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
Kito Cheng changed:
What|Removed |Added
CC||andrew at sifive dot com
--- Comment #12 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120295
--- Comment #10 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6h61fwbp5@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120366
Andrew Pinski changed:
What|Removed |Added
Summary|__PRETTY_FUNCTION__ is |__PRETTY_FUNCTION__ is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120360
--- Comment #2 from Linus Torvalds ---
Btw, for a similar - but different - comparison optimization failure case, we
had a discussion about our error pointer comparisons in the kernel.
We have this model where we return a pointer or error code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120360
--- Comment #3 from Linus Torvalds ---
(In reply to Linus Torvalds from comment #2)
>
> Stupid test-case:
Actually, that was a bit *too* stupid, since it doesn't show the effect of "we
still need the original value afterwards".
So change it to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119885
Robert Dubner changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
Robert Dubner changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #1 from Robert Dubn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119337
Robert Dubner changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120297
--- Comment #2 from Edwin Lu ---
Created attachment 61477
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61477&action=edit
user-config-O3-lto.s
Here's the assembly file with -O3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120297
--- Comment #3 from Edwin Lu ---
Created attachment 61478
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61478&action=edit
user-config-O2-lto.s
Here's the assembly with -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120368
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|target
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2025-05-20
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47803
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
--- Comment #4 from Andrew Pinski ---
I think I know the issue. it comes down to the LHS of __builtin_cabs is NULL.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
James K. Lowden changed:
What|Removed |Added
Status|WAITING |NEW
Assignee|rdubner at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120374
Bug ID: 120374
Summary: ext-dce fails to realize a shift pair makes bits dead
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120374
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
--- Comment #6 from Andrew Pinski ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2025-May/684319.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119324
--- Comment #5 from David Binderman ---
cppcheck says a lot of things that are true but not useful.
I use the following grep command to find the more interesting material:
grep -E "performance:| error:| warning:| style:" filename
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120273
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2025-05-20
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118994
--- Comment #8 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:72f0b446d2c03866ebe4cae125e32fef598e924d
commit r16-767-g72f0b446d2c03866ebe4cae125e32fef598e924d
Author: liuhongt
Date: Tue Feb 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118994
Hongtao Liu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
--- Comment #3 from Robert Dubner ---
(In reply to James K. Lowden from comment #2)
> The issue appears to boil down to YYLTYPE and YDFLTYPE, which are identical,
> being defined differently somehow, somewhere. A clue perhaps: in
> gcc/cobol/ut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120373
Bug ID: 120373
Summary: operator overloads inside extern "C"
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120367
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118694
--- Comment #5 from sandra at gcc dot gnu.org ---
Created attachment 61485
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61485&action=edit
test case metadirective-1a.c with dynamic selector
Hmmm, interesting. I temporarily #ifdef'ed out
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120363
Nathaniel Shead changed:
What|Removed |Added
Last reconfirmed||2025-05-21
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #14 from Andrew Waterman ---
> Let us summon the RISC-V judge!!!
The key is that vtype.vill affects only those instructions that depend on
vtype. vlr and vsr do not depend on vtype and so are unaffected by
vtype.vill.
> vmv1r also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119324
--- Comment #4 from Robert Dubner ---
I fear that my ignorance is holed up in a bit of a fortress.
I have installed Cppcheck 2.7 on an Ubuntu 22.04 LTS x86_64 system.
When I try to run it on just one file that you mention, I get the following.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120273
--- Comment #7 from Sam James ---
```
[...]
==838291== Invalid read of size 1
==838291==at 0x8EB7F10: __strcmp_avx2 (strcmp-avx2.S:249)
==838291==by 0x5EF52CE: UnknownInlinedFun (splay-tree.c:151)
==838291==by 0x5EF52CE: UnknownInlin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80400
Campbell changed:
What|Removed |Added
CC||rlcamp.pdx at gmail dot com
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120372
--- Comment #3 from Andrew Pinski ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2025-May/684328.html
https://gcc.gnu.org/pipermail/gcc-patches/2025-May/684329.html
(with extra comments added compared to the patch attached here and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120367
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2025-05-21
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120371
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |15.2
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119928
Richard Biener changed:
What|Removed |Added
CC||juergen.reuter at desy dot de
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Andrew Pinski changed:
What|Removed |Added
Known to work||14.1.0, 14.2.0
Summary|[15/1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
--- Comment #7 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:95c74f354ae3186e84fbada22d2e7f3845dbb659
commit r16-769-g95c74f354ae3186e84fbada22d2e7f3845dbb659
Author: Andrew Pinski
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119636
--- Comment #4 from Simon Sobisch ---
Please reopen as this is not about doing anything with the obsolete code in any
way, but ignoring = "parse in the water".
The main issue is that the FD is not recognized any more, and yes, there are a
lot o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
--- Comment #21 from mcccs at gmx dot com ---
Okay I'm so sorry for the misinterpretation. I thought DCE should never turn an
invalid program to a valid one because DCE is always an optimization and
optimizations should never modify the behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120364
Bug ID: 120364
Summary: std::bitset is missing hardened preconditions
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #7 from Li Pan ---
Does it possible that the board has set such insn to illegal insn by mistake?
The qemu and spike doesn't report any illegal insn. I will go thru the spec for
more details.
Ideally, the vl1re32.v has the vtype info
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #8 from JuzheZhong ---
(In reply to Robin Dapp from comment #6)
> (In reply to Kito Cheng from comment #5)
> > Oh, vsetvli/vill issue should only appeared for whole reg move not whole reg
> > load store
>
> On the Banana Pi I get a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120345
--- Comment #3 from Orgad Shaneh ---
Looks right. See analysis in
https://github.com/scummvm/scummvm/pull/6620#issuecomment-2886321894
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
Bug ID: 120362
Summary: [GCC-15.1] Illegal Insn when run spec2017 511 ref size
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #1 from Robin Dapp ---
That's a misaligned vector load I suppose?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #2 from Li Pan ---
(In reply to Robin Dapp from comment #1)
> That's a misaligned vector load I suppose?
I see, but when I changed to
addia5,a5,912
aka load from 0xdd390, the board still has the illegal insn. 0xdd390 is aligne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120355
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #9 from Robin Dapp ---
> No. vlre should not depend on vtype. It should be hardware bug.
Are you sure about that? vmv1r also doesn't depend on a specific vtype, each
one is OK, but the vtype must at least be valid. So we get a SIG
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #10 from JuzheZhong ---
(In reply to Robin Dapp from comment #9)
> > No. vlre should not depend on vtype. It should be hardware bug.
>
> Are you sure about that? vmv1r also doesn't depend on a specific vtype,
> each one is OK, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120363
--- Comment #1 from ACB ---
Created attachment 61476
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61476&action=edit
freport-bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #6 from Robin Dapp ---
(In reply to Kito Cheng from comment #5)
> Oh, vsetvli/vill issue should only appeared for whole reg move not whole reg
> load store
On the Banana Pi I get a SIGILL for
int
main() {
asm volatile ("lui a5, 0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #5 from Kito Cheng ---
Oh, vsetvli/vill issue should only appeared for whole reg move not whole reg
load store
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120362
--- Comment #4 from Robin Dapp ---
> I see, but when I changed to
>
> addia5,a5,912
>
> aka load from 0xdd390, the board still has the illegal insn. 0xdd390 is
> aligned for -O2 -march=rv64gcv -mrvv-vector-bits=zvl build, right?
Hmm, righ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119835
Thomas Schwinge changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89550
Andrew Pinski changed:
What|Removed |Added
Target Milestone|8.5 |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120367
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.2
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119885
--- Comment #1 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:d44beb132850a8ced1b0614e2724f18465b4a737
commit r16-761-gd44beb132850a8ced1b0614e2724f18465b4a737
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119770
--- Comment #2 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119810
--- Comment #5 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119632
--- Comment #11 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119335
--- Comment #3 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119790
--- Comment #2 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119771
--- Comment #2 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119770
Robert Dubner changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119790
Robert Dubner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119772
--- Comment #2 from GCC Commits ---
The master branch has been updated by Robert Dubner :
https://gcc.gnu.org/g:fba34a0cc55488ad89becf81cf2c9ac517d244d4
commit r16-764-gfba34a0cc55488ad89becf81cf2c9ac517d244d4
Author: Robert Dubner
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119772
Robert Dubner changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102891
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
Bug ID: 120369
Summary: internal compiler error: Segmentation fault during
GIMPLE pass: cplxlower0 only in version 15.1 and trunk
Product: gcc
Version: 16.0
Status: UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120370
Bug ID: 120370
Summary: GCC fails to parse a trailing requires-clause that
ends with an identifier when followed by a
ctor-initializer
Product: gcc
Version: 15.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
--- Comment #1 from Andrew Pinski ---
Created attachment 61481
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61481&action=edit
No header version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120370
--- Comment #1 from Andrew Pinski ---
Simple workaround is to do `(i)`.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120370
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120371
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120369
--- Comment #5 from Andrew Pinski ---
Created attachment 61482
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61482&action=edit
Patch which I am testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120371
Bug ID: 120371
Summary: [15.1 regression] erroneously triggered error message
on non-matching interfaces with flag -Wall
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102599
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2025-5-20
Keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120371
--- Comment #2 from Jürgen Reuter ---
(In reply to anlauf from comment #1)
> Jürgen,
>
> this is likely a duplicate of pr119928/pr120163 and has been fixed after
> the 15.1 release.
>
> Either upgrade to 15-HEAD, or use -Wno-external-argument-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120372
Bug ID: 120372
Summary: canonicalize_comparison uses gen_move_insn to
calcualate the cost of the constant formation
Product: gcc
Version: 16.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120367
--- Comment #1 from Andrew Pinski ---
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x7788b9b3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120366
Andrew Pinski changed:
What|Removed |Added
Known to work||8.5.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119712
Andrew Macleod changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85316
Bug 85316 depends on bug 95801, which changed state.
Bug 95801 Summary: Optimiser does not exploit the fact that an integer divisor
cannot be zero
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95801
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95801
Andrew Macleod changed:
What|Removed |Added
CC||amacleod at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120367
Bug ID: 120367
Summary: C++23 ranges::transform | ranges::to exception
catching (segfault)
Product: gcc
Version: 15.1.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 116 matches
Mail list logo
