GCC Help

• Thread Index

• Re: Specifying where Binutils is and what it is called
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Additional peephole pass(es)
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 9.2, partial specialization with non-type template parameters: bug or not?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Additional peephole pass(es)
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: GCC 9.2, partial specialization with non-type template parameters: bug or not?
  • From: Bence Kodaj via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Specifying where Binutils is and what it is called
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Specifying where Binutils is and what it is called
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• GCC 9.2, partial specialization with non-type template parameters: bug or not?
  • From: Bence Kodaj via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: prevent zero-extension when using a memory load instruction
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• prevent zero-extension when using a memory load instruction
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: OpenACC parallelization
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: Section pragmas
  • From: Richard Biener via Gcc-help <gcc-help@xxxxxxxxxxx>
• add a new instruction to gcc
  • From: 郑镐东 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Section pragmas
  • From: Yousef via Gcc-help <gcc-help@xxxxxxxxxxx>
• OpenACC parallelization
  • From: Lewis Braley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Documentation for packaging GCC
  • From: squirek <squirek@xxxxxxxxxxx>
• Re: How to customize GCC builtin search paths
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to customize GCC builtin search paths
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: How to configure thread model to be used by a custom GCC port ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to configure thread model to be used by a custom GCC port ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Documentation for packaging GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to configure thread model to be used by a custom GCC port ?
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Documentation for packaging GCC
  • From: squirek <squirek@xxxxxxxxxxx>
• Re: The problem(difference) in the gnu website about C++11 support in a specific version of GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• The problem(difference) in the gnu website about C++11 support in a specific version of GCC
  • From: Qiye Tan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: High memory usage compiling large ‘xxd -i’ output
  • From: relliott--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to customize GCC builtin search paths
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: High memory usage compiling large ‘xxd -i’ output
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: High memory usage compiling large ‘xxd -i’ output
  • From: relliott--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: High memory usage compiling large ‘xxd -i’ output
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• High memory usage compiling large ‘xxd -i’ output
  • From: relliott--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: RITM19968871_GNU compiler collection
  • From: Ian Lance Taylor via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: RITM19968871_GNU compiler collection
  • From: "M, Akarsh \(GE CoreTech & Cyber, consultant\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• RE: Pass compile flags to libitm/ subdirectory (and in general)
  • From: Maxim Blinov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Pass compile flags to libitm/ subdirectory (and in general)
  • From: Maxim Blinov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to customize GCC builtin search paths
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• How to customize GCC builtin search paths
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Default arch on Linux/PowerPC?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Unable to create a dynamic library with openmp offload=nvptx-none object files
  • From: "Coyne, Michael K via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Could not join the list, sourceware.org complaining something irrational.
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Could not join the list, sourceware.org complaining something irrational.
  • From: Randy via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Subscription for gcc releases
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Subscription for gcc releases
  • From: "Aleksandrov, Dmitry V via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Subscription for gcc releases
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Subscription for gcc releases
  • From: "Aleksandrov, Dmitry V via Gcc-help" <gcc-help@xxxxxxxxxxx>
• RITM19968871_GNU compiler collection
  • From: "M, Akarsh \(GE CoreTech & Cyber, consultant\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Default arch on Linux/PowerPC?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Could not join the list, sourceware.org complaining something irrational.
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Default arch on Linux/PowerPC?
  • From: Jeffrey Walton via Gcc-help <gcc-help@xxxxxxxxxxx>
• Could not join the list, sourceware.org complaining something irrational.
  • From: Randy via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 9.3 Standard C++ Library docs permissions
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC 9.3 Standard C++ Library docs permissions
  • From: Githogori Nyangara-Murage <githogori@xxxxxxxxxxxxxxxxx>
• Re: #define STARTFILE_SPEC such that crt0.o is used only when crt1.o does not exist
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• RE: problem with opening files
  • From: ALAN P VONDEROHE via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problem with opening files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• problem with opening files
  • From: ALAN P VONDEROHE via Gcc-help <gcc-help@xxxxxxxxxxx>
• #define STARTFILE_SPEC such that crt0.o is used only when crt1.o does not exist
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC modules branch CMI mapping
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC modules branch CMI mapping
  • From: Lapo Falcone via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC modules branch CMI mapping
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC modules branch CMI mapping
  • From: Lapo Falcone via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: intrinsic
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• intrinsic
  • From: Gabriele Capannini via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem with blx (immediate) on ARM M-class processor
  • From: Michael Edie via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC generating symbols prefixed with "call_"
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Set of array elements assigned with compound literals are not assigned with gcc-9.2 compiler
  • From: Nagaraju Mekala via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::regexp with GCC 7.3.1 on AIX, Japanese
  • From: Gabriel VLASIU <gabriel@xxxxxxxxxx>
• Re: std::regexp with GCC 7.3.1 on AIX, Japanese
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::regexp with GCC 7.3.1 on AIX, Japanese
  • From: gabriel@xxxxxxxxxx
• Re: Set of array elements assigned with compound literals are not assigned with gcc-9.2 compiler
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Set of array elements assigned with compound literals are not assigned with gcc-9.2 compiler
  • From: Nagaraju Mekala via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC and division by 0 under sanitizers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• GCC and division by 0 under sanitizers
  • From: Jeffrey Walton via Gcc-help <gcc-help@xxxxxxxxxxx>
• Force LTO inlining
  • From: Gabriel Rodríguez Álvarez <gabriel.rodriguez@xxxxxx>
• Re: Building arm-none-eabi Toolchain
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Building arm-none-eabi Toolchain
  • From: "Sid Spry" <sid@xxxxxxx>
• Re: Can't change password on GCC Bugzilla
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Can't change password on GCC Bugzilla
  • From: Brian Bi via Gcc-help <gcc-help@xxxxxxxxxxx>
• STARTFILE_SPEC value based on whether C or C++
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC generating symbols prefixed with "call_"
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC generating symbols prefixed with "call_"
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Building arm-none-eabi Toolchain
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: OpenACC
  • From: MAHDI LOTFI via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: OpenACC
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• OpenACC
  • From: MAHDI LOTFI via Gcc-help <gcc-help@xxxxxxxxxxx>
• OpenACC
  • From: MAHDI LOTFI via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC generating symbols prefixed with "call_"
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building arm-none-eabi Toolchain
  • From: "Sid Spry" <sid@xxxxxxx>
• Building arm-none-eabi Toolchain
  • From: "Sid Spry" <sid@xxxxxxx>
• gcov misses 'do' line in 'do {...} while(...)' loop?
  • From: Dan Krejsa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GPLv3 runtime exception : libstdc++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GPLv3 runtime exception : libstdc++
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• GPLv3 runtime exception : libstdc++
  • From: emile.fortes@xxxxxxx
• Re: mips alignment restrictions
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• mips alignment restrictions
  • From: Elyashiv Horovitz via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building on Mac with --enable-tls
  • From: Tom N <nospam@xxxxxxxxxxxxxxx>
• Building shared object file for an SH target
  • From: Yann Magnin <yann.magnin@xxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building on Mac with --enable-tls
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building on Mac with --enable-tls
  • From: Tom N <nospam@xxxxxxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Building on Mac with --enable-tls
  • From: Iain Sandoe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building on Mac with --enable-tls
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Building on Mac with --enable-tls
  • From: Tom N <nospam@xxxxxxxxxxxxxxx>
• Re: Message Delay?
  • From: Tom N <nospam@xxxxxxxxxxxxxxx>
• Message Delay?
  • From: - - <nospam@xxxxxxxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: mark_at_yahoo via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Mingw-w64-public] Profile guided optimizations aren't working with absolute paths that start with drive letters
  • From: Liu Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Martin Sebor via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jeffrey Walton via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Hot to test for _FORTIFY_SOURCE with Autoconf
  • From: Jeffrey Walton via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: "Shrader, David Lee via Gcc-help" <gcc-help@xxxxxxxxxxx>
• RE: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: "Shrader, David Lee via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: Jeffrey Walton via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [EXTERNAL] Re: question about knowing when optimization options are used
  • From: "Shrader, David Lee via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: question about knowing when optimization options are used
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• question about knowing when optimization options are used
  • From: "Shrader, David Lee via Gcc-help" <gcc-help@xxxxxxxxxxx>
• gfortran
  • From: Song Hi Lee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: re： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: bule <bule1@xxxxxxxxxx>
• Re: re： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• re: re： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: bule <bule1@xxxxxxxxxx>
• Re: Issues with file I/O fortran 9.2
  • From: "Brian L. Drummond" <brian@xxxxxxxxxxxxxxxxxx>
• Issues with file I/O fortran 9.2
  • From: Francois Clemens via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Vijay Holimath via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Inquiries about GCC binary files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiries about GCC binary files
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Inquiries about GCC binary files
  • From: 김석환 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: kipade <kipade@xxxxxxx>
• Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re:Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: kipade <kipade@xxxxxxx>
• Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re:Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: kipade <kipade@xxxxxxx>
• Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re:Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: kipade <kipade@xxxxxxx>
• Re: how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• how to fix "arm-linux-gnueabihf/lib/libstdc++.so: undefined reference to `clock_gettime@GLIBC_2.17'?
  • From: kipade <kipade@xxxxxxx>
• Re: Will lost bugzilla comments be restored?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Will lost bugzilla comments be restored?
  • From: Stephen Casner <casner@xxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Vijay Holimath <vijay.holimath@xxxxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Mis-aligned debugging symbols
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• RE: Initializing a vector to zero leads to less efficient assemblies than manually assigning a vector to zero?
  • From: "Hong X" <hongx@xxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Vijay Holimath <vijay.holimath@xxxxxxxxx>
• Re: RISC-V G++ and Gfortran Help
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RISC-V G++ and Gfortran Help
  • From: Vijay Holimath <vijay.holimath@xxxxxxxxx>
• Re: re： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Fwd: Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Chris Hall <gcc@xxxxxxx>
• Re: Initializing a vector to zero leads to less efficient assemblies than manually assigning a vector to zero?
  • From: Hongtao Liu <crazylht@xxxxxxxxx>
• re： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: bule <bule1@xxxxxxxxxx>
• Re: Mis-aligned debugging symbols
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Wish to be allowed to send emails to GCC.GNU.org
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Wish to be allowed to send emails to GCC.GNU.org
  • From: Aarya Arun <aarya.arun4@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Mis-aligned debugging symbols
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Chris Hall <gcc@xxxxxxx>
• Fw: problem with gdb debugger applied to gfortran 77 program
  • From: "Cefola, Paul" <paulcefo@xxxxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Initializing a vector to zero leads to less efficient assemblies than manually assigning a vector to zero?
  • From: "Hong X" <hongx@xxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Chris Hall <gcc@xxxxxxx>
• Re: 回复： [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: Re: Install gcc
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: Install gcc
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Re: Install gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: Install gcc
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: Install gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Install gcc
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: Are atomic_fetch_xxx() functions broken for atomic-pointer types ?
  • From: Chris Hall <gcc@xxxxxxx>
• Re: Anonymous read-only Git access
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: Anonymous read-only Git access
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: Re: Anonymous read-only Git access
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: Liu Hao <lh_mouse@xxxxxxx>
• Re: Anonymous read-only Git access
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: Anonymous read-only Git access
  • From: Dan Kegel <dank@xxxxxxxxx>
• Anonymous read-only Git access
  • From: "yilu@xxxxxxxxxxx" <yilu@xxxxxxxxxxx>
• Re: [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Wilco Dijkstra <Wilco.Dijkstra@xxxxxxx>
• Re: C++ expected-to-fail compilation goes through by not detecting mutable-specifier on lambda...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Are atomic_fetch_xxx() functions broken for atomic-pointer types ?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Are atomic_fetch_xxx() functions broken for atomic-pointer types ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Are atomic_fetch_xxx() functions broken for atomic-pointer types ?
  • From: Chris Hall <gcc@xxxxxxx>
• Re: [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: C++ expected-to-fail compilation goes through by not detecting mutable-specifier on lambda...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unable to see list of all ICE reported till date on my GCC Bugszilla account
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Unable to see list of all ICE reported till date on my GCC Bugszilla account
  • From: Shubham Narlawar <gsocshubham@xxxxxxxxx>
• Is there a way to build part of gcc as a dynamic library?
  • From: zerons <sironhide0null@xxxxxxxxx>
• Re: Is there anyway to make the function get parmters from registers not stack during more than 4 parameters on arm port?
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: C++ expected-to-fail compilation goes through by not detecting mutable-specifier on lambda...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• C++ expected-to-fail compilation goes through by not detecting mutable-specifier on lambda...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Cross compiler questions
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• Is there anyway to make the function get parmters from registers not stack during more than 4 parameters on arm port?
  • From: tugouxp <13824125580@xxxxxxx>
• Re: unwind tables for asm blocks
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: failed emails + deficient interface to list archive.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: failed emails + deficient interface to list archive.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: unwind tables for asm blocks
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• failed emails + deficient interface to list archive.
  • From: L A Walsh <gcc@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Chris Hall <chris.hall@xxxxxxx>
• Re: unwind tables for asm blocks
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: Cross compiler questions
  • From: Asha <Ashusdiggi@xxxxxxxxx>
• Re: Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• unwind tables for asm blocks
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: Cross compiler questions
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• Re: [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Wilco Dijkstra <Wilco.Dijkstra@xxxxxxx>
• Should atomic_xxx() functions reject not-_Atomic() arguments ?
  • From: Chris Hall <gcc@xxxxxxx>
• Re: what is the post price of this sites?https://gcc.gnu.org/
  • From: Alfie blake <alfieblake3600@xxxxxxxxx>
• what is the post price of this sites?https://gcc.gnu.org/
  • From: Alfie blake <alfieblake3600@xxxxxxxxx>
• Re: Cross compiler questions
  • From: Asha <Ashusdiggi@xxxxxxxxx>
• Re: Question on gcc RTL and scheduling step.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Question on gcc RTL and scheduling step.
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Question on gcc RTL and scheduling step.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Question on gcc RTL and scheduling step.
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Question on gcc RTL and scheduling step.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Question on gcc RTL and scheduling step.
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: "=?gb18030?b?QnUgTGU=?=" <cityubule@xxxxxx>
• Re: [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: Wilco Dijkstra <Wilco.Dijkstra@xxxxxxx>
• Mysterious hang in __sanitizer::internal_sched_yield
  • From: Dan Kegel <dank@xxxxxxxxx>
• Re: how to add -fPIC support ?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: how to add -fPIC support ?
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: how to add -fPIC support ?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: how to add -fPIC support ?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• how to add -fPIC support ?
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• __builtin_cpu_supports for x86 SHA-1 and SHA-256
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• [AArch64][Spec2017]Question about mlow-precision-div optimization.
  • From: "Bu Le" <cityubule@xxxxxx>
• Re: Difference between --target=i386 and i686
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Getting the enum type of values and the type of a cast via a gcc plugin
  • From: Yassin Kaddar <yassin.kaddar@xxxxxxxx>
• Re: Difference between --target=i386 and i686
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Difference between --target=i386 and i686
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: Difference between --target=i386 and i686
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: Retargetting GCC for new architectures HOWTO
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: __pthread_mutex_lock assertion error with a simple test program
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: __pthread_mutex_lock assertion error with a simple test program
  • From: "Paul Pluzhnikov via gcc-help" <gcc-help@xxxxxxxxxxx>
• __pthread_mutex_lock assertion error with a simple test program
  • From: wanghanlin@xxxxxxxxxxxxxxxx
• Re: specialized templates not working as expected
  • From: andre maute <andre.maute@xxxxxx>
• Re: specialized templates not working as expected
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• specialized templates not working as expected
  • From: andre maute <andre.maute@xxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: constexpr memeber function not constexpt anymore in v10
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -flto=jobserver does not use all CPU cores
  • From: "R. Diez via gcc-help" <gcc-help@xxxxxxxxxxx>
• constexpr memeber function not constexpt anymore in v10
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Marco Sulla <gnu.org@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Difference between --target=i386 and i686
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• AW: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Retargetting GCC for new architectures HOWTO
  • From: S Talha Ergün <ergunst@xxxxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Dan Allen <danallen46@xxxxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Iain Sandoe <idsandoe@xxxxxxxxxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Dan Allen <danallen46@xxxxxxxxx>
• Re: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Marco Sulla <gnu.org@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Iain Sandoe <idsandoe@xxxxxxxxxxxxxx>
• Fwd: [Mingw-w64-public] MingW64 doesn't generate line numbers debugging information for lambdas
  • From: Liu Hao <lh_mouse@xxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Dan Allen <danallen46@xxxxxxxxx>
• GCC Address Sanitizer – identifying what produced which defect log
  • From: Gordon McConnell <Gordon.McConnell@xxxxxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make compiled a lot of programs, but not gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• make compiled a lot of programs, but not gcc
  • From: Marco Sulla <gnu.org@xxxxxxxxxxxxxxxxxxxxxx>
• Building gcc on macOS 10.15 Catalina is stage 1 only
  • From: Dan Allen <danallen46@xxxxxxxxx>
• Re: A way to make GCC assume certain argument flags
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• AW: A way to make GCC assume certain argument flags
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: A way to make GCC assume certain argument flags
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: A way to make GCC assume certain argument flags
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: A way to make GCC assume certain argument flags
  • From: hugo brunie <hbrunie0@xxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• A way to make GCC assume certain argument flags
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: hugo brunie <hbrunie0@xxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Timothy Wrona <tjwrona1992@xxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Timothy Wrona <tjwrona1992@xxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: -flto=jobserver does not use all CPU cores
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Future support of constexpr math functions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -flto=jobserver does not use all CPU cores
  • From: "R. Diez via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How can I ensure genuineness of compiled GCC?
  • From: "mark_r via gcc-help" <gcc-help@xxxxxxxxxxx>
• How can I ensure genuineness of compiled GCC?
  • From: zsugabubus <zsugabubus@national.shitposting.agency>
• Future support of constexpr math functions
  • From: Timothy Wrona <tjwrona1992@xxxxxxxxx>
• Debug info with C macros (-g3) not honoured in LTO builds
  • From: "R. Diez via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: gcc -g1 does not do what the docs say?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• gcc -g1 does not do what the docs say?
  • From: Alexey Neyman <alexey.neyman@xxxxxxxxx>
• Difference between --target=i386 and i686
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: GCC inline assembly question
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: GCC inline assembly question
  • From: "Boie, Andrew P" <andrew.p.boie@xxxxxxxxx>
• Re: GCC inline assembly question
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• GCC inline assembly question
  • From: "Boie, Andrew P" <andrew.p.boie@xxxxxxxxx>
• Re: How to constexpr construct C++ object containing reinterpret_cast pointer?
  • From: "mark_r via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to constexpr construct C++ object containing reinterpret_cast pointer?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to constexpr construct C++ object containing reinterpret_cast pointer?
  • From: "mark_r via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to constexpr construct C++ object containing reinterpret_cast pointer?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to constexpr construct C++ object containing reinterpret_cast pointer?
  • From: "mark_r via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: GCC asm clobbers
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC asm clobbers
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Problem with zero extend from BI to SI
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Problem with zero extend from BI to SI
  • From: Jeff Law <law@xxxxxxxxxx>
• RE: ***UNCHECKED*** Targeting libgcc for a particular ARM
  • From: Gary Partis <Gary@xxxxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Problem with zero extend from BI to SI
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: gcc-nm behavior with -flto
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Liu Hao <lh_mouse@xxxxxxx>
• Re: gcc-nm behavior with -flto
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• gcc-nm behavior with -flto
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question on peephole2 optimizer
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Question on peephole2 optimizer
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Question on peephole2 optimizer
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Question on peephole2 optimizer
  • From: Jeff Law <law@xxxxxxxxxx>
• Question on peephole2 optimizer
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Behavior of fixincludes when using --with-advance-toolchain
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Behavior of fixincludes when using --with-advance-toolchain
  • From: Matheus Castanho <msc@xxxxxxxxxxxxx>
• Re: Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Issue with subregs
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Issue with subregs
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: Feature request for "friendship" of pointers in "C"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: ***UNCHECKED*** Targeting libgcc for a particular ARM
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: AW: Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Feature request for "friendship" of pointers in "C"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: Function attributes and x32, x64
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Function attributes and x32, x64
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: AW: AW: Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: boolean and interger operation declaration in gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: AW: AW: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• AW: AW: AW: Issue with subregs
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: AW: AW: Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• AW: AW: Issue with subregs
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: AW: Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• AW: Issue with subregs
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: GCC 9.2 and OpenMP offloading to GPUs
  • From: dbroemmel <dibr-bugzilla@xxxxxxxxxxxx>
• Re: GCC 9.2 and OpenMP offloading to GPUs
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: GCC 9.2 and OpenMP offloading to GPUs
  • From: dbroemmel <dibr-bugzilla@xxxxxxxxxxxx>
• Re: GCC 9.2 and OpenMP offloading to GPUs
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• boolean and interger operation declaration in gcc
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• GCC 9.2 and OpenMP offloading to GPUs
  • From: dbroemmel <dibr-bugzilla@xxxxxxxxxxxx>
• Re: Issue with subregs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Issue with subregs
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: ***UNCHECKED*** Targeting libgcc for a particular ARM
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• ***UNCHECKED*** Targeting libgcc for a particular ARM
  • From: Gary Partis <Gary@xxxxxxxxxxxx>
• Re: 128-bit data model macros
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: 128-bit data model macros
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• 128-bit data model macros
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to get feedback for a submitted PATCH
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to get feedback for a submitted PATCH
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• RE: [EXT] Fwd: Re: g++ for riscv32 "bare metal"
  • From: Alex Rocha Prado <alex.prado@xxxxxxx>
• Re: g++ for riscv32 "bare metal"
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: g++ for riscv32 "bare metal"
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: g++ for riscv32 "bare metal"
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• g++ for riscv32 "bare metal"
  • From: Alex Rocha Prado <alex.prado@xxxxxxx>
• Re: Question on movsi and movdi
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Question on movsi and movdi
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: -std=C++11 and strict ANSI compliance
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -std=C++11 and strict ANSI compliance
  • From: Anton Shepelev <anton.txt@xxxxxxxxx>
• Re: -std=C++11 and strict ANSI compliance
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -std=C++11 and strict ANSI compliance
  • From: Anton Shepelev <anton.txt@xxxxxxxxx>
• Re: -std=C++11 and strict ANSI compliance
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -std=C++11 and strict ANSI compliance
  • From: Anton Shepelev <anton.txt@xxxxxxxxx>
• Re: Issue with DI and SI mode
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Issue with DI and SI mode
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: riscv32 : -mno-strict-align has no effect
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: riscv32 : -mno-strict-align has no effect
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• ABI compatibility: GCC9 vs GCC10
  • From: Jason Mancini <jayrusman@xxxxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• Re: riscv32 : -mno-strict-align has no effect
  • From: Jim Wilson <jimw@xxxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• RE: [EXT] Re: riscv32 : -mno-strict-align has no effect
  • From: Alex Rocha Prado <alex.prado@xxxxxxx>
• Re: riscv32 : -mno-strict-align has no effect
  • From: Stefan Ring <stefanrin@xxxxxxxxx>
• riscv32 : -mno-strict-align has no effect
  • From: Alex Rocha Prado <alex.prado@xxxxxxx>
• Re: Question on GCC register optimization.
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Question on GCC register optimization.
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: Help required regarding gcc
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• Re: Building v3.4.6: fails to build c-parse.c
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Help required regarding gcc
  • From: "Raamkumar, A." <a.raamkumar@xxxxxxxxxxxxxx>
• Re: Building v3.4.6: fails to build c-parse.c
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: GCC fails to build.
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• Building v3.4.6: fails to build c-parse.c
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: New in gcc compiler develment
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• New in gcc compiler develment
  • From: Henri Cloetens <henri.cloetens@xxxxxxxxxx>
• Re: GCC fails to build.
  • From: DAVID STUMPH <DSTUMPH1144@xxxxxxxxxxxxx>
• RE: Interactions between function inlining and inline assembly
  • From: RECOULES Frederic <Frederic.RECOULES@xxxxxx>
• Re: Interactions between function inlining and inline assembly
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Interactions between function inlining and inline assembly
  • From: RECOULES Frederic <Frederic.RECOULES@xxxxxx>
• Re: Interactions between function inlining and inline assembly
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Interactions between function inlining and inline assembly
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• RE: Interactions between function inlining and inline assembly
  • From: RECOULES Frederic <Frederic.RECOULES@xxxxxx>
• Re: Interactions between function inlining and inline assembly
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Interactions between function inlining and inline assembly
  • From: RECOULES Frederic <Frederic.RECOULES@xxxxxx>
• Re: Exception not caught with gcc-8.2.0
  • From: Prasath P <ijprasath@xxxxxxxxx>
• TARGET_FUNCTION_ARG vs TARGET_MUST_PASS_IN_STACK
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: GCC fails to build.
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• GCC fails to build.
  • From: DAVID STUMPH <DSTUMPH1144@xxxxxxxxxxxxx>
• Re: Intended usage of _GLIBCXX_HAVE_TLS / emutls symbols on OSX
  • From: Iain Sandoe <iain@xxxxxxxxxxxx>
• Using the ACC_DEVICE_TYPE environment variable
  • From: Leonardo Castro de Lima <castrodelimaleonardo@xxxxxxxxx>
• Re: Intended usage of _GLIBCXX_HAVE_TLS / emutls symbols on OSX
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Make GCC initialize global variable using instructions instead of assembly directive such as .long or .quad
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Function returning struct on x86_64 (at least)
  • From: Chris Hall <chris.hall@xxxxxxx>
• Re: Intended usage of _GLIBCXX_HAVE_TLS / emutls symbols on OSX
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: Query: Regarding mtrack-speculation support in gcc latest version
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Query: Regarding mtrack-speculation support in gcc latest version
  • From: Gaurav Kohli <gkohli@xxxxxxxxxxxxxx>
• Re: Make GCC initialize global variables generating instructions in crti.S _init
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: We need to know if you are aware!
  • From: Arman Mallick <lee@xxxxxxxxxxx>
• Re: Make GCC initialize global variables generating instructions in crti.S _init
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Make GCC initialize global variables generating instructions in crti.S _init
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Query: Regarding mtrack-speculation support in gcc latest version
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Function returning struct on x86_64 (at least)
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Function returning struct on x86_64 (at least)
  • From: Chris Hall <gcc@xxxxxxx>
• Re: Make GCC initialize global variables generating instructions in crti.S _init
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Winston Smith <smith_winston_6079@xxxxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: In-tree build of glibc for a cross compiler
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Make GCC initialize global variables generating instructions in crti.S _init
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Make GCC initialize global variables generating instructions in crti.S _init
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• In-tree build of glibc for a cross compiler
  • From: DAVID STUMPH <DSTUMPH1144@xxxxxxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Winston Smith <smith_winston_6079@xxxxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Error during building stage 2 gcc-9.2.0: "configure: error: cannot compute sizeof (long long)
  • From: Winston Smith <Smith_Winston_6079@xxxxxxxxxxx>
• Query: Regarding mtrack-speculation support in gcc latest version
  • From: Gaurav Kohli <gkohli@xxxxxxxxxxxxxx>
• Re: gcc warning about return value truncation
  • From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
• Re: gcc warning about return value truncation
  • From: Liu Hao <lh_mouse@xxxxxxx>
• gcc warning about return value truncation
  • From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• Re: How to use gcc with sanitizers in Void Linux?
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• How to use gcc with sanitizers in Void Linux?
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• Re: What happens to fopen and posix open on a GCC compiler which uses EBCDIC coding for char const[] literals????
  • From: Liu Hao <lh_mouse@xxxxxxx>
• What happens to fopen and posix open on a GCC compiler which uses EBCDIC coding for char const[] literals????
  • From: sotrdg sotrdg <euloanty@xxxxxxxx>
• gnatdll option -I
  • From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
• "skipping incompatible ... when searching for -lgcc"
  • From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Need help with providing a sensible bug report.
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Need help with providing a sensible bug report.
  • From: Colin Close <itchka@xxxxxxxxxxxxxx>
• Re: [Q] ld: Does LTO reorder ro variables in two files?
  • From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
• Re: [Q] ld: Does LTO reorder ro variables in two files?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: [Q] ld: Does LTO reorder ro variables in two files?
  • From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
• Re: [Q] ld: Does LTO reorder ro variables in two files?
  • From: Jeff Law <law@xxxxxxxxxx>
• [Q] ld: Does LTO reorder ro variables in two files?
  • From: Kirill Tkhai <ktkhai@xxxxxxxxxxxxx>
• Intended usage of _GLIBCXX_HAVE_TLS / emutls symbols on OSX
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: How to print pointer to function?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Re: How to print pointer to function?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Manfred <mx2927@xxxxxxxxx>
• Re: How to print pointer to function?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• "Permission denied" error during compilation
  • From: Sebastien LEDIOURIS <sebastien.lediouris.ext@xxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Re: How to print pointer to function?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: FORTRAN preprocessor
  • From: SOUREN ADHIKARY <sourenadhikary@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• RE: [EXT] Re: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: Xing-Hao Chen <ericxh@xxxxxxxxxxx>
• Re: FORTRAN preprocessor
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: [EXT] Re: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• Re: FORTRAN preprocessor
  • From: SOUREN ADHIKARY <sourenadhikary@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• FORTRAN preprocessor
  • From: SOUREN ADHIKARY <sourenadhikary@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: size value of vector_size attribute
  • From: Chris Elrod <elrodc@xxxxxxxxx>
• Re: size value of vector_size attribute
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Stable Version to build
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Stable Version to build
  • From: J Decker <d3ck0r@xxxxxxxxx>
• Re: size value of vector_size attribute
  • From: Chris Elrod <elrodc@xxxxxxxxx>
• documentation bug
  • From: aotto <aotto1968@xxxxxxxxxxx>
• RE: [EXT] Re: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: Xing-Hao Chen <ericxh@xxxxxxxxxxx>
• Re: size value of vector_size attribute
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
• size value of vector_size attribute
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: PR92606: Which target hook to disallow symbol aliasing?
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: PR92606: Which target hook to disallow symbol aliasing?
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• PR92606: Which target hook to disallow symbol aliasing?
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: gcc-9.2.0 and spurious warnings
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: How to print pointer to function?
  • From: Liu Hao <lh_mouse@xxxxxxx>
• Re: How to print pointer to function?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to print pointer to function?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• gcc-9.2.0 and spurious warnings
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• RE: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: Xing-Hao Chen <ericxh@xxxxxxxxxxx>
• Re: std::bit_cast
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Exception not caught with gcc-8.2.0
  • From: Florian Dörsch <gcc@xxxxxxxxxxxx>
• Re: help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Exception not caught with gcc-8.2.0
  • From: Prasath P <ijprasath@xxxxxxxxx>
• help! why a 'so' can't load its dependent 'so' to the pre-defined address
  • From: Xing-Hao Chen <ericxh@xxxxxxxxxxx>
• Only throw-branch coverage markers in gcc 5.4
  • From: Наталья <liretta26@xxxxxxxxx>
• Compilation status
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: GCC cross compiling issue
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC cross compiling issue
  • From: Jin Zhang <jzhang8@xxxxxxxxxxxxxx>
• Re: code that went to process segment now goes to shared segment
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• code that went to process segment now goes to shared segment
  • From: "bmuller@xxxxxxxxxxx" <brunomuller65@xxxxxxxxx>
• RE: Gcc 3.4.3 to Gcc 4.8x
  • From: "Dallman, John" <john.dallman@xxxxxxxxxxx>
• Re: Well formated re: Really want a simple fully free pure x64 operating system i build myself
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Well formated re: Really want a simple fully free pure x64 operating system i build myself
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Well formated re: Really want a simple fully free pure x64 operating system i build myself
  • From: skah@xxxxxxxx
• Re: Gcc 3.4.3 to Gcc 4.8x
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Gcc 3.4.3 to Gcc 4.8x
  • From: Michael Richardson <michael_richardson@xxxxxxxxxxxxxxxxxxxxx>
• Re: Really want a simple fully free pure x64 operating system i build myself
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Really want a simple fully free pure x64 operating system i build myself
  • From: Bryan Baldwin <bryan@xxxxxxxxxxxxxx>
• Re: Really want a simple fully free pure x64 operating system i build myself
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Really want a simple fully free pure x64 operating system i build myself
  • From: skah@xxxxxxxx
• Re: Compiletime check for bit-positions in bit-field
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Compiletime check for bit-positions in bit-field
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Compiletime check for bit-positions in bit-field
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Compiletime check for bit-positions in bit-field
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Compiletime check for bit-positions in bit-field
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: exec: -m: invalid option for GCC 9.2.0 on RHEL6.9
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: exec: -m: invalid option for GCC 9.2.0 on RHEL6.9
  • From: Thomas Doczkal <Thomas.Doczkal@xxxxxxxxxxxxx>
• Re: exec: -m: invalid option for GCC 9.2.0 on RHEL6.9
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• exec: -m: invalid option for GCC 9.2.0 on RHEL6.9
  • From: Thomas Doczkal <Thomas.Doczkal@xxxxxxxxxxxxx>
• Re: std::bit_cast
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• std::bit_cast
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Missed optimization question
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Missed optimization question
  • From: Arvind Sankar <nivedita@xxxxxxxxxxxx>
• null reference function pointer check on __register_frame_info() within frame_dummy() in crtstuff.c
  • From: William Tambe <tambewilliam@xxxxxxxxx>
• Re: Question about attachments on the mailing list
  • From: Christopher Faylor <cgf-use-the-mailinglist-please@xxxxxxx>
• Re: Question about attachments on the mailing list
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Question about attachments on the mailing list
  • From: Erick Ochoa <erick.ochoa@xxxxxxxxxxxxxxxxxxxxx>
• Re: Bit-field with std::byte as member type cannot be initialized: bug or feature?
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Template aliases and attributes
  • From: Martin Reinecke <martin@xxxxxxxxxxxxxxxxxxx>
• Re: Template aliases and attributes
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Template aliases and attributes
  • From: Martin Reinecke <martin@xxxxxxxxxxxxxxxxxxx>
• Re: Bit-field with std::byte as member type cannot be initialized: bug or feature?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Bit-field with std::byte as member type cannot be initialized: bug or feature?
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Questions about LTO, clones and ipa_ref
  • From: erick.ochoa@xxxxxxxxxxxxxxxxxxxxx
• Re: Questions about LTO, clones and ipa_ref
  • From: erick.ochoa@xxxxxxxxxxxxxxxxxxxxx
• Questions about LTO, clones and ipa_ref
  • From: erick.ochoa@xxxxxxxxxxxxxxxxxxxxx
• Re: Trying to understand the -fabi-version=n and -fabi-compat-version=n options
  • From: Jason Merrill <jason@xxxxxxxxxx>
• RE: Trying to understand the -fabi-version=n and -fabi-compat-version=n options
  • From: "Dallman, John" <john.dallman@xxxxxxxxxxx>
• Building gnatdll
  • From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
• Re: Trying to understand the -fabi-version=n and -fabi-compat-version=n options
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Trying to understand the -fabi-version=n and -fabi-compat-version=n options
  • From: "Dallman, John" <john.dallman@xxxxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Jonny Grant <jg@xxxxxxxx>
• Tips for improving OpenMP offload performance on NVIDIA GPU
  • From: Eric Raut <eric.raut@xxxxxxxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Cristiano Di Buduo <cristiano@xxxxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: shift-count-overflow possible issue on 64bit type
  • From: Ponnuvel Palaniyappan <pponnuvel@xxxxxxxxx>
• shift-count-overflow possible issue on 64bit type
  • From: Jonny Grant <jg@xxxxxxxx>
• GCOV is showing 0 percent code coverage
  • From: mandar munagekar <mandarmunagekar@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Richard Sandiford <richard.sandiford@xxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: Israr Sayed <sd.israr@xxxxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: Israr Sayed <sd.israr@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• swapcontext and stack size
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• GCC 7 on ppc64le does not recognize vec_xl_be?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to build gcc with AVX512?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to build gcc with AVX512?
  • From: "Cameron Fletcher (CF)" <circumflex@xxxxxxxxxxx>
• Re: Can g++5.4 link library compiled by gcc4.8 safely?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to build gcc with AVX512?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: How to build gcc with AVX512?
  • From: "Cameron Fletcher (CF)" <circumflex@xxxxxxxxxxx>
• Re: How to build gcc with AVX512?
  • From: Stefan Ring <stefanrin@xxxxxxxxx>
• How to build gcc with AVX512?
  • From: "Cameron Fletcher (CF)" <circumflex@xxxxxxxxxxx>
• Can g++5.4 link library compiled by gcc4.8 safely?
  • From: leo chen <izhiqiu.chen@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Spaceship-operator: why the data-members must be public / triggers ICE
  • From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
• Re: NTH_INSN macro like NEXT_INSN?
  • From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
• Re: NTH_INSN macro like NEXT_INSN?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• NTH_INSN macro like NEXT_INSN?
  • From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: Israr Sayed <sd.israr@xxxxxxxxx>
• Re: Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Fwd: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: sayed israr <sd.israr@xxxxxxxxx>
• Re: Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Is it possible to build Single GCC Executable for armv5, armv6, armv7-{cortex-xx-{A,R,M}},armv8 etc.?
  • From: Israr Sayed <sd.israr@xxxxxxxxx>
• (Template) friend class cannot inherit from private member of class declaring friendship
  • From: "Kilian, Jens" <jens.kilian@xxxxxxxxxxxxx>
• ada frontend stuff lives in subdirectory - why?
  • From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>