public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
@ 2023-03-22 13:09 laf163 at hotmail dot com
  2023-03-22 13:28 ` [Bug c++/109250] " redi at gcc dot gnu.org
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: laf163 at hotmail dot com @ 2023-03-22 13:09 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

            Bug ID: 109250
           Summary: Invalid configuration `loongarch64-linux-gnu': machine
                    `loongarch64-unknown' not recognized
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: laf163 at hotmail dot com
  Target Milestone: ---

I am trying to compile GCC v12.2.0 on the Kylin Desktop Operating System V10
(SP1), with a loongson-3A5000 CPU. The current GCC version is v8.3, but I am
encountering errors during the compilation process. Can you please help me take
a look?

Kernel: linux 5.4.18-28.23-bj-generic

$lscpu
Architecture:        loongarch64
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
NUMA node(s):        1
CPU family:          Loongson-64bit
Model name:          Loongson-3A5000
BogoMIPS:            5000.00
L1d cache:           256 KiB
L1i cache:           256 KiB
L2 cache:            1 MiB
L3 cache:            16 MiB
NUMA node0 CPU(s):   0-3
Flags:               cpucfg lam ual fpu lsx lasx complex crypto lvz

$gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/loongarch64-linux-gnu/8/lto-wrapper
Target: loongarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Loongnix
8.3.0-6.lnd.vec.24' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,c++,fortran --prefix=/usr --with-gcc-major-version-only
--program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
--disable-libsanitizer --disable-libquadmath --disable-libquadmath-support
--enable-plugin --with-system-zlib --enable-multiarch --disable-werror
--with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array
--enable-gnu-indirect-function --disable-host-shared --disable-emultls
--with-fix-loongson3-llsc --enable-checking=release
--build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
--target=loongarch64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Loongnix 8.3.0-6.lnd.vec.24) 

$./configure --enable-languages=c,c++ --prefix=/opt/gcc-12.2.0
--program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
--enable-linker-build-id --without-included-gettext --enable-threads=posix
--enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-libitm --disable-libsanitizer
--disable-libquadmath --disable-libquadmath-support --enable-plugin
--with-system-zlib --enable-multiarch --disable-werror --with-arch=loongarch64
--with-abi=lp64 --enable-tls --enable-initfini-array
--enable-gnu-indirect-function --disable-host-shared --disable-emultls
--with-fix-loongson3-llsc --enable-checking=release
--build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
--target=loongarch64-linux-gnu

$make
......
Configuring stage 1 in host-loongarch64-linux-gnu/gmp
configure: loading cache ./config.cache
checking build system type... Invalid configuration `loongarch64-linux-gnu':
machine `loongarch64-unknown' not recognized
configure: error: /bin/bash ../.././gmp/config.sub loongarch64-linux-gnu failed
......

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
@ 2023-03-22 13:28 ` redi at gcc dot gnu.org
  2023-03-22 13:35 ` laf163 at hotmail dot com
                   ` (7 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: redi at gcc dot gnu.org @ 2023-03-22 13:28 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Liu Aifu from comment #0)
> I am trying to compile GCC v12.2.0 on the Kylin Desktop Operating System V10
> (SP1), with a loongson-3A5000 CPU. The current GCC version is v8.3, but I am
> encountering errors during the compilation process. Can you please help me
> take a look?
> 
> Kernel: linux 5.4.18-28.23-bj-generic
> 
> $lscpu
> Architecture:        loongarch64
> Byte Order:          Little Endian
> CPU(s):              4
> On-line CPU(s) list: 0-3
> Thread(s) per core:  1
> Core(s) per socket:  4
> Socket(s):           1
> NUMA node(s):        1
> CPU family:          Loongson-64bit
> Model name:          Loongson-3A5000
> BogoMIPS:            5000.00
> L1d cache:           256 KiB
> L1i cache:           256 KiB
> L2 cache:            1 MiB
> L3 cache:            16 MiB
> NUMA node0 CPU(s):   0-3
> Flags:               cpucfg lam ual fpu lsx lasx complex crypto lvz
> 
> $gcc -v
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/loongarch64-linux-gnu/8/lto-wrapper
> Target: loongarch64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Loongnix
> 8.3.0-6.lnd.vec.24' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
> --enable-languages=c,c++,fortran --prefix=/usr --with-gcc-major-version-only
> --program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
> --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
> --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
> --disable-libsanitizer --disable-libquadmath --disable-libquadmath-support
> --enable-plugin --with-system-zlib --enable-multiarch --disable-werror
> --with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array
> --enable-gnu-indirect-function --disable-host-shared --disable-emultls
> --with-fix-loongson3-llsc --enable-checking=release
> --build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
> --target=loongarch64-linux-gnu
> Thread model: posix
> gcc version 8.3.0 (Loongnix 8.3.0-6.lnd.vec.24) 
> 
> $./configure --enable-languages=c,c++ --prefix=/opt/gcc-12.2.0

Don't build in the source directory.
https://gcc.gnu.org/wiki/FAQ#configure

> --program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
> --enable-linker-build-id --without-included-gettext --enable-threads=posix
> --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
> --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
> --enable-gnu-unique-object --disable-libitm --disable-libsanitizer
> --disable-libquadmath --disable-libquadmath-support --enable-plugin
> --with-system-zlib --enable-multiarch --disable-werror
> --with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array
> --enable-gnu-indirect-function --disable-host-shared --disable-emultls
> --with-fix-loongson3-llsc --enable-checking=release
> --build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
> --target=loongarch64-linux-gnu

Why are you including all these options, most of which are already implied by
default?

https://gcc.gnu.org/wiki/InstallingGCC

"If your build fails and your configure command has lots of complicated options
you should try removing options and keep it simple. Do not add lots of
configure options you don't understand, they might be the reason your build
fails."

e.g. why do you want the suffix to be -8 when you're building gcc-12?


Anyway, the error is in the gmp sub-directory, so you probably need a more
recent version of gmp to get loongarch support.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
  2023-03-22 13:28 ` [Bug c++/109250] " redi at gcc dot gnu.org
@ 2023-03-22 13:35 ` laf163 at hotmail dot com
  2023-03-22 14:32 ` redi at gcc dot gnu.org
                   ` (6 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: laf163 at hotmail dot com @ 2023-03-22 13:35 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #2 from Liu Aifu <laf163 at hotmail dot com> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Liu Aifu from comment #0)
> > I am trying to compile GCC v12.2.0 on the Kylin Desktop Operating System V10
> > (SP1), with a loongson-3A5000 CPU. The current GCC version is v8.3, but I am
> > encountering errors during the compilation process. Can you please help me
> > take a look?
> > 
> > Kernel: linux 5.4.18-28.23-bj-generic
> > 
> > $lscpu
> > Architecture:        loongarch64
> > Byte Order:          Little Endian
> > CPU(s):              4
> > On-line CPU(s) list: 0-3
> > Thread(s) per core:  1
> > Core(s) per socket:  4
> > Socket(s):           1
> > NUMA node(s):        1
> > CPU family:          Loongson-64bit
> > Model name:          Loongson-3A5000
> > BogoMIPS:            5000.00
> > L1d cache:           256 KiB
> > L1i cache:           256 KiB
> > L2 cache:            1 MiB
> > L3 cache:            16 MiB
> > NUMA node0 CPU(s):   0-3
> > Flags:               cpucfg lam ual fpu lsx lasx complex crypto lvz
> > 
> > $gcc -v
> > Using built-in specs.
> > COLLECT_GCC=gcc
> > COLLECT_LTO_WRAPPER=/usr/lib/gcc/loongarch64-linux-gnu/8/lto-wrapper
> > Target: loongarch64-linux-gnu
> > Configured with: ../src/configure -v --with-pkgversion='Loongnix
> > 8.3.0-6.lnd.vec.24' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
> > --enable-languages=c,c++,fortran --prefix=/usr --with-gcc-major-version-only
> > --program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
> > --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
> > --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu
> > --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> > --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
> > --disable-libsanitizer --disable-libquadmath --disable-libquadmath-support
> > --enable-plugin --with-system-zlib --enable-multiarch --disable-werror
> > --with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array
> > --enable-gnu-indirect-function --disable-host-shared --disable-emultls
> > --with-fix-loongson3-llsc --enable-checking=release
> > --build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
> > --target=loongarch64-linux-gnu
> > Thread model: posix
> > gcc version 8.3.0 (Loongnix 8.3.0-6.lnd.vec.24) 
> > 
> > $./configure --enable-languages=c,c++ --prefix=/opt/gcc-12.2.0
> 
> Don't build in the source directory.
> https://gcc.gnu.org/wiki/FAQ#configure
> 
> > --program-suffix=-8 --program-prefix=loongarch64-linux-gnu- --enable-shared
> > --enable-linker-build-id --without-included-gettext --enable-threads=posix
> > --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
> > --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
> > --enable-gnu-unique-object --disable-libitm --disable-libsanitizer
> > --disable-libquadmath --disable-libquadmath-support --enable-plugin
> > --with-system-zlib --enable-multiarch --disable-werror
> > --with-arch=loongarch64 --with-abi=lp64 --enable-tls --enable-initfini-array
> > --enable-gnu-indirect-function --disable-host-shared --disable-emultls
> > --with-fix-loongson3-llsc --enable-checking=release
> > --build=loongarch64-linux-gnu --host=loongarch64-linux-gnu
> > --target=loongarch64-linux-gnu
> 
> Why are you including all these options, most of which are already implied
> by default?
> 
> https://gcc.gnu.org/wiki/InstallingGCC
> 
> "If your build fails and your configure command has lots of complicated
> options you should try removing options and keep it simple. Do not add lots
> of configure options you don't understand, they might be the reason your
> build fails."
> 
> e.g. why do you want the suffix to be -8 when you're building gcc-12?
> 
> 
> Anyway, the error is in the gmp sub-directory, so you probably need a more
> recent version of gmp to get loongarch support.

The above command line was copied from the output of "gcc -v". I tried shorter
parameters at the beginning, but the same error was reported.

$./configure --prefix=/opt/gcc-12.2.0 --disable-multilib
--enable-language=c,c++ --enable-checking=release

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
  2023-03-22 13:28 ` [Bug c++/109250] " redi at gcc dot gnu.org
  2023-03-22 13:35 ` laf163 at hotmail dot com
@ 2023-03-22 14:32 ` redi at gcc dot gnu.org
  2023-03-22 14:32 ` redi at gcc dot gnu.org
                   ` (5 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: redi at gcc dot gnu.org @ 2023-03-22 14:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Like I said, don't build in the source directory, and try a newer version of
GMP.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (2 preceding siblings ...)
  2023-03-22 14:32 ` redi at gcc dot gnu.org
@ 2023-03-22 14:32 ` redi at gcc dot gnu.org
  2023-03-22 15:18 ` xry111 at gcc dot gnu.org
                   ` (4 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: redi at gcc dot gnu.org @ 2023-03-22 14:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-03-22
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (3 preceding siblings ...)
  2023-03-22 14:32 ` redi at gcc dot gnu.org
@ 2023-03-22 15:18 ` xry111 at gcc dot gnu.org
  2023-03-22 15:32 ` schwab@linux-m68k.org
                   ` (3 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: xry111 at gcc dot gnu.org @ 2023-03-22 15:18 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> Like I said, don't build in the source directory, and try a newer version of
> GMP.

Even the latest GMP release does not supports LoongArch.  This is a GMP issue.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (4 preceding siblings ...)
  2023-03-22 15:18 ` xry111 at gcc dot gnu.org
@ 2023-03-22 15:32 ` schwab@linux-m68k.org
  2023-03-22 15:35 ` xry111 at gcc dot gnu.org
                   ` (2 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: schwab@linux-m68k.org @ 2023-03-22 15:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #5 from Andreas Schwab <schwab@linux-m68k.org> ---
There is support for loongarch in longlong.h (added a year ago
https://gmplib.org/repo/gmp/rev/32dc4af70f95), which may be enough to build it,
if config.sub is updated from upstream.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (5 preceding siblings ...)
  2023-03-22 15:32 ` schwab@linux-m68k.org
@ 2023-03-22 15:35 ` xry111 at gcc dot gnu.org
  2023-03-22 15:36 ` xry111 at gcc dot gnu.org
  2023-07-31 16:28 ` [Bug bootstrap/109250] " xry111 at gcc dot gnu.org
  8 siblings, 0 replies; 10+ messages in thread
From: xry111 at gcc dot gnu.org @ 2023-03-22 15:35 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #6 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #5)
> There is support for loongarch in longlong.h (added a year ago
> https://gmplib.org/repo/gmp/rev/32dc4af70f95), which may be enough to build
> it, if config.sub is updated from upstream.

Yes, a manual configfsf.{guess,sub} update is enough.  All GMP tests passes
(with 6.2.1 and updated config files).

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug c++/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (6 preceding siblings ...)
  2023-03-22 15:35 ` xry111 at gcc dot gnu.org
@ 2023-03-22 15:36 ` xry111 at gcc dot gnu.org
  2023-07-31 16:28 ` [Bug bootstrap/109250] " xry111 at gcc dot gnu.org
  8 siblings, 0 replies; 10+ messages in thread
From: xry111 at gcc dot gnu.org @ 2023-03-22 15:36 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |MOVED

--- Comment #7 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
I'm sending a mail to gmp-bugs.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* [Bug bootstrap/109250] Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized
  2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
                   ` (7 preceding siblings ...)
  2023-03-22 15:36 ` xry111 at gcc dot gnu.org
@ 2023-07-31 16:28 ` xry111 at gcc dot gnu.org
  8 siblings, 0 replies; 10+ messages in thread
From: xry111 at gcc dot gnu.org @ 2023-07-31 16:28 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109250

--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Should be fixed with GMP 6.3.0.

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2023-07-31 16:28 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-22 13:09 [Bug c++/109250] New: Invalid configuration `loongarch64-linux-gnu': machine `loongarch64-unknown' not recognized laf163 at hotmail dot com
2023-03-22 13:28 ` [Bug c++/109250] " redi at gcc dot gnu.org
2023-03-22 13:35 ` laf163 at hotmail dot com
2023-03-22 14:32 ` redi at gcc dot gnu.org
2023-03-22 14:32 ` redi at gcc dot gnu.org
2023-03-22 15:18 ` xry111 at gcc dot gnu.org
2023-03-22 15:32 ` schwab@linux-m68k.org
2023-03-22 15:35 ` xry111 at gcc dot gnu.org
2023-03-22 15:36 ` xry111 at gcc dot gnu.org
2023-07-31 16:28 ` [Bug bootstrap/109250] " xry111 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).