public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc
@ 2024-05-01 14:16 hjl.tools at gmail dot com
2024-05-01 14:29 ` [Bug libgcc/114907] " hjl.tools at gmail dot com
` (13 more replies)
0 siblings, 14 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 14:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
Bug ID: 114907
Summary: Missing __extendhfbf2 in libgcc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: crazylht at gmail dot com
Target Milestone: ---
Target: x86-64
From https://sourceware.org/bugzilla/show_bug.cgi?id=31685
$ cat x.cc
#include <stdlib.h>
#include <cstdint>
#include <array>
#include <iostream>
#define SIZE 8
typedef _Float16 T;
//typedef volatile float T;
void fp16tobf16(_Float16 * f) {
__bf16 * b = reinterpret_cast<__bf16*>(f);
for(int i=0; i<SIZE; i++){
T temp = f[i];
b[i] = (__bf16) temp;
}
}
int main(){
std::array<_Float16, SIZE> a{};
std::fill(a.begin(), a.end(), (_Float16) 1.7653432432424324);
fp16tobf16(a.data());
__bf16 * b = reinterpret_cast<__bf16*>(a.data());
std::cout << "\n";
for(int i=0; i<SIZE; i++)
std::cout << ((double) b[i]) << "\n";
return 0;
}
$ g++ -O0 -std=c++23 x.cc
/usr/local/bin/ld: /tmp/ccWrIm0Z.o: in function `fp16tobf16(_Float16*)':
x.cc:(.text+0x4d): undefined reference to `__extendhfbf2'
collect2: error: ld returned 1 exit status
$
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] Missing __extendhfbf2 in libgcc
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
@ 2024-05-01 14:29 ` hjl.tools at gmail dot com
2024-05-01 14:29 ` hjl.tools at gmail dot com
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 14:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
There is __trunchfbf2. Why does GCC generate __extendhfbf2?
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] Missing __extendhfbf2 in libgcc
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
2024-05-01 14:29 ` [Bug libgcc/114907] " hjl.tools at gmail dot com
@ 2024-05-01 14:29 ` hjl.tools at gmail dot com
2024-05-01 14:34 ` hjl.tools at gmail dot com
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 14:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2024-05-01
Status|UNCONFIRMED |NEW
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] Missing __extendhfbf2 in libgcc
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
2024-05-01 14:29 ` [Bug libgcc/114907] " hjl.tools at gmail dot com
2024-05-01 14:29 ` hjl.tools at gmail dot com
@ 2024-05-01 14:34 ` hjl.tools at gmail dot com
2024-05-01 14:49 ` [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2 hjl.tools at gmail dot com
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 14:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
[hjl@gnu-cfl-3 pr114907]$ cat foo.c
__bf16
foo (_Float16 x)
{
return x;
}
[hjl@gnu-cfl-3 pr114907]$ make CC=gcc
gcc -O2 -S foo.c
[hjl@gnu-cfl-3 pr114907]$ cat foo.s
.file "foo.c"
.text
.p2align 4
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
subq $8, %rsp
.cfi_def_cfa_offset 16
call __extendhfbf2
addq $8, %rsp
.cfi_def_cfa_offset 8
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.globl __extendhfbf2
.ident "GCC: (GNU) 14.0.1 20240411 (Red Hat 14.0.1-0)"
.section .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-3 pr114907]$
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (2 preceding siblings ...)
2024-05-01 14:34 ` hjl.tools at gmail dot com
@ 2024-05-01 14:49 ` hjl.tools at gmail dot com
2024-05-01 16:50 ` hjl.tools at gmail dot com
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 14:49 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Missing __extendhfbf2 in |__trunchfbf2 should be
|libgcc |renamed to __extendhfbf2
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
convert_mode_scalar has
if (GET_MODE_PRECISION (from_mode) == GET_MODE_PRECISION (to_mode))
/* Conversion between decimal float and binary float, same size. */
tab = DECIMAL_FLOAT_MODE_P (from_mode) ? trunc_optab : sext_optab;
Since for HF->BF, DECIMAL_FLOAT_MODE_P (from_mode) is false, tab is sext_optab
and __trunchfbf2 should be renamed to __extendhfbf2.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (3 preceding siblings ...)
2024-05-01 14:49 ` [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2 hjl.tools at gmail dot com
@ 2024-05-01 16:50 ` hjl.tools at gmail dot com
2024-05-01 16:58 ` hjl.tools at gmail dot com
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 16:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to H.J. Lu from comment #3)
> convert_mode_scalar has
>
> if (GET_MODE_PRECISION (from_mode) == GET_MODE_PRECISION (to_mode))
> /* Conversion between decimal float and binary float, same size. */
> tab = DECIMAL_FLOAT_MODE_P (from_mode) ? trunc_optab : sext_optab;
>
> Since for HF->BF, DECIMAL_FLOAT_MODE_P (from_mode) is false, tab is
> sext_optab
> and __trunchfbf2 should be renamed to __extendhfbf2.
Since BFmode range is bigger than HFmode, __trunchfbf2 should be used.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (4 preceding siblings ...)
2024-05-01 16:50 ` hjl.tools at gmail dot com
@ 2024-05-01 16:58 ` hjl.tools at gmail dot com
2024-05-01 18:17 ` jakub at gcc dot gnu.org
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: hjl.tools at gmail dot com @ 2024-05-01 16:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to H.J. Lu from comment #4)
> (In reply to H.J. Lu from comment #3)
> > convert_mode_scalar has
> >
> > if (GET_MODE_PRECISION (from_mode) == GET_MODE_PRECISION (to_mode))
> > /* Conversion between decimal float and binary float, same size. */
> > tab = DECIMAL_FLOAT_MODE_P (from_mode) ? trunc_optab : sext_optab;
> >
> > Since for HF->BF, DECIMAL_FLOAT_MODE_P (from_mode) is false, tab is
> > sext_optab
> > and __trunchfbf2 should be renamed to __extendhfbf2.
>
> Since BFmode range is bigger than HFmode, __trunchfbf2 should be used.
Opp, __extendhfbf2 is correct.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (5 preceding siblings ...)
2024-05-01 16:58 ` hjl.tools at gmail dot com
@ 2024-05-01 18:17 ` jakub at gcc dot gnu.org
2024-05-05 8:31 ` liuhongt at gcc dot gnu.org
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-01 18:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Neither of the modes is a subset or superset of the other, so truncate vs.
extend makes no sense. The choice was arbitrary.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (6 preceding siblings ...)
2024-05-01 18:17 ` jakub at gcc dot gnu.org
@ 2024-05-05 8:31 ` liuhongt at gcc dot gnu.org
2024-05-06 14:08 ` [Bug middle-end/114907] " jakub at gcc dot gnu.org
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: liuhongt at gcc dot gnu.org @ 2024-05-05 8:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
Hongtao Liu <liuhongt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |liuhongt at gcc dot gnu.org
--- Comment #7 from Hongtao Liu <liuhongt at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> Neither of the modes is a subset or superset of the other, so truncate vs.
> extend makes no sense. The choice was arbitrary.
It sounds to me we need to define an alias of
strong_alias (__trunchfbf2, __extendhfbf2)
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (7 preceding siblings ...)
2024-05-05 8:31 ` liuhongt at gcc dot gnu.org
@ 2024-05-06 14:08 ` jakub at gcc dot gnu.org
2024-05-07 19:30 ` cvs-commit at gcc dot gnu.org
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-06 14:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 58108
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58108&action=edit
gcc15-pr114907.patch
In retrospect, it has been a mistake to export __trunchfbf2 rather than
__extendhfbf2, but we've done that already.
Given that it is an arbitrary name choice (both are wrong), I think it is
better to change what gcc emits rather than what functions libgcc exports,
because we can backport what gcc emits but can't the libgcc changes.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (8 preceding siblings ...)
2024-05-06 14:08 ` [Bug middle-end/114907] " jakub at gcc dot gnu.org
@ 2024-05-07 19:30 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-05-07 19:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:28ee13db2e9d995bd3728c4ff3a3545e24b39cd2
commit r15-303-g28ee13db2e9d995bd3728c4ff3a3545e24b39cd2
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue May 7 21:30:21 2024 +0200
expansion: Use __trunchfbf2 calls rather than __extendhfbf2 [PR114907]
The HF and BF modes have the same size/precision and neither is
a subset nor superset of the other.
So, using either __extendhfbf2 or __trunchfbf2 is weird.
The expansion apparently emits __extendhfbf2, but on the libgcc side
we apparently have __trunchfbf2 implemented.
I think it is easier to switch to using what is available rather than
adding new entrypoints to libgcc, even alias, because this is backportable.
2024-05-07 Jakub Jelinek <jakub@redhat.com>
PR middle-end/114907
* expr.cc (convert_mode_scalar): Use trunc_optab rather than
sext_optab for HF->BF conversions.
* optabs-libfuncs.cc (gen_trunc_conv_libfunc): Likewise.
* gcc.dg/pr114907.c: New test.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (9 preceding siblings ...)
2024-05-07 19:30 ` cvs-commit at gcc dot gnu.org
@ 2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:33 ` jakub at gcc dot gnu.org
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-05-07 19:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:f43f346f19889a15a171a10c6ae1b1fe0a5bc038
commit r14-10181-gf43f346f19889a15a171a10c6ae1b1fe0a5bc038
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue May 7 21:30:21 2024 +0200
expansion: Use __trunchfbf2 calls rather than __extendhfbf2 [PR114907]
The HF and BF modes have the same size/precision and neither is
a subset nor superset of the other.
So, using either __extendhfbf2 or __trunchfbf2 is weird.
The expansion apparently emits __extendhfbf2, but on the libgcc side
we apparently have __trunchfbf2 implemented.
I think it is easier to switch to using what is available rather than
adding new entrypoints to libgcc, even alias, because this is backportable.
2024-05-07 Jakub Jelinek <jakub@redhat.com>
PR middle-end/114907
* expr.cc (convert_mode_scalar): Use trunc_optab rather than
sext_optab for HF->BF conversions.
* optabs-libfuncs.cc (gen_trunc_conv_libfunc): Likewise.
* gcc.dg/pr114907.c: New test.
(cherry picked from commit 28ee13db2e9d995bd3728c4ff3a3545e24b39cd2)
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (10 preceding siblings ...)
2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
@ 2024-05-07 19:33 ` jakub at gcc dot gnu.org
2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org
2024-05-09 8:18 ` jakub at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-07 19:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed for 14.2+ for now.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (11 preceding siblings ...)
2024-05-07 19:33 ` jakub at gcc dot gnu.org
@ 2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org
2024-05-09 8:18 ` jakub at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-05-09 4:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
--- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:cad27df08915ead8db3c7d512cfcc1866e7ece69
commit r13-8734-gcad27df08915ead8db3c7d512cfcc1866e7ece69
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue May 7 21:30:21 2024 +0200
expansion: Use __trunchfbf2 calls rather than __extendhfbf2 [PR114907]
The HF and BF modes have the same size/precision and neither is
a subset nor superset of the other.
So, using either __extendhfbf2 or __trunchfbf2 is weird.
The expansion apparently emits __extendhfbf2, but on the libgcc side
we apparently have __trunchfbf2 implemented.
I think it is easier to switch to using what is available rather than
adding new entrypoints to libgcc, even alias, because this is backportable.
2024-05-07 Jakub Jelinek <jakub@redhat.com>
PR middle-end/114907
* expr.cc (convert_mode_scalar): Use trunc_optab rather than
sext_optab for HF->BF conversions.
* optabs-libfuncs.cc (gen_trunc_conv_libfunc): Likewise.
* gcc.dg/pr114907.c: New test.
(cherry picked from commit 28ee13db2e9d995bd3728c4ff3a3545e24b39cd2)
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug middle-end/114907] __trunchfbf2 should be renamed to __extendhfbf2
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
` (12 preceding siblings ...)
2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org
@ 2024-05-09 8:18 ` jakub at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-09 8:18 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114907
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed also for 13.3.
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2024-05-09 8:18 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-01 14:16 [Bug libgcc/114907] New: Missing __extendhfbf2 in libgcc hjl.tools at gmail dot com
2024-05-01 14:29 ` [Bug libgcc/114907] " hjl.tools at gmail dot com
2024-05-01 14:29 ` hjl.tools at gmail dot com
2024-05-01 14:34 ` hjl.tools at gmail dot com
2024-05-01 14:49 ` [Bug libgcc/114907] __trunchfbf2 should be renamed to __extendhfbf2 hjl.tools at gmail dot com
2024-05-01 16:50 ` hjl.tools at gmail dot com
2024-05-01 16:58 ` hjl.tools at gmail dot com
2024-05-01 18:17 ` jakub at gcc dot gnu.org
2024-05-05 8:31 ` liuhongt at gcc dot gnu.org
2024-05-06 14:08 ` [Bug middle-end/114907] " jakub at gcc dot gnu.org
2024-05-07 19:30 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:33 ` jakub at gcc dot gnu.org
2024-05-09 4:26 ` cvs-commit at gcc dot gnu.org
2024-05-09 8:18 ` jakub at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).