https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121145
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Component|libfortran |fortran
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121145
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2025-07-17
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118580
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #23 from anlauf at gcc dot gnu.org ---
(In reply to Richard Biener from comment #22)
> (In reply to Richard Biener from comment #21)
> > A pragmatic solution might be to pattern-match (by name) some of the
> > af
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #20 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #18)
> Plus, ASYNCHRONOUS means that the variable can change even in
> the absence of a call, so
>
>CALL FOO (A)
>A = 2
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #16 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #15)
> (In reply to anlauf from comment #14)
> > (In reply to Thomas Koenig from comment #13)
> > > I think we have quite a few bad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #14 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #13)
> I think we have quite a few bad choices here, each with different drawbacks.
> I don't think we should do nothing, or pessimize ex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #10)
> The problem is not restricted to mpi_isend.
This was supposed to read: ... not restricted to mpi_irecv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120843
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120843
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to GCC Commits from comment #6)
> The master branch has been updated by Andre Vehreschild :
>
> https://gcc.gnu.org/g:15413e05eb9cde976b8890cd9b597d0a41a8eb27
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Martin Jambor from comment #7)
> (In reply to kargls from comment #5)
> >
> > So, if I understand, you want an fnspec of ". . w w w w w w w".
> > Can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120958
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120847
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #8)
> Created attachment 61779 [details]
> Reduced testcase
>
> This is roughly the minimum I got.
Even the nint is not needed...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120847
--- Comment #8 from anlauf at gcc dot gnu.org ---
Created attachment 61779
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61779&action=edit
Reduced testcase
This is roughly the minimum I got.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120847
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #4)
> (In reply to Andre Vehreschild from comment #3)
> > Will backport to gcc-15 in about a week.
>
> I am still getting a failure on trun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120812
--- Comment #12 from anlauf at gcc dot gnu.org ---
(In reply to Christophe Peyret from comment #11)
> same on Mac ARM :)
Good. So it is most likely the issue with SAVEd pointer/allocatable
that was recently fixed.
To verify, you can try
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
--- Comment #10 from anlauf at gcc dot gnu.org ---
Regtested fine here.
Submitted: https://gcc.gnu.org/pipermail/fortran/2025-June/062395.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
--- Comment #9 from anlauf at gcc dot gnu.org ---
Fixed by:
diff --git a/gcc/fortran/interface.cc b/gcc/fortran/interface.cc
index cdb838d8336..7899864158c 100644
--- a/gcc/fortran/interface.cc
+++ b/gcc/fortran/interface.cc
@@ -457,7 +457,9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
--- Comment #7 from anlauf at gcc dot gnu.org ---
Created attachment 61738
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61738&action=edit
New testcase
The committed patch unfortunately broke this (reduced) testcase:
pr120784-v2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #7)
> Created attachment 61738 [details]
> New testcase
>
> The committed patch unfortunately broke this (reduced) testcase:
We run into the followi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120812
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to Christophe Peyret from comment #8)
> try this on Mac with Fortran 15.1.0
>
>
> program main
>
> use iso_c_binding
> implicit none
>
> character(le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119106
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Andre Vehreschild from comment #5)
> Harald, are you still on this?
No. As I wrote, I got stuck.
Please take over if you wish!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120743
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120812
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to kargls from comment #5)
> (In reply to kargls from comment #4)
> > (In reply to anlauf from comment #3)
> >
> > troutmask:sgk[215] gfcx --version
> &g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120711
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to Andre Vehreschild from comment #1)
> Confirmed, but this is not coarray dependent. For me it also crashes without
> -fcoarray=single.
Indeed. valgrind reports an invalid rea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120812
--- Comment #1 from anlauf at gcc dot gnu.org ---
Works as expected on Linux.
What happens if you replace C_NEW_LINE by something different,
like c_carriage_return, or c_null_char, and pipe the output
through "cat -v"?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120812
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to kargls from comment #2)
> Harald, there's a bug (at least it fails on FreeBSD).Here's
> a testcase based on the original code. On FreeBSD, I see
>
> %
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120743
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120711
--- Comment #2 from anlauf at gcc dot gnu.org ---
There is another recent PR on using array constructors of derived types
with allocatable character components, quite similar to this one.
Cannot find it now, but very likely related.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120743
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #4)
> (In reply to Jerry DeLisle from comment #3)
> >
> > Here is a smaller reproducer.
> >
> ...
> >
> > Delete the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120788
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 61694
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61694&action=edit
Untested patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120784
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51961
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82036
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||12.4.1, 13.4.1, 14.3.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46299
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
Keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51961
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120656
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51961
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf 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
Target Milestone|--- |15.0
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110076
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |15.0
Known to work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82480
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32630
Bug 32630 depends on bug 38220, which changed state.
Bug 38220 Summary: C_LOC intrinsic non-pure and without explicit interface
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20585
Bug 20585 depends on bug 38220, which changed state.
Bug 38220 Summary: C_LOC intrinsic non-pure and without explicit interface
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29670
Bug 29670 depends on bug 38220, which changed state.
Bug 38220 Summary: C_LOC intrinsic non-pure and without explicit interface
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119994
--- Comment #7 from anlauf at gcc dot gnu.org ---
Created attachment 61582
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61582&action=edit
Exploratory patch
This patch tries to improve upon the determination of whether a symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99838
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99838
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114022
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |15.2
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102599
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |15.2
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120483
--- Comment #5 from anlauf at gcc dot gnu.org ---
Instead of adding the SAVE attribute to the declaration, one can get the
same wrong code with -fno-automatic.
The decl generated by gfc_sym_type() looks suspicious in the case when the
SAVE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114022
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102599
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
--- Comment #12 from anlauf at gcc dot gnu.org ---
Created attachment 61529
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61529&action=edit
Fix for the breakage by r16-914-g787a8dec1acedf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #10)
> Seems like some last-minute cleanup before submission broke something.
> I'll have a look.
It was the last-minute cleanup. Duh!
This fixe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #9)
> (In reply to anlauf from comment #8)
> > (In reply to Jerry DeLisle from comment #7)
> > > Ruuning tests right now to see if th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #7)
> Ruuning tests right now to see if this has caused some breakage.
Are you also hit by r16-916-g517c9487f8fdc4 which breaks texinfo again?
We had t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to kargls from comment #5)
> (In reply to anlauf from comment #4)
> > (In reply to Jerry DeLisle from comment #3)
> > > My understanding is they are getting built gene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120431
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #3)
> My understanding is they are getting built generated in the build directory
> which is a recent bug someone reported. I dont think it has been
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85750
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|[12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101735
--- Comment #4 from anlauf at gcc dot gnu.org ---
Created attachment 61505
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61505&action=edit
WIP patch
This WIP patch improves the parsing of expressions with inquiry references
of sub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85750
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[12/13/14/15/16 Regression] |[12/13/14 Regression
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=102599
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2025-5-20
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=102891
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120355
--- Comment #1 from anlauf at gcc dot gnu.org ---
Workaround: don't use the result clause in the external function, e.g.
integer function s(x)
implicit none
integer, intent(in) :: x
s = 1 - x
end function s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120355
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120355
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|Type mismatch for passed|[15/16 Regression] Type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #21 from anlauf at gcc dot gnu.org ---
Patch from comment#16 submitted:
https://gcc.gnu.org/pipermail/fortran/2025-May/062180.html
I hope I got the description of the issue right in the changelog.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #20 from anlauf at gcc dot gnu.org ---
Does anybody know why there is the following comment preceding the suspcious
block:
/* Possibly return complex numbers by reference for g77 compatibility.
We don't do this for cal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #18 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #17)
> (In reply to Andrew Pinski from comment #15)
> > (In reply to anlauf from comment #14)
> > > This fixes the reduced te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #16 from anlauf at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #15)
> (In reply to anlauf from comment #14)
> > This fixes the reduced testcase for me, but gfortran.dg/specifics_1.f90
> > still fails h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #14 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #12)
> Good point. Tentative patch which excepts (d)conjg:
>
> diff --git a/gcc/fortran/trans-types.cc b/gcc/fortran/trans-types.cc
> index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
--- Comment #12 from anlauf at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #11)
> I wonder why gfc_return_by_reference is not returning true here because I
> think that would be idea here.
Good point. Tentative patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120099
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120302
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120298
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||j...@bolding-bruggeman.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85750
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119928
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||abensonca at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119812
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85750
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC|anlauf at gmx dot de |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119986
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Thomas Schwinge from comment #8)
> (In reply to GCC Commits from comment #5)
> > commit r16-480-g6ce73ad4370c143a7d1e6a13b1d353db5884213f
>
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120049
--- Comment #26 from anlauf at gcc dot gnu.org ---
Have you tried to move some of the checks *after* the resolution stage?
The checks in check.cc are invoked rather early. Maybe look into
trans-intrinsic.cc (conv_isocbinding_function)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120196
--- Comment #2 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> Here's a testcase that fails under valgrind:
>
> program p
> implicit none
> character(:), allocatable :: a(:), s
> allocate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120196
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |15.2
Assignee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
--- Comment #2 from anlauf at gcc dot gnu.org ---
Created attachment 61373
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61373&action=edit
Patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120179
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120163
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102891
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
1 - 100 of 1842 matches
Mail list logo