https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104562
--- Comment #1 from Tobias Burnus ---
That should be already fixed by
r12-7250-g4d74ea551734694c225643c4069b1b4d4d2b05ed
"Fortran/OpenMP: Fix depend-clause handling for c_ptr"
Crossref: PR 104545 was about the original issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104545
--- Comment #2 from Tobias Burnus ---
Crossrefs:
* PR 104562 shows an issue caused by the original commit.
* r12-7250-g4d74ea551734694c225643c4069b1b4d4d2b05ed
"Fortran/OpenMP: Fix depend-clause handling for c_ptr"
fixes that issue + an is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104024
Kewen Lin changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101456
--- Comment #9 from Hongtao.liu ---
(In reply to H.J. Lu from comment #8)
> It turns out that reading YMM registers with all zero bits needs VZEROUPPER
> on Sandy Bride, Ivy Bridge, Haswell, Broadwell and Alder Lake to avoid
> SSE <-> AVX transi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104551
--- Comment #4 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #3)
> (In reply to Hongtao.liu from comment #2)
> > let me take a look.
>
> Start with r12-7216
for (bool a = 0; a < (bool)var_11; a = 2)
for (unsigned b = 0; b <
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104562
Bug ID: 104562
Summary: [12 regression] gfortran.dg/gomp/depend-5.f90 fails
after r12-7242-g3939c1b11279dc
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104551
--- Comment #3 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #2)
> let me take a look.
Start with r12-7216
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104551
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102006
--- Comment #11 from Dmitriano ---
It was UB in my code, I dereference a pointer to an object that does not exist.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90533
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-02-16
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104548
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100795
Andrew Pinski changed:
What|Removed |Added
CC||Berenger.Berthoul at onera dot
fr
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104561
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104561
康桓瑋 changed:
What|Removed |Added
CC||hewillk at gmail dot com
--- Comment #1 from 康桓瑋
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104107
Jason Merrill changed:
What|Removed |Added
Known to work||12.0
Summary|[9/10/11/12 Reg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95036
Jason Merrill changed:
What|Removed |Added
Known to work||12.0
Summary|[9/10/11/12 Regr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104561
Bug ID: 104561
Summary: std::ranges::sort, std::ranges::stable_sort and
std::ranges::partial_sort do not support proxy
references
Product: gcc
Version: og11 (dev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104557
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104551
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Summary|Wrong code with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104530
--- Comment #2 from Andrew Macleod ---
mmm. tricky.
Imports: b.0_1 d.3_7
Exports: b.0_1 _2 _3 d.3_7 _8
_2 : b.0_1(I)
_3 : b.0_1(I) _2
_8 : b.0_1(I) _2 _3 d.3_7(I)
:
b.0_1 = b;
_2 = b.0_1 == 0B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100442
--- Comment #4 from Andres Freund ---
> Ending up with an excessive range isn't uncommon in code that freely converts
> between signed and unsigned integers (e.g., by passing an int to a size_t
> argument) and involves conditionals like those
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104559
--- Comment #1 from Andrew Pinski ---
>From include/bits/stl_bvector.h"
iterator
#if __cplusplus >= 201103L
insert(const_iterator __position, const bool& __x = bool())
#else
insert(iterator __position, const bool& __x = bool()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
--- Comment #5 from Qing Zhao ---
> On Feb 15, 2022, at 3:38 PM, pinskia at gcc dot gnu.org
> wrote:
> Maybe __builtin_clear_padding lowering should mark the load "MEM[(struct
> vx_audio_level *)&info]" as not needing a warning.
>
This sound
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104560
Bug ID: 104560
Summary: False positive from -Wanalyzer-free-of-non-heap seen
with rdma-core
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104559
Bug ID: 104559
Summary: vector v; v.insert(v.begin()); compiles, but it
shouldn't
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104526
Andrew Macleod changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104526
--- Comment #4 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:e15425e899e4a9eec768cf74aaf36cdbf1d29913
commit r12-7253-ge15425e899e4a9eec768cf74aaf36cdbf1d29913
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97114
Martin Jambor changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104554
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104524
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102692
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #4 from Andrew P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104524
--- Comment #1 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:84832cab6e43db7fa10ec53d15f8f8457aa31080
commit r12-7252-g84832cab6e43db7fa10ec53d15f8f8457aa31080
Author: David Malcolm
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102692
--- Comment #5 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:1e2fe6715a949f80c1204ae244baad3cd80ffaf0
commit r12-7251-g1e2fe6715a949f80c1204ae244baad3cd80ffaf0
Author: David Malcolm
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
--- Comment #3 from qinzhao at gcc dot gnu.org ---
the root cause for this bug is due to the new call to __builtin_clear_padding
added by -ftrivial-auto-var-init=pattern, this is treated as a use of the
uninitialized variable during early uninit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104515
--- Comment #3 from Jonathan Wakely ---
aka r9-84-gcdc184174ce56d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104515
--- Comment #2 from GBE ---
I don't know if it helps - but I used git-bisect to find the original commit
that added this issue: cdc184174ce
https://github.com/gcc-mirror/gcc/commit/cdc184174ce
It indeed has to do with trivial destructors and c
2b37a5-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220215 (experimental) (GCC)
unk//binary-trunk-r12-7249-20220215180935-g8e84b2b37a5-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.0.1 20220215 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276
--- Comment #12 from qinzhao at gcc dot gnu.org ---
I will go with the following solution:
1. avoid emitting switch-unreachable warnings for -ftrivial-auto-var-init;
2. adding a new option -Wtrivial-auto-var-init to emit warnings for the
switch-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104556
Bug ID: 104556
Summary: ICE in gfc_conv_class_to_class, at
fortran/trans-expr.cc:1267
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104555
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104555
Bug ID: 104555
Summary: ICE in gfc_compare_derived_types, at
fortran/interface.cc:628
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104554
Bug ID: 104554
Summary: ICE in check_assumed_size_reference, at
fortran/resolve.cc:1650
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104553
G. Steinmetz changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104553
Bug ID: 104553
Summary: ICE in aggregate_value_p, at function.cc:2087
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #42 from Randy ---
(In reply to Jonathan Wakely from comment #41)
> So then basically the same as what I said:
>
> (In reply to Jonathan Wakely from comment #37)
> > (Your segfaults are probably because you're using c_str() on a temp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
--- Comment #3 from Roland Illig ---
(In reply to Iain Buclaw from comment #2)
> (In reply to Roland Illig from comment #0)
> > > -fdump-cxx-spec=Write all declarations as C++ code to
> > > .
> >
> > The '' should be '' as well.
> >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
Iain Buclaw changed:
What|Removed |Added
CC||ibuclaw at gdcproject dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97240
Andris Pavenis changed:
What|Removed |Added
Known to fail||10.3.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104552
Bug ID: 104552
Summary: Mistakes in strings to be translated in GCC 12
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100874
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100874
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:8e84b2b37a541b27feea69769fc314d534464ebd
commit r12-7249-g8e84b2b37a541b27feea69769fc314d534464ebd
Author: Richard Sandiford
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104551
Bug ID: 104551
Summary: Wrong code with -O3 for skylake-avx512,
icelake-server, and sapphirerapids
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
Iain Sandoe changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104549
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104532
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95137
--- Comment #47 from Jakub Jelinek ---
On the #c42 testcase the false positive warning is gone with
r12-3529-g70ee703c479081ac2ea67eb67041551216e66783
which has been backported in
r11-9062-g17e4e6e33d13e0cf09c76cba06c5fc20deab8bb4 to 11.x.
Is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104507
Patrick Palka changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100056
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104531
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2022-02-15
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276
--- Comment #11 from qinzhao at gcc dot gnu.org ---
(In reply to rguent...@suse.de from comment #10)
> I think it definitely makes sense to diagnose that we are not
> following -ftrivial-auto-init-var=X for a decl. Maybe we should
> do that wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-02-15
Ever confirm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
--- Comment #1 from qinzhao at gcc dot gnu.org ---
Kees reported the following issue with -ftrivial-auto-var-init=pattern. the
testing case was reduced from Kernel building.
$ cat warns.i
struct vx_audio_level {
int has_monitor_level : 1;
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104550
Bug ID: 104550
Summary: bogus warning from -Wuninitialized +
-ftrivial-auto-var-init=pattern
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104549
Bug ID: 104549
Summary: Missing variable at O2/O3 likely caused by
-fearly-inlining
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104547
--- Comment #8 from Jonathan Wakely ---
Thanks for looking at it! There's no urgency here from my point of view, I just
wanted to get it into bugzilla so I could concentrate on other things. Parking
this until stage1 makes sense.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
--- Comment #9 from Jonathan Wakely ---
(In reply to Jakub Jelinek from comment #7)
> I would say that is a terrible design...
Yes, I completely agree, but I don't see why GCC should be in the business of
diagnosing other people's junk :-)
Mayb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
--- Comment #8 from Jonathan Wakely ---
(In reply to Austin Morton from comment #5)
> https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553182.html
>
> I sent a patch to do exactly that in 2020 and it was not accepted.
Thanks. The review
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104547
--- Comment #7 from Andrew Macleod ---
Created attachment 52447
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52447&action=edit
proposed patch
(In reply to Jakub Jelinek from comment #5)
> If you mean with -O3 on the
> #include
>
> voi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
--- Comment #7 from Jakub Jelinek ---
I would say that is a terrible design...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102645
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Keyw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
--- Comment #6 from Jonathan Wakely ---
(In reply to Jakub Jelinek from comment #4)
> Exactly. Seems clang doesn't bother with it and allows anything, but it is
> unclear if that is the best thing to do.
MSVC ignores any tokens after the region
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
--- Comment #11 from Michael Matz ---
(In reply to Richard Biener from comment #5)
> in particular the comment in bb_prevents_fusion_p saying
>
> /* BB is duplicated by outer unrolling and then all N-1 first copies
> move into the body o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104542
--- Comment #1 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:6cfb7ffb659fd6b87a21312021ab023a06e8f6be
commit r12-7244-g6cfb7ffb659fd6b87a21312021ab023a06e8f6be
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
--- Comment #5 from Austin Morton ---
(In reply to Jonathan Wakely from comment #3)
> The docs raise some questions.
>
> They say that a #pragma region must be ended by a #pragma endregion. Should
> the compiler check that and issue a diagnosti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101456
H.J. Lu changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104544
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=85487
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104544
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
Jonathan Wakely changed:
What|Removed |Added
Keywords||easyhack
--- Comment #3 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102087
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102645
Richard Biener changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #3 from Ri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
--- Comment #10 from Richard Biener ---
*** Bug 103873 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103873
Richard Biener changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
--- Comment #9 from Richard Biener ---
*** Bug 103300 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103300
Richard Biener changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #41 from Jonathan Wakely ---
So then basically the same as what I said:
(In reply to Jonathan Wakely from comment #37)
> (Your segfaults are probably because you're using c_str() on a temporary
> string, so accessing the pointer afte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #40 from Randy ---
(In reply to Jonathan Wakely from comment #39)
> (In reply to Randy from comment #38)
> > std::string is not thread safe, this is why vstring is used (from my
> > memory).
>
> That's totally wrong, vstring has no m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96881
--- Comment #5 from Richard Biener ---
The CD-DCE issue is that we do not mark CLOBBERs as necessary but in the end
choose to keep them, even if we elided its control dependences. The following
fixes that in the simplest conservative way.
This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104547
--- Comment #6 from Jonathan Wakely ---
(In reply to Jakub Jelinek from comment #5)
> If you mean with -O3
Yes, sorry for not saying so: all examples were compiled with -O3.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #39 from Jonathan Wakely ---
(In reply to Randy from comment #38)
> std::string is not thread safe, this is why vstring is used (from my
> memory).
That's totally wrong, vstring has no more thread-safety than std::string has.
The sam
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100499
Bug 100499 depends on bug 104519, which changed state.
Bug 104519 Summary: [12 Regression] wrong code at -Os on x86_64-linux-gnu and
char as induction variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104519
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104519
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
Richard Biener changed:
What|Removed |Added
Target Milestone|12.0|9.5
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104543
--- Comment #6 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:d03a67dc69251dc86c0772a432380a6e9bcb8617
commit r12-7243-gd03a67dc69251dc86c0772a432380a6e9bcb8617
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63311
Mark Wielaard changed:
What|Removed |Added
CC||mark at gcc dot gnu.org
--- Comment #19
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104547
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2022-02-15
CC|
1 - 100 of 141 matches
Mail list logo