GCC Help
[Prev Page][Next Page]
- 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
- 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
- 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>
- using wrap to mock internal shared library functions
- From: Thanos Makatos <thanos.makatos@xxxxxxxxxxx>
- GCC4.1.2 using “-fPIE -Wl,-pie”
- From: dno gcc <dno.gcc@xxxxxxxxx>
- Re: Hello, I would like to know how to download gcc 9.2 in windows from here. https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ Thanks.
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: Hello, I would like to know how to download gcc 9.2 in windows from here. https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ Thanks.
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: Hello, I would like to know how to download gcc 9.2 in windows from here. https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ Thanks.
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Hello, I would like to know how to download gcc 9.2 in windows from here. https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/ Thanks.
- From: Aditya Guharoy <pslv.adityaguharoy@xxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Error
- From: pen1979871192 <pen1979871192@xxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: Non-optimal code generated for H8
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Possible __VA_OPT__ bug
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Possible __VA_OPT__ bug
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: Non-optimal code generated for H8
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Re: Automatically pass an assembler option when a specific GCC option is used.
- From: Peter Bergner <bergner@xxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Automatically pass an assembler option when a specific GCC option is used.
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Non-optimal code generated for H8
- From: Jeff Law <law@xxxxxxxxxx>
- Non-optimal code generated for H8
- From: Mikael Tillenius <mti-1@xxxxxxxxxxxxx>
- Re: Issue with passing NULL as argument in 4.8.5
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Issue with passing NULL as argument in 4.8.5
- From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Issue with __sync_synchronize() or asm volatile("": : :"memory")
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Issue with __sync_synchronize() or asm volatile("": : :"memory")
- From: William Tambe <tambewilliam@xxxxxxxxx>
- [OpenMP] [libgomp] Limit the number of threads spawned around
- From: Quaquaraquà <nuquaquaraqua@xxxxxxxxx>
- Re: mcpu/mtune=native is wrong on Tinker Board?
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- mcpu/mtune=native is wrong on Tinker Board?
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
- 回复: A common bug about gcc
- From: Wilson John <bsauce0@xxxxxxxxxxx>
- Re: A common bug about gcc
- From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
- Re: A common bug about gcc
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- A common bug about gcc
- From: Wilson John <bsauce0@xxxxxxxxxxx>
- Re: Linker doesn't replace weak functions in assembly with global function in C when LTO is turned on
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: Is it safe to assume that ggc_cleared_alloc() return memory that has been zeroed ?
- From: Jeff Law <law@xxxxxxxxxx>
- Is it safe to assume that ggc_cleared_alloc() return memory that has been zeroed ?
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Propagating addresses from linker to the runtie
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Propagating addresses from linker to the runtie (was: Re: Crash when cross compiling for ARM with GCC-8-2-0 and) -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Linker doesn't replace weak functions in assembly with global function in C when LTO is turned on
- From: 謝憲譁 <r901042004@xxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- how to change multilib directory
- From: "v-jeahua@xxxxxxxxxxxxx" <rcasio@xxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Matthias Pfaller <leo@xxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Compile of gcc 9.2.0 fails
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Compile of gcc 9.2.0 fails
- From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Compile of gcc 9.2.0 fails
- From: Michael LeVine <mlevine@xxxxxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Matthias Pfaller <leo@xxxxxxxx>
- Crash when cross compiling for ARM with GCC-8-2-0 and -ftree-loop-distribute-patterns
- From: Josef Wolf <jw@xxxxxxxxxxxxx>
- Re: Inhibit saving callee-saved registers for noreturn+nothrow functions
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Inhibit saving callee-saved registers for noreturn+nothrow functions
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Inhibit saving callee-saved registers for noreturn+nothrow functions
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Inhibit saving callee-saved registers for noreturn+nothrow functions
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: GNU C for Windows and blind user!
- From: Pierre Gaumond <pierregaumond1946@xxxxxxxxx>
- Re: Has to install gcc-3.4.6 under Centos 7
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Has to install gcc-3.4.6 under Centos 7
- From: "Patel, Kiran D. (GSFC-699.0)[GLOBAL SCIENCE & TECHNOLOGY INC] via gcc-help" <gcc-help@xxxxxxxxxxx>
- libasan: possible false positive?
- From: Christian Schneider <cschneider@xxxxxxxxxxxxx>
- Re: gcc bug? constinit does not require constexpr ctor
- From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
- Re: Save and restore all used registers before and after a system-call assembly instruction.
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Save and restore all used registers before and after a system-call assembly instruction.
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Ada and signal handling
- From: Didier Kryn <kryn@xxxxxxxx>
- gcc bug? constinit does not require constexpr ctor
- From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
- Re: g++ and suppressing threadsafe-statics
- From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
- RE: Ada and signal handling
- From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
- Re: g++ and suppressing threadsafe-statics
- From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
- Re: g++ and suppressing threadsafe-statics
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Ada and signal handling
- From: Didier Kryn <kryn@xxxxxxxx>
- g++ and suppressing threadsafe-statics
- From: Klaus Doldinger <klaus.doldinger64@xxxxxxxxx>
- Ada and signal handling
- From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
- Re: Gcc 9.2.01 on OSX 10.14.4
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Gcc 9.2.01 on OSX 10.14.4
- From: "Harrison, Nicholas M" <nicholas.harrison@xxxxxxxxxxxxxx>
- storageclassof()
- From: phi gcc <phi.gcc@xxxxxxxxx>
- Re: gcc-10 Bug report
- From: Thomas Koenig <tkoenig@xxxxxxxxxxxxx>
- Re: gcc-10 Bug report
- From: Toon Moene <toon@xxxxxxxxx>
- Re: Test for GNU/XSI version of strerror_r
- From: Stefan Ring <stefanrin@xxxxxxxxx>
- Test for GNU/XSI version of strerror_r
- From: Ian Pilcher <arequipeno@xxxxxxxxx>
- Re: gcc-10 Bug report
- From: Jeff Law <law@xxxxxxxxxx>
- Re: gcc-10 Bug report
- From: Thomas Koenig <tkoenig@xxxxxxxxxxxxx>
- gcc-10 Bug report
- From: Selçuk Han AYDIN <shaydin@xxxxxxxxxx>
- Re: how to makeinfo the standalone texinfo source tarballs?
- From: David Liu <xdavidliu@xxxxxxxxx>
- g++, ld: Warning: size of symbol '_' changed (g++3.4)
- From: LMH <lmh_users-groups@xxxxxxxxxxx>
- Re: how to makeinfo the standalone texinfo source tarballs?
- From: Stefan Ring <stefanrin@xxxxxxxxx>
- how to makeinfo the standalone texinfo source tarballs?
- From: David Liu <xdavidliu@xxxxxxxxx>
- Re: Fwd: Eorror compiling GCC-4.8.0 for Solaris 2.9 and 2.10
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: Fwd: Eorror compiling GCC-4.8.0 for Solaris 2.9 and 2.10
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: problem building cross-gcc with pre-built cross-gcc
- From: stsp <stsp2@xxxxxxxxx>
- Re: Fwd: Eorror compiling GCC-4.8.0 for Solaris 2.9 and 2.10
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: AW: make static method find_reloads_address_1(...) extern accessible
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Fwd: Eorror compiling GCC-4.8.0 for Solaris 2.9 and 2.10
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Fwd: Eorror compiling GCC-4.8.0 for Solaris 2.9 and 2.10
- From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- problem building cross-gcc with pre-built cross-gcc
- From: stsp <stsp2@xxxxxxxxx>
- Regarding GCOV
- From: Aditya h <haditya9949@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: "rolf perau via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- AW: make static method find_reloads_address_1(...) extern accessible
- Re: make static method find_reloads_address_1(...) extern accessible
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: "rolf perau via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: make static method find_reloads_address_1(...) extern accessible
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: "rolf perau via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- make static method find_reloads_address_1(...) extern accessible
- Re: Using C++20 __VA_OPT__ in a macro gives an error
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Support for __VA_OPT__ in gcc
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: gcc on Sparc Solaris 8
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- gcc on Sparc Solaris 8
- From: "rolf perau via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Using C++20 __VA_OPT__ in a macro gives an error
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Support for __VA_OPT__ in gcc
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- RE: Using C on x86-64, why emit .text for global data?
- From: Bob Plantz <rgplantz@xxxxxxxxxxx>
- Re: Using C on x86-64, why emit .text for global data?
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: Logical operator inside fold-expression: strange warning
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Using C on x86-64, why emit .text for global data?
- From: Bob Plantz <rgplantz@xxxxxxxxxxx>
- Re: Help with "unable to generate reloads for" atomic_exchangesi
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Using C++20 __VA_OPT__ in a macro gives an error
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Odd optimizer behavior with FP arithmetic
- From: Konstantin Shegunov <kshegunov@xxxxxxxxx>
- Re: Odd optimizer behavior with FP arithmetic
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: Logical operator inside fold-expression: strange warning
- From: Niklas Gürtler <profclonk@xxxxxxxxx>
- Odd optimizer behavior with FP arithmetic
- From: Konstantin Shegunov <kshegunov@xxxxxxxxx>
- Logical operator inside fold-expression: strange warning
- From: "Student FourK via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Stefan Ring <stefanrin@xxxxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- AW: Why does gcc not provide CMakeList.txt for compilation?
- Why does gcc not provide CMakeList.txt for compilation?
- From: unlvsur unlvsur <unlvsur@xxxxxxxx>
- RE: about gcc native on Microsoft Windows
- From: Tamar Christina <Tamar.Christina@xxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- AW: Help with "unable to generate reloads for" atomic_exchangesi
- Re: Help with "unable to generate reloads for" atomic_exchangesi
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Help with "unable to generate reloads for" atomic_exchangesi
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: about gcc native on Microsoft Windows
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Help with "unable to generate reloads for" atomic_exchangesi
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Help with "unable to generate reloads for" atomic_exchangesi
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Strange error message from an incorrect typedef
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- RE: GCC 8.3.0, libatomic and text relocations
- From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
- Re: GCC 8.3.0, libatomic and text relocations
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: ERROR DURING INSTALLATION
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- GCC 8.3.0, libatomic and text relocations
- From: "Kacvinsky, Tom" <Tom.Kacvinsky@xxxxxxxxxx>
- ERROR DURING INSTALLATION
- From: Ana <anna.207346@xxxxxxxxx>
- Re: taking OpenCL C as a built-in lang of GCC?
- From: Jason Merrill <jason@xxxxxxxxxx>
- Re: [DSO missing from command line] gcc-c++ error
- From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
- Re: taking OpenCL C as a built-in lang of GCC?
- From: Jeff Law <law@xxxxxxxxxx>
- AW: new ira optimization - adding a loop to ira
- Re: [DSO missing from command line] gcc-c++ error
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: [DSO missing from command line] gcc-c++ error
- From: Vassilena Treneva <treneva@xxxxxxxxx>
- Re: [DSO missing from command line] gcc-c++ error
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- [DSO missing from command line] gcc-c++ error
- From: Vassilena Treneva <treneva@xxxxxxxxx>
- Re: Header search order problem
- From: Josh Scoggins <josh.scoggins@xxxxxxxxxxxx>
- Header search order problem
- From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
- Different output between 9.2 and 8.3: Regression or expected?
- From: "Hong X" <hongx@xxxxxxx>
- _FORTIFY_SOURCE and libtool
- From: Liu Hao <lh_mouse@xxxxxxx>
- AW: new ira optimization - adding a loop to ira
- AW: new ira optimization - adding a loop to ira
- AW: new ira optimization - adding a loop to ira
- Re: new ira optimization - adding a loop to ira
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- new ira optimization - adding a loop to ira
- Re: About machine description for atomic_exchange
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: About machine description for atomic_exchange
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: taking OpenCL C as a built-in lang of GCC?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- taking OpenCL C as a built-in lang of GCC?
- From: "Jianbin Fang" <jianbinfang@xxxxxxxx>
- Re: Role of unspec or unspec_volatile in a machine description pattern
- From: "Ian Lance Taylor via gcc-help" <gcc-help@xxxxxxxxxxx>
- Role of unspec or unspec_volatile in a machine description pattern
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Question about __builtin_strlen and constexpr
- From: "Yan Yichen" <yichen.yan@xxxxxxxxxxx>
- Re: About machine description for atomic_exchange
- From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
- Re: gcc-ver 7.3 support
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- gcc-ver 7.3 support
- From: "Krishnakant Mehta via gcc-help" <gcc-help@xxxxxxxxxxx>
- About machine description for atomic_exchange
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Machine description for volatile memory access
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Machine description for volatile memory access
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Machine description for volatile memory access
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Machine description for volatile memory access
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Ayrat Gaskarov <777grand@xxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Ayrat Gaskarov <777grand@xxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Andrew Haley <aph@xxxxxxxxxx>
- Local variables reordering and 'asm volatile("" ::: "memory");'
- From: Ayrat Gaskarov <777grand@xxxxxxxxx>
- Re: Trouble with --with-sysroot
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
- Re: Trouble with --with-sysroot
- From: Alex <wailingoctopus@xxxxxxxxx>
- Re: Trouble with --with-sysroot
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: Trouble with --with-sysroot
- From: Alex <wailingoctopus@xxxxxxxxx>
- gcc openmp target nvptx: LTO_tags out of range
- From: Jeffrey Kelling <j.kelling@xxxxxxx>
- Re: Trouble with --with-sysroot
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Trouble with --with-sysroot
- From: Alex <wailingoctopus@xxxxxxxxx>
- Re: libssp_nonshared license problem
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: libssp_nonshared license problem
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- libssp_nonshared license problem
- From: yao zhuang <secularbird.eagle@xxxxxxxxx>
- while building GCC linking libstdc++.so with the correct libgcc_s.so.1
- From: Marco Maggi <mrc.mgg@xxxxxxxxx>
- gcc-helpnetwork system
- From: "Sales.35@xxxxxxxxxxxxxx" <Sales.35@xxxxxxxxxxxxxx>
- Re: Use and misuse of __builtin_expect
- From: Denis Efremov <efremov@xxxxxxxxx>
- Re: bool to size_t warning
- From: Jonny Grant <jg@xxxxxxxx>
- Re: bool to size_t warning
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: bool to size_t warning
- From: Jonny Grant <jg@xxxxxxxx>
- Re: bool to size_t warning
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: bool to size_t warning
- From: Jonny Grant <jg@xxxxxxxx>
- Re: argument "named" of TARGET_FUNCTION_ARG
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- Re: bool to size_t warning
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- argument "named" of TARGET_FUNCTION_ARG
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Promo Products For Events
- From: <amy@xxxxxxxxxxxxxx>
- Use and misuse of __builtin_expect
- From: Denis Efremov <efremov@xxxxxxxxx>
- Re: How to debug null-pointer function call within __do_global_dtors_aux()
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- Re: How to debug null-pointer function call within __do_global_dtors_aux()
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: How to debug null-pointer function call within __do_global_dtors_aux()
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- How to debug null-pointer function call within __do_global_dtors_aux()
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: does gcc support _mm256_loadu2_m128i()
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- How to insert a new function in plugin?
- From: 时彦辉 <shiyanhui@xxxxxxxx>
- does gcc support _mm256_loadu2_m128i()
- From: qw <applemax82@xxxxxxx>
- Re: cross-compiling gcc-8.3.0 fail; Makefile:528: recipe for target 'elf.lo' failed
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- cross-compiling gcc-8.3.0 fail; Makefile:528: recipe for target 'elf.lo' failed
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: unrecognizable insn
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: what does help?
- From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
- Re: what does help?
- From: Ali MURAT <alimupas2@xxxxxxxxx>
- what does help?
- From: Ali MURAT <alimupas2@xxxxxxxxx>
- Re: NULL_RTX etc
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- NULL_RTX etc
- From: graham stott <graham.stott77@xxxxxxxxx>
- Re: unrecognizable insn
- From: William Tambe <tambewilliam@xxxxxxxxx>
- unrecognizable insn
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Are pretend arguments included in the outgoing argument region ?
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Are pretend arguments included in the outgoing argument region ?
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Are pretend arguments included in the outgoing argument region ?
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Are pretend arguments included in the outgoing argument region ?
- From: Jeff Law <law@xxxxxxxxxx>
- Are pretend arguments included in the outgoing argument region ?
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Does the sign of the value returned by INITIAL_ELIMINATION_OFFSET matters ?
- From: Jeff Law <law@xxxxxxxxxx>
- Does the sign of the value returned by INITIAL_ELIMINATION_OFFSET matters ?
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Akshat Garg <xkspr7@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Akshat Garg <xkspr7@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Akshat Garg <xkspr7@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: dg-error having two regexes
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- dg-error having two regexes
- From: Akshat Garg <xkspr7@xxxxxxxxx>
- Re: it is problem?
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- it is problem?
- From: Ali MURAT <alimupas2@xxxxxxxxx>
- Re: bool to size_t warning
- From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
- Re: bool to size_t warning
- From: Jonny Grant <jg@xxxxxxxx>
- Re: bool to size_t warning
- From: Maksim Fomin <maxim@xxxxxxxxx>
- bool to size_t warning
- From: Jonny Grant <jg@xxxxxxxx>
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- Re: stage1 bootstrap 9.1.0 on RHEL produces 64-bit ELF output in gcc/32/crtbeginS.o
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- stage1 bootstrap 9.1.0 on RHEL produces 64-bit ELF output in gcc/32/crtbeginS.o
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: gcc -Wconversion
- From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: gcc -Wconversion
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- gcc -Wconversion
- From: David Aldrich <david.aldrich.ntml@xxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- Re: Manuals for GCC v8.2.0.3
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Manuals for GCC v8.2.0.3
- From: "Kewen.Lin" <linkw@xxxxxxxxxxxxx>
- Manuals for GCC v8.2.0.3
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: how to configure GCC to have caller save registers instead of callee prologue
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- From: Jim Wilson <jimw@xxxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- Re: Question about AArch64 mcmodel=large
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- how to configure GCC to have caller save registers instead of callee prologue
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Re: Troubles building cross-compiler; target 64-bit RISC-V
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Troubles building cross-compiler; target 64-bit RISC-V
- Question about AArch64 mcmodel=large
- From: "Bu Le" <cityubule@xxxxxx>
- Re: Understanding target specifications for memory barriers
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Can I thrust in GCC doing the right thing when casting to a wider type in C?
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Can I thrust in GCC doing the right thing when casting to a wider type in C?
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Can I thrust in GCC doing the right thing when casting to a wider type in C?
- From: Aaron <aaron_ng@xxxxxxxx>
- Standard expand_prologue() and expand_epilogue() implementations
- From: William Tambe <tambewilliam@xxxxxxxxx>
- Understanding target specifications for memory barriers
- From: Akshat Garg <xkspr7@xxxxxxxxx>
- C++: __asm on static method
- From: Georg-Johann Lay <avr@xxxxxxxx>
- Re: Dejagnu: Catch cc1 regexp errors without associated line number
- From: Richard Sandiford <richard.sandiford@xxxxxxx>
- Dejagnu: Catch cc1 regexp errors without associated line number
- From: Maxim Blinov <maxim.blinov@xxxxxxxxxxxx>
- Re: flow control statement
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- Re: Should a class-scope typedef effect ODR?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: flow control statement
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- Re: Should a class-scope typedef effect ODR?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Should a class-scope typedef effect ODR?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: flow control statement
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- Fwd: flow control statement
- From: Ali MURAT <alimupas2@xxxxxxxxx>
[Index of Archives]
[Fedora Development]
[Security]
[Netfilter]
[Bugtraq]