https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89115
--- Comment #6 from Richard Biener ---
Author: rguenth
Date: Thu Jan 31 08:09:59 2019
New Revision: 268414
URL: https://gcc.gnu.org/viewcvs?rev=268414&root=gcc&view=rev
Log:
2019-01-31 Richard Biener
PR rtl-optimization/89115
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89119
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89125
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89124
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Thu Jan 31 08:20:45 2019
New Revision: 268415
URL: https://gcc.gnu.org/viewcvs?rev=268415&root=gcc&view=rev
Log:
PR sanitizer/89124
* ipa-inline.c (sanitize_attrs_match_fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89130
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89124
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88170
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135
--- Comment #3 from Shubham Narlawar ---
I could reproduce the ICE on gcc-8.2 but not on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89134
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Status|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89115
Richard Biener changed:
What|Removed |Added
Known to work||9.0
Known to fail|9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87199
--- Comment #3 from Ev Drikos ---
Created attachment 45573
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45573&action=edit
program output & gcc configuration in Yosemite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87199
--- Comment #4 from Ev Drikos ---
Created attachment 45574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45574&action=edit
program output & gcc configuration in Sierra
Hello,
Having run this small test in older systems also, Yosemite (10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84733
Paolo Carlini changed:
What|Removed |Added
Priority|P4 |P3
Severity|minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81651
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from Domin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89115
--- Comment #8 from Richard Biener ---
Author: rguenth
Date: Thu Jan 31 10:00:26 2019
New Revision: 268416
URL: https://gcc.gnu.org/viewcvs?rev=268416&root=gcc&view=rev
Log:
2019-01-31 Richard Biener
Backport from mainline
20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
Bug ID: 89136
Summary: libbacktrace/elf.c:2941: suspicious assignment
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
David Binderman changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
nsz at gcc dot gnu.org changed:
What|Removed |Added
CC||nsz at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84974
Paolo Carlini changed:
What|Removed |Added
Summary|[8/9 Regression] ICE: |[8 Regression] ICE:
|S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89123
rdapp at linux dot ibm.com changed:
What|Removed |Added
CC||rdapp at linux dot ibm.com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #20 from Uroš Bizjak ---
(In reply to nsz from comment #19)
> that code was there for a reason.. now aarch64 fails because it cannot
> detect if the flags are supported or not.
>
> so if detection is turned off then on aarch64 "suppo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89137
Bug ID: 89137
Summary: gcc/omp-low.c:7135: possible read of uninit memory ?
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #21 from nsz at gcc dot gnu.org ---
this fix undid the change for bug 78314
do you plan to backport it to gcc 7,8 branches ?
note that in principle on targets where trapping is not supported
the "immediate alternate exception handling
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89137
--- Comment #1 from Jakub Jelinek ---
As this is all in
if (code == OMP_FOR || code == OMP_SECTIONS)
guarded block, that warning is obviously a false positive.
I guess I can just drop the " if (code == OMP_SECTIONS)" to make it happy.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #22 from Uroš Bizjak ---
(In reply to nsz from comment #21)
> this fix undid the change for bug 78314
> do you plan to backport it to gcc 7,8 branches ?
>
> note that in principle on targets where trapping is not supported
> the "imm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #23 from Uroš Bizjak ---
(In reply to Uroš Bizjak from comment #22)
> (In reply to nsz from comment #21)
> > this fix undid the change for bug 78314
> > do you plan to backport it to gcc 7,8 branches ?
Yes, I'd like to backport the f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
Tom de Vries changed:
What|Removed |Added
Keywords||patch
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89138
Bug ID: 89138
Summary: ICE on valid C++11 code: in expand_expr_real_1, at
expr.c:9993
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89137
Richard Biener changed:
What|Removed |Added
Keywords||openmp
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135
--- Comment #4 from Richard Biener ---
Author: rguenth
Date: Thu Jan 31 11:51:59 2019
New Revision: 268417
URL: https://gcc.gnu.org/viewcvs?rev=268417&root=gcc&view=rev
Log:
2019-01-31 Richard Biener
PR tree-optimization/89135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89135
Richard Biener changed:
What|Removed |Added
Known to work||9.0
Summary|[7/8/9 Regressio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81651
--- Comment #3 from Thomas Koenig ---
(In reply to Dominique d'Humieres from comment #2)
> What is a "fully qualified module name"?
Error: Module file /full/path/to/module/mymodule.mod is bletchful.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89115
--- Comment #9 from Richard Biener ---
Author: rguenth
Date: Thu Jan 31 12:05:19 2019
New Revision: 268418
URL: https://gcc.gnu.org/viewcvs?rev=268418&root=gcc&view=rev
Log:
2019-01-31 Richard Biener
Backport from mainline
20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89115
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
--- Comment #3 from Tom de Vries ---
Author: vries
Date: Thu Jan 31 12:17:32 2019
New Revision: 268419
URL: https://gcc.gnu.org/viewcvs?rev=268419&root=gcc&view=rev
Log:
[libbacktrace] Fix .gnu_debugaltlink build-id check
The 'debugaltlink_name
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
Tom de Vries changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89138
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
--- Comment #6 from Tom de Vries ---
(In reply to Jakub Jelinek from comment #4)
> Shouldn't we have a warning for this =+ vs. += case (of course, =- is fine)?
I found PR45358 - "Diagnostic could be issued for old C style a =+ b and
similar case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45358
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #5 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79966
Uroš Bizjak changed:
What|Removed |Added
Target Milestone|7.5 |9.0
Summary|[7 Regression] run
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89134
Jiangning Liu changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88494
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88494
Richard Biener changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88494
Jakub Jelinek changed:
What|Removed |Added
CC||vekumar at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84101
--- Comment #10 from Jakub Jelinek ---
lower-subreg.c doesn't consider this for multiple reasons: 1) it doesn't have
VEC_CONCAT handling, but that could be easily added 2) V2DImode isn't
considered, because its move cost is the same as scalar mov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89008
--- Comment #13 from Bill Schmidt ---
Author: wschmidt
Date: Thu Jan 31 13:53:06 2019
New Revision: 268422
URL: https://gcc.gnu.org/viewcvs?rev=268422&root=gcc&view=rev
Log:
2018-01-31 Bill Schmidt
PR tree-optimization/89008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89116
Jakub Jelinek changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88988
Jakub Jelinek changed:
What|Removed |Added
Summary|[8/9 Regression] ICE: |[8 Regression] ICE:
|S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88932
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88394
--- Comment #2 from Jakub Jelinek ---
Related to e.g. PR89138 - lambdas and VLAs don't play nicely together right
now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89104
--- Comment #5 from Wilco ---
(In reply to Jakub Jelinek from comment #4)
> I really don't like these aarch64 warnings, declare simd is an optimization
> (admittedly with ABI consequences) and warning about this by default is
> weird,
> + it is g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89104
--- Comment #6 from Jakub Jelinek ---
(In reply to Wilco from comment #5)
> I agree backend specific warnings are not ideal but it's unclear whether a
> better solution exists beyond just not emitting these warnings at all and
> letting the user
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89139
Bug ID: 89139
Summary: GCC emits code for static functions that aren't used
by the optimized code
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89140
Bug ID: 89140
Summary: libiberty/pex-unix.c fails to compile in
aarch64-to-x86_64 cross build
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88932
bin.cheng changed:
What|Removed |Added
CC||amker.cheng at gmail dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89139
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
--- Comment #5 from Jason Merrill ---
Author: jason
Date: Thu Jan 31 15:03:21 2019
New Revision: 268424
URL: https://gcc.gnu.org/viewcvs?rev=268424&root=gcc&view=rev
Log:
PR c++/88752 - ICE with lambda and constexpr if.
In this testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88932
--- Comment #5 from rguenther at suse dot de ---
On Thu, 31 Jan 2019, amker.cheng at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88932
>
> bin.cheng changed:
>
>What|Removed |Added
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Jason Merrill changed:
What|Removed |Added
Summary|[8/9 Regression] ICE in |[8 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89141
Bug ID: 89141
Summary: Documentation of -H ignores effect of include guards
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86487
Vladimir Makarov changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86487
--- Comment #10 from avieira at gcc dot gnu.org ---
Hi Vlad,
I don't think it is a duplication. I believe this PR is caused by an issue with
'uses_hard_regs_p' and paradoxical subregs. I proposed a patch in
https://gcc.gnu.org/ml/gcc-patches/2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
--- Comment #12 from nsz at gcc dot gnu.org ---
this got reverted because of bug 88678
and because compile time and runtime support_halting are different.
the compile time value is unconditionally true, which is wrong for
aarch64 and arm:
gcc/f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Matthew Malcomson changed:
What|Removed |Added
CC||matmal01 at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89136
--- Comment #7 from David Binderman ---
(In reply to Tom de Vries from comment #5)
> Thanks for finding and reporting this.
You are welcome. I was testing new clang-8.0.0-rc1
and hadn't compiled gcc with clang for a while.
clang warns for "=+"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88596
Vladimir Makarov changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89138
Arseny Solokha changed:
What|Removed |Added
CC||asolokha at gmx dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
--- Comment #13 from Uroš Bizjak ---
(In reply to nsz from comment #12)
> i don't know how to change this to false for IEEE_SUPPORT_HALTING
> on aarch64 and arm targets, but that would be a possible fix.
--cut here--
Index: libgfortran/config/fp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88596
--- Comment #2 from Arseny Solokha ---
I'll check it on the next trunk snapshot and report back next Monday.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #30 from Jakub Jelinek ---
(In reply to Matthew Malcomson from comment #29)
> I've been working on a patch that does very similar to the draft patch posted
> above, and I notice a few things I've tried to avoid in it.
> I doubt there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89008
--- Comment #14 from Bill Schmidt ---
Author: wschmidt
Date: Thu Jan 31 17:14:36 2019
New Revision: 268425
URL: https://gcc.gnu.org/viewcvs?rev=268425&root=gcc&view=rev
Log:
2018-01-31 Bill Schmidt
Backport from mainline
2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88107
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89142
Bug ID: 89142
Summary: Allow poisoning identifier from the command line
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
--- Comment #14 from nsz at gcc dot gnu.org ---
(In reply to Uroš Bizjak from comment #13)
> (In reply to nsz from comment #12)
> > i don't know how to change this to false for IEEE_SUPPORT_HALTING
> > on aarch64 and arm targets, but that would be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78314
nsz at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|nsz at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89142
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #31 from Matthew Malcomson ---
(In reply to Jakub Jelinek from comment #30)
> (In reply to Matthew Malcomson from comment #29)
> > I've been working on a patch that does very similar to the draft patch
> > posted
> > above, and I not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89142
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #2 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89122
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89122
--- Comment #3 from David Malcolm ---
Author: dmalcolm
Date: Thu Jan 31 18:09:29 2019
New Revision: 268426
URL: https://gcc.gnu.org/viewcvs?rev=268426&root=gcc&view=rev
Log:
Fix bogus fix-it for FLT_MAX (PR c/89122)
PR c/89122 reports that we e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87295
--- Comment #7 from Jan Hubicka ---
It seems that this breaks debug-types-sections w/o LTO as well now.
./xgcc -B ./ -O2 -g ~/tramp3d-v44.ii -fdebug-types-section
/aux/hubicka/tramp3d-v4b.cpp:56088:1: internal compiler error: in
build_abbrev_tabl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88596
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87451
--- Comment #11 from Steve Ellcey ---
(In reply to Richard Biener from comment #10)
> (In reply to Steve Ellcey from comment #9)
> Looks like that's because of different expected comment characters,
> # vs. // in your file. The pattern for the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88150
Johannes Pfau changed:
What|Removed |Added
CC||code at dawg dot eu,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88917
Jakub Jelinek changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #2 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87864
Johannes Pfau changed:
What|Removed |Added
CC||johannespfau at gmail dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89143
Bug ID: 89143
Summary: [9 Regression] comparison of abs(i) against excessive
constant less than UXXX_MAX no longer folded
Product: gcc
Version: 9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89143
Martin Sebor changed:
What|Removed |Added
Keywords||missed-optimization
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89127
--- Comment #3 from Martin Sebor ---
I see what you mean. It might perhaps be useful to mention the bigint rule of
thumb in the manual. At the same time, the warning still doesn't work even
under this restricted interpretation. For example, in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88917
Florian Weimer changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89134
David Malcolm changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89144
Bug ID: 89144
Summary: GCC emits undefined references when a constexpr
initializer_list appears in a template function
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89084
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89125
--- Comment #8 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #6)
> Checking with FreeBSD developers on C99 compliance.
The answer is 'no'. FreeBSD's C runtime libraries
(libc+libm) are not fully C99 complaint. It is a shame
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89084
--- Comment #2 from David Malcolm ---
Fails this assertion:
1892 gcc_checking_assert (vnode->definition);
(gdb) p vnode
$3 =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89143
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88296
--- Comment #5 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #3)
> for Vlad the question
> is just whether r266862 is a real fix or just made it latent. Given that
> both are IRA costs changes, I assume it is a real fix.
I'v
1 - 100 of 148 matches
Mail list logo