https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438
--- Comment #6 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #5)
> (In reply to anlauf from comment #3)
> > The same text existed in F2018, so it is not new: F2018:C7103 and Note 1.
> >
> > Either eve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438
--- Comment #5 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #3)
> The same text existed in F2018, so it is not new: F2018:C7103 and Note 1.
>
> Either every compiler developer team misunderstood that clause, or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438
--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #3)
> The same text existed in F2018, so it is not new: F2018:C7103 and Note 1.
>
> Either every compiler developer team misunderstood that clause, or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> Can you be a little more explicit?
>
> If I extend the program as follows:
>
> type(params) :: p
> p = params( 0.1, 2.0 )
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114438
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Created attachment 57785
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57785&action=edit
Fortran 2023:C7108 violation
Gfortran does not diagnosis F2023:C7108.
C7108 (R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105547
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114188
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=114141
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P4 |P5
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114146
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P5
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114141
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #3 from kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99837
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #3 from kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99837
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
CC
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Created attachment 57556
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57556&action=edit
patch
gfortran reje
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504
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=114023
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #1 from kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114024
--- Comment #3 from kargl at gcc dot gnu.org ---
Created attachment 57482
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57482&action=edit
patch
The attached patch fixes this PR. It includes a new testcase
and passes regression testing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114024
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #2 from kargl
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found with the Fujitsu testsuite.
The complex part%ref is a rank-1 array with dimension=3.
xx should be allocated and assigned [3.45,3.45
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found with the Fujitsu testsuite. The original code led to
an ICE, but the modified version here
: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found with the Fujitsu testsuite. The complex part%ref in
the first if-stmt leads to an ICE. Likely, the nested
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Note sure if this is legal Fortran, but it leads to an ICE.
Reduced testcase from Fujitsu testsuite
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found with the Fujitsu testsuite. Reduced testcase.
Note, if the use of ENTRY is replace with an actual
function, ie., 'function kmr_fixfun() result(zz)" the
code co
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found this issues with the Fujitsu testsuite. The code
is reduced to the minimum required. If I had to guess,
gfc_charlen for source= is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113997
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=113883
kargl at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113883
--- Comment #1 from kargl at gcc dot gnu.org ---
Created attachment 57389
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57389&action=edit
patch to fix bug
This is the patch and testcase. I have successfully bootstrapped
and
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
All,
I stumbled across the following issue with my code. Consider,
! { dg-do compile }
! { dg-options "-Werror -Wall" }
module foo
contains
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
% gmake bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113866
kargl at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2024-02-10
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #2)
> (In reply to kargl from comment #1)
> > Thanks. Reduce test case.
> >
> > subroutine test_adjustl(x)
> > character(*) :: x(10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #1)
> Thanks. Reduce test case.
>
> subroutine test_adjustl(x)
> character(*) :: x(100)
> call bar(adjustl(x))
> end subroutine
Forcing gf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113845
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to David Binderman from comment #2)
> (In reply to kargl from comment #1)
> > (In reply to David Binderman from comment #0)
> > >
> > > This is the second ic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823
kargl at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Status
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113671
kargl at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #15 from kargl at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #14)
> On Sun, Jan 21, 2024 at 09:52:39PM +, anlauf at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
> &g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360
--- Comment #7 from kargl at gcc dot gnu.org ---
Upon some additional thinking, I wonder how useful this will be compared
to the possible volume of warning messages from modern Fortran. Consider
this code:
module foo
integer :: j = 2
type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360
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=113152
kargl at gcc dot gnu.org changed:
What|Removed |Added
Attachment #56949|0 |1
is obsolete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #3 from kargl at gcc dot gnu.org ---
Created attachment 57109
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57109&action=edit
patch
The attached patch has been regtested. There were no regression.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #2 from kargl at gcc dot gnu.org ---
With the patch at the end of this message and this source code,
program foo
integer(8) x
real(8) y, z
x = 1
y = x
z = atan(y,x)
print *, z
end
I get
% gfcx -c a.f90
a.f90:6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #1 from kargl at gcc dot gnu.org ---
Ugh. This seems to be by design.
The error message
Error: Too many arguments in call to ‘atan’ at (1)
is queued by intrinsic.cc(sort_actual) and appears to take
precedence over an error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113413
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Fortran 2023 added ATAND(X) and ATAND(Y,X). The former is supported.
The latter is unsupported. Consider.
program main
real(4) x, y
x = 1.
y = x
print*, atand(y,x), atan2d(y,x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Fortran 2008 added the misguided form ATAN(Y,X) where Y could be missing.
However, if Y is present, then X is required to have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #5 from kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313
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=113305
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=113254
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to mecej4 from comment #2)
> Created attachment 57001 [details]
> Program source that is handled correctly when -fallow-invalid-boz is
> specified
Correctly? It is not the sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113254
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=113223
--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #3)
> Created attachment 56990 [details]
> Suggested patch including affected test cases
>
> Regression tested OK. Three test cases affected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113223
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Found at https://github.com/llvm/llvm-project/issues/76798
Program test_namelist_blank
Integer :: i,j
Character(300) ::s
Namelist
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #9 from kargl at gcc dot gnu.org ---
Current patch is incomplete as it fails to scalarize.
It seems I need to remember how to register the new
intrinsic subprograms in trans-intrinsics.cc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113165
--- Comment #2 from kargl at gcc dot gnu.org ---
With the attached example code and the patch at the end of this
message, gfortran can be changes to identify both lines of code.
Fixing the run-on errors when -fimplicit-none is used is left as
an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113165
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P5
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #8 from kargl at gcc dot gnu.org ---
Created attachment 56956
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56956&action=edit
git diff cannot find trigpi.c (updated file)
The new file tries to deal with a system with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #7 from kargl at gcc dot gnu.org ---
Created attachment 56955
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56955&action=edit
test program for inverse functions
The attach program tests the inverse functions, e.g.,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #6 from kargl at gcc dot gnu.org ---
In reflecting on the possibility of an OS lacking support for
REAL(10) but having a REAL(16), the mapping of types into
C are likely REAL(4) <--> float, REAL(8) <--> double,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #4 from kargl at gcc dot gnu.org ---
Created attachment 56953
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56953&action=edit
test program
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #3 from kargl at gcc dot gnu.org ---
Created attachment 56952
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56952&action=edit
file that git cannot find
Put in libgfortran/intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #2 from kargl at gcc dot gnu.org ---
Created attachment 56951
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56951&action=edit
file that git cannot find
Put file in libgfortran/intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #1 from kargl at gcc dot gnu.org ---
Created attachment 56950
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56950&action=edit
new file that git cannot diff
Put file in libgfortran/intrinsics.
: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Created attachment 56949
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56949&action=edit
patch with implementation
The attach patch implements the hal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113128
kargl at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-12-24
Known to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
--- Comment #9 from kargl at gcc dot gnu.org ---
I have updated the diff. I don't know have ChangeLog works under git. Here's
what I have written.
* gcc/fortran/gfortran.texi: Remove the "Extended math intrinsics" node.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
kargl at gcc dot gnu.org changed:
What|Removed |Added
Attachment #56810|0 |1
is obsolete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112873
--- Comment #1 from kargl at gcc dot gnu.org ---
Possible ChangeLog (although I don't know the git world requirements).
* intrinsic.cc(add_functions): Update the standard that the various
degree trigonometric functions have been describ
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
Created attachment 56810
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56810&action=edit
* intrinsic.cc(add_functions): Update the standard that the various degree
trigon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
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=30409
--- Comment #12 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #11)
> (In reply to kargl from comment #10)
> > (In reply to anlauf from comment #8)
>
> > which is equivalent to
> >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30409
--- Comment #10 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #8)
> The suggested optimization needs to take into account that the evaluation
> of the temporary expression might trap, or that allocatable variables are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30409
--- Comment #7 from kargl at gcc dot gnu.org ---
The attached testcase use xmin and xmax uninitialized.
After setting xmin = 0 and xmax = 1 and adding z(1) to
the print statements to prevent the inner loop from
being optimized away, I see the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111880
kargl at gcc dot gnu.org changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111851
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=111853
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=111218
--- Comment #7 from kargl at gcc dot gnu.org ---
An alternative patch that allows the original code to compile is
diff --git a/gcc/fortran/symbol.cc b/gcc/fortran/symbol.cc
index a6078bc608a..34eb3a65e8f 100644
--- a/gcc/fortran/symbol.cc
+++ b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #6 from kargl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218
--- Comment #5 from kargl at gcc dot gnu.org ---
Interesting bug. If one puts a break point ...
0x75917d gfc_format_decoder
/home/toon/compilers/gcc/gcc/fortran/error.cc:1078
0x2153e1f pp_format(pretty_printer*, text_info
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107716
--- Comment #4 from kargl at gcc dot gnu.org ---
What the heck does "RESOLVED MOVED"?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111341
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=99711
kargl at gcc dot gnu.org changed:
What|Removed |Added
Known to work||12.2.0, 14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111218
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=109684
--- Comment #14 from kargl at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #13)
> (In reply to Steve Kargl from comment #12)
> > On Mon, Aug 07, 2023 at 10:04:54PM +0000, kargl at gcc dot gnu.org wrote:
> > >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684
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=88286
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=110825
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Priority|P3
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
The was pointed out in Fortran Discourse,
https://fortran-lang.discourse.group/t/strange-behaviour-when-using-type-and-character-in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326
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=110725
kargl at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||14.0
Known to work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725
kargl at gcc dot gnu.org changed:
What|Removed |Added
Summary|[13/14 Regression] internal |[13/14 Regression,openmp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
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=110629
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
1 - 100 of 1174 matches
Mail list logo
