https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109977
--- Comment #2 from Andrew Pinski ---
Introduced by r14-215-g85279b0bddc1c5 .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109977
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
--- Comment #6 from JuzheZhong ---
>> With decrement IV, the optimized IR actually becomes better, it also aligns
>> >>with our discussion here:
>> https://gcc.gnu.org/pipermail/gcc-patches/2023->>April/615629.html (Thanks
>> for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
Kewen Lin changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-1235-20230525094833-g0d1e0d7433c-checking-yes-rtl-df-extra-aarch64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230525 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85944
--- Comment #11 from Andrew Pinski ---
*** Bug 109976 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109976
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109976
Bug ID: 109976
Summary: error: is not a constant expression in std::equal()
with _GLIBCXX_DEBUG
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85944
Andrew Pinski changed:
What|Removed |Added
CC||ed at catmur dot uk
--- Comment #10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 109975, which changed state.
Bug 109975 Summary: error: '(((int*)(&.X::a)) != 0)' is not a
constant expression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109975
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109975
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109975
Bug ID: 109975
Summary: error: '(((int*)(&.X::a)) != 0)' is not a
constant expression
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109974
Bug ID: 109974
Summary: RISCV: RVV VSETVL Pass ICE in SLP auto-vectorization
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56439
Andrew Pinski changed:
What|Removed |Added
CC||NickParker at Eaton dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65082
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
--- Comment #4 from JuzheZhong ---
(In reply to Kewen Lin from comment #3)
> I'll take a look first.
Thanks a lot. I am sorry for causing such issue to you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610
--- Comment #14 from Hongtao.liu ---
Fixed for GCC14.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109858
--- Comment #11 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:4fb66b2329319e9b47e89200d613b6f741a114fc
commit r14-1252-g4fb66b2329319e9b47e89200d613b6f741a114fc
Author: liuhongt
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610
--- Comment #13 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:4fb66b2329319e9b47e89200d613b6f741a114fc
commit r14-1252-g4fb66b2329319e9b47e89200d613b6f741a114fc
Author: liuhongt
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65082
--- Comment #6 from Andrew Pinski ---
See bug 43491 comment #12 for some analysis of this issue really.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65082
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36884
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
Kewen Lin changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52396
Andrew Pinski changed:
What|Removed |Added
Known to fail||5.4.0, 6.4.0, 7.5.0
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10050
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|middle-end
--- Comment #11 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109973
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.2
Summary|Wrong code for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109973
--- Comment #1 from Benji Smith ---
Created attachment 55159
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55159=edit
A compressed preprocessed minimal repro of the VPAND/VPTEST issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38264
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Confirmed.
> The code looks slightly different now as find_edge has been inlined and
> merged with checking for eh edges.
Which was done with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109973
Bug ID: 109973
Summary: Wrong code for AVX2 since 13.1 by combining VPAND and
VPTEST
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21827
Andrew Pinski changed:
What|Removed |Added
Known to work||6.1.0
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109951
--- Comment #5 from Iain Sandoe ---
Since AFAICT, there is only one piece of Darwin-specific code in the libgomp
TCL (which adds -shared-libgcc), I would expect the base phenomenon to be the
same on Linux. What is not obvious there is why it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109951
--- Comment #4 from Iain Sandoe ---
(In reply to Thomas Schwinge from comment #3)
> Looking at your "test x86_64 multilib on i686" case.
The situation is simply mirrored for an x86_64 host with an i686 non-native
lib.
> First, is my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #8 from Andrew Pinski ---
(In reply to Scott Zhong from comment #7)
> If I understand you correctly, the following example should produce an
> uninitialized variable diagnostics and the fact that it doesn't means it is
> a bug in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #7 from Scott Zhong ---
(In reply to rguent...@suse.de from comment #6)
> > Am 25.05.2023 um 20:24 schrieb pinskia at gcc dot gnu.org
> > :
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
> >
> > --- Comment #5 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109972
Bug ID: 109972
Summary: RISC-V: Could use umodsi3/udivsi3/divsi3 libcalls for
32-bit division/remainder on RV64 without M extension
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
--- Comment #2 from JuzheZhong ---
It seems this condition:
+ /* If we're vectorizing a loop that uses length "controls" and
+ can iterate more than once, we apply decrementing IV approach
+ in loop control. */
+ if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
--- Comment #1 from JuzheZhong ---
It seems this condition:
+ /* If we're vectorizing a loop that uses length "controls" and
+ can iterate more than once, we apply decrementing IV approach
+ in loop control. */
+ if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109971
Bug ID: 109971
Summary: [14 regression] Several powerpc64 vector test cases
fail after r14-1242-gf574e2dfae7905
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109951
Thomas Schwinge changed:
What|Removed |Added
CC||macro at orcam dot me.uk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49263
--- Comment #40 from Oleg Endo ---
(In reply to Alexander Klepikov from comment #39)
>
> I'm sorry, but .md lang is too complicated for me.
Yeah, it looks alien at first sight. But it's where a lot of things happen
w.r.t. instruction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109970
Bug ID: 109970
Summary: -Wstringop-overflow should work with parameter forward
declarations
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109948
--- Comment #7 from anlauf at gcc dot gnu.org ---
Some more digging: in the case when ref->u.ar.as is NULL, it appears that
e->symtree->n.sym->assoc->target->ref->u.ar.as
is properly set.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109933
--- Comment #12 from Rory Bolt ---
(In reply to Patrick O'Neill from comment #11)
> I can confirm that your fix does *not* break the testsuite on little endian.
>
> We also recently added inline subword atomics to GCC 13, will this code also
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #6 from rguenther at suse dot de ---
> Am 25.05.2023 um 20:24 schrieb pinskia at gcc dot gnu.org
> :
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
>
> --- Comment #5 from Andrew Pinski ---
> (In reply to Scott Zhong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108896
Nick Desaulniers changed:
What|Removed |Added
CC||ndesaulniers at google dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109174
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109173
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109948
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966
--- Comment #4 from Andrew Pinski ---
(In reply to Marek Polacek from comment #3)
Slightly more reduced (removing the template):
```
struct k {
k(const char *);
};
struct M {
k name;
int j = 42;
int default_value = j;
};
struct S {
M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109933
--- Comment #11 from Patrick O'Neill ---
I can confirm that your fix does *not* break the testsuite on little endian.
We also recently added inline subword atomics to GCC 13, will this code also
need to change for big endian?
Trunk:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #5 from Andrew Pinski ---
(In reply to Scott Zhong from comment #4)
> The move constructor "steals" resources rather than make copies of them, and
> leave the argument in some valid but otherwise indeterminate state. It is
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
--- Comment #4 from Scott Zhong ---
The move constructor "steals" resources rather than make copies of them, and
leave the argument in some valid but otherwise indeterminate state. It is
reasonable that size_ is not initialized in the context
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109967
Andrew Pinski changed:
What|Removed |Added
Summary|Wrong code at -O2 on|[10/11/12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109967
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux-gnu
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108896
--- Comment #45 from qinzhao at gcc dot gnu.org ---
the first version of the patches were submitted to upstream today for
discussion:
https://gcc.gnu.org/pipermail/gcc-patches/2023-May/619708.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82931
Georg-Johann Lay changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49263
--- Comment #39 from Alexander Klepikov
---
> The tst insn is mainly formed by the combine pass, which relies on certain
> insn patterns and combinations thereof. See also sh.md, around line 530.
I'm sorry, but .md lang is too complicated for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109969
Gaius Mulley changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104327
--- Comment #13 from CVS Commits ---
The releases/gcc-12 branch has been updated by Georg-Johann Lay
:
https://gcc.gnu.org/g:0537c71aa7ef88c4ffe754cf7af81e346273b079
commit r12-9655-g0537c71aa7ef88c4ffe754cf7af81e346273b079
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82931
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Georg-Johann Lay
:
https://gcc.gnu.org/g:4d39f68b891ed2ac7aca5ef24119f50976b84c22
commit r12-9654-g4d39f68b891ed2ac7aca5ef24119f50976b84c22
Author: Georg-Johann
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104327
--- Comment #12 from CVS Commits ---
The releases/gcc-13 branch has been updated by Georg-Johann Lay
:
https://gcc.gnu.org/g:6506590e70e57ed8d7fb68ab9443e31c31208fb0
commit r13-7378-g6506590e70e57ed8d7fb68ab9443e31c31208fb0
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109969
Bug ID: 109969
Summary: Linking large project causes an ICE
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104327
--- Comment #11 from CVS Commits ---
The master branch has been updated by Georg-Johann Lay :
https://gcc.gnu.org/g:66cc0cb0f44f17049f61af6755043999c4fa5a24
commit r14-1245-g66cc0cb0f44f17049f61af6755043999c4fa5a24
Author: Georg-Johann Lay
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82931
--- Comment #6 from CVS Commits ---
The releases/gcc-13 branch has been updated by Georg-Johann Lay
:
https://gcc.gnu.org/g:a499ab08d18eff4ca9c079cafaee0708d2bcbf20
commit r13-7377-ga499ab08d18eff4ca9c079cafaee0708d2bcbf20
Author: Georg-Johann
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #9 from Jakub Jelinek ---
Why?
It should be enabled by default only if it is effectively mandated by the ABI
and/or doesn't affect performance at all (and is actually useful in functions
that don't need it like functions with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #8 from AK ---
Should we enable frame-pointers by default for RISCV64 as well?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103794
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104350
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82931
--- Comment #5 from CVS Commits ---
The master branch has been updated by Georg-Johann Lay :
https://gcc.gnu.org/g:ff0a6900700636ac4c7f40b88490a20d19a68db3
commit r14-1244-gff0a6900700636ac4c7f40b88490a20d19a68db3
Author: Georg-Johann Lay
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109968
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Reduced testcase without -fsanitize=address:
Sorry missed one undefined type.
Here is the corrected reduced testcase:
```
extern int write1 (int __fd, const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109968
Andrew Pinski changed:
What|Removed |Added
Summary|False Warning |False Warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109933
--- Comment #10 from Rory Bolt ---
Tested and verified on little endian too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109956
--- Comment #12 from Martin Uecker ---
The C standard says "However, when a . (or -> ) operator has a left operand
that is (a pointer to) a structure with a flexible array member and the right
operand names that member, it behaves as if that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #7 from Florian Weimer ---
(In reply to Jakub Jelinek from comment #6)
> I think aarch64 defaults to -fno-omit-frame-pointer anyway.
> /* Disable fomit-frame-pointer by default. */
> { OPT_LEVELS_ALL,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #6 from Jakub Jelinek ---
I think aarch64 defaults to -fno-omit-frame-pointer anyway.
/* Disable fomit-frame-pointer by default. */
{ OPT_LEVELS_ALL, OPT_fomit_frame_pointer, NULL, 0 },
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
--- Comment #5 from Andrew Pinski ---
(In reply to AK from comment #4)
> On AArch64 (typically mobile platforms) app developers typically would
> enable frame pointers by default because it helps with crash reporting.
s/AArch64 (typically
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109968
--- Comment #1 from Andrew Pinski ---
From
https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Instrumentation-Options.html#index-fsanitize_003daddress
:
Note that sanitizers tend to increase the rate of false positive warnings, most
notably those
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966
--- Comment #3 from Marek Polacek ---
// PR c++/109966
struct M;
template struct __array_traits {
typedef M _Type[_Nm];
};
template struct array {
typename __array_traits<_Nm>::_Type _M_elems;
};
struct basic_string_view {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109968
Bug ID: 109968
Summary: False Warning stringop-overread when -O2 and
-fsanitize=address used
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100811
AK changed:
What|Removed |Added
CC||hiraditya at msn dot com
--- Comment #4 from AK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109947
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|SUSPENDED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109965
--- Comment #4 from Jonathan Wakely ---
(In reply to Saifi Khan from comment #2)
> Short of re-compiling the doxygen code with string literal changed to
> "Components" i can't seem to find any other way.
Well if nothing else works, we can just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109791
--- Comment #16 from Andrew Pinski ---
(In reply to Richard Biener from comment #15)
> Created attachment 55155 [details]
> patch unfolding such PHIs
>
> Updated PHI unfolding patch. Tests fine besides mentioned diagnostic
> regressions.
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109965
--- Comment #3 from Saifi Khan ---
Trying the 'custom' layout approach that you suggested.
The file modified is
/opt/gcc/src/libstdc++-v3/doc/doxygen/DoxygenLayout.xml
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109965
--- Comment #2 from Saifi Khan ---
Yes, you are right.
Doxygen has 'Modules' hard-coded everywhere in the code as they have used the
word as an organizing principle.
It starts with enum Kind defined in LayoutNavEntry
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109967
Bug ID: 109967
Summary: Wrong code at -O2 on x86_64-linux-gnu
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99195
--- Comment #17 from CVS Commits ---
The master branch has been updated by Kyrylo Tkachov :
https://gcc.gnu.org/g:560bb845321f5ad039a318a081b0e88d9900f5cb
commit r14-1241-g560bb845321f5ad039a318a081b0e88d9900f5cb
Author: Kyrylo Tkachov
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 109801, which changed state.
Bug 109801 Summary: -Wmaybe-uninitialized warning with -O1 on move constructor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109801
Richard Biener changed:
What|Removed |Added
Resolution|--- |INVALID
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109965
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-05-25
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105541
Patrick Palka changed:
What|Removed |Added
CC||egor.pugin at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103212
Patrick Palka changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109964
--- Comment #4 from rsandifo at gcc dot gnu.org
---
(In reply to Richard Biener from comment #3)
> So the bug in the vectorizer is that it does
>
> t.ii:14:5: note: can narrow to signed:16 without loss of precision: _31 =
> 1 >> _30;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109800
--- Comment #1 from CVS Commits ---
The master branch has been updated by Alex Coplan :
https://gcc.gnu.org/g:f5298d9969b4fa34ff3aecd54b9630e22b2984a5
commit r14-1239-gf5298d9969b4fa34ff3aecd54b9630e22b2984a5
Author: Alex Coplan
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966
Richard Biener changed:
What|Removed |Added
Known to work||12.3.0
Summary|[13.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109966
Bug ID: 109966
Summary: [13.1 Regression] ICE in implify_var_or_parm_decl, à
gimplify.cc:3058
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109791
Richard Biener changed:
What|Removed |Added
Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109791
Richard Biener changed:
What|Removed |Added
Attachment #55047|0 |1
is obsolete|
1 - 100 of 158 matches
Mail list logo
