GCC Help

• Thread Index

• GNU linker script - how to automatically distribute code to multiple non-contiguous sections
  • From: Adrian Muresan <adrianmuresan@xxxxxxxxxxx>
• Re: Query
  • From: "Ekant V. vats" <ekantvv@xxxxxxxxx>
• Re: Build failure - error: bits/c++config.h: No such file or directory
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Build failure - error: bits/c++config.h: No such file or directory
  • From: Robert Jones <robertgbjones@xxxxxxxxx>
• Re: Query
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Query
  • From: "Ekant V. vats" <ekantvv@xxxxxxxxx>
• Why is there now a difference between "{static const char a[]={...}" and "{const char a[]={...}"?
  • From: John Carter <john.carter@xxxxxxxxxxxxx>
• Re: Tests Failing on x86_64_gnu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Tests Failing on x86_64_gnu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Tests Failing on x86_64_gnu
  • From: nick <xerofoify@xxxxxxxxx>
• Re: Tests Failing on x86_64_gnu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Tests Failing on x86_64_gnu
  • From: nick <xerofoify@xxxxxxxxx>
• Re: Bug report
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C to Forth compiler
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re:C to Forth compiler
  • From: zhoupeng <myselfzp1007@xxxxxxx>
• Re: gfortran download link doesn't work for macOS
  • From: Purod Du <djyjin@xxxxxxxxx>
• Bug report
  • From: Egor Kashpersky <ekashpersky@xxxxxxxxx>
• C to Forth compiler
  • From: zhoupeng <myselfzp1007@xxxxxxx>
• Re: gfortran download link doesn't work for macOS
  • From: FX <fxcoudert@xxxxxxxxx>
• Re: gfortran download link doesn't work for macOS
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gfortran download link doesn't work for macOS
  • From: Purod Du <djyjin@xxxxxxxxx>
• Re: Function multiversioning question
  • From: Martin Reinecke <martin@xxxxxxxxxxxxxxxxxxx>
• Re: Function multiversioning question
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Function multiversioning question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Function multiversioning question
  • From: Martin Reinecke <martin@xxxxxxxxxxxxxxxxxxx>
• Re: Function multiversioning question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Function multiversioning question
  • From: Martin Reinecke <martin@xxxxxxxxxxxxxxxxxxx>
• Re: Odd segfault
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Odd segfault
  • From: Marcel Keller <mks.keller@xxxxxxxxx>
• Re: How to check the type of gimple
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• How to check the type of gimple
  • From: "wang tom via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• the mystery of math.h in lib/gcc/%triple-name%/%gcc-version%/include-fixed
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: test results are now locked out for those of us that do gcc tests?
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: test results are now locked out for those of us that do gcc tests?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: test results are now locked out for those of us that do gcc tests?
  • From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
• test results are now locked out for those of us that do gcc tests?
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: lost access to the gcc mailing lists
  • From: Dominique d'Humières <dominiq@xxxxxxxxxxxxxxxxxxxx>
• Re: lost access to the gcc mailing lists
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: lost access to the gcc mailing lists
  • From: Dominique d'Humières <dominiq@xxxxxxxxxxxxxxxxxxxx>
• Re: lost access to the gcc mailing lists
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• lost access to the gcc mailing lists
  • From: Dominique d'Humières <dominiq@xxxxxxxxxxxxxxxxxxxx>
• Re: gcc 7.3 diagnostic message descriptions
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Can someone point me to the correct bug report?
  • From: Luca Bacci <luca.bacci982@xxxxxxxxx>
• Re: Can someone point me to the correct bug report?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Can someone point me to the correct bug report?
  • From: Luca Bacci <luca.bacci982@xxxxxxxxx>
• RE: I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: "Ling, Darcy (NSB - CN/Qingdao)" <darcy.ling@xxxxxxxxxxxxxxx>
• RE: gcc 7.3 diagnostic message descriptions
  • From: "David Gilbert" <dgilbert.france@xxxxxxxxx>
• Re: LTO, shared libraries and extern class templates
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: LTO, shared libraries and extern class templates
  • From: Hadrien Grasland <grasland@xxxxxxxxxxxx>
• Re: "confirm unsubscribe from gcc@xxxxxxxxxxx"
  • From: auto-message@xxxxxxxxxxxxxx
• Re: LTO, shared libraries and extern class templates
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc 7.3 diagnostic message descriptions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• LTO, shared libraries and extern class templates
  • From: Hadrien Grasland <grasland@xxxxxxxxxxxx>
• gcc 7.3 diagnostic message descriptions
  • From: "David Gilbert" <dgilbert.france@xxxxxxxxx>
• Re: GCC for AArch64 never emits CFI in debug_frame
  • From: Alexander Fedotov <alfedotov@xxxxxxxxx>
• RE: I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: "Ling, Darcy (NSB - CN/Qingdao)" <darcy.ling@xxxxxxxxxxxxxxx>
• Re: I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: "Ling, Darcy (NSB - CN/Qingdao)" <darcy.ling@xxxxxxxxxxxxxxx>
• Re: I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: warning: comparison with string literal results in unspecified behavior [-Waddress]
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: warning: comparison with string literal results in unspecified behavior [-Waddress]
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• warning: comparison with string literal results in unspecified behavior [-Waddress]
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• I have installed the GLIBCXX_3.4.21 but it always reports libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed during the RPM install
  • From: "Ling, Darcy (NSB - CN/Qingdao)" <darcy.ling@xxxxxxxxxxxxxxx>
• Re: Getting started with LTO, could use some material on linking/loading
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Getting started with LTO, could use some material on linking/loading
  • From: Hadrien Grasland <grasland@xxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: GPU specific target for OpenMP target offload?
  • From: Jeff Layton <laytonjb@xxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• GPU specific target for OpenMP target offload?
  • From: "Jost, Gabriele (ARC-TNC)[Supersmith] via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: GCC for AArch64 never emits CFI in debug_frame
  • From: Alexander Fedotov <alfedotov@xxxxxxxxx>
• Re: GCC for AArch64 never emits CFI in debug_frame
  • From: Alexander Fedotov <alfedotov@xxxxxxxxx>
• Re: GCC for AArch64 never emits CFI in debug_frame
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: GCC for AArch64 never emits CFI in debug_frame
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• Re: g++ 7.3.0 & 8.2.0: weird std::string_view behavior when using in-line if-else
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Variably modified at file scope due to (void *)0 == (sem_t *)0?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• g++ 7.3.0 & 8.2.0: weird std::string_view behavior when using in-line if-else
  • From: Tmplt <tmplt@dragons.rocks>
• Re: m68k/cpu32 TRAP instruction?
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: m68k/cpu32 TRAP instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Variably modified at file scope due to (void *)0 == (sem_t *)0?
  • From: Liu Hao <lh_mouse@xxxxxxx>
• m68k/cpu32 TRAP instruction?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: Variably modified at file scope due to (void *)0 == (sem_t *)0?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: gcc 8.1 + libc.a
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Variably modified at file scope due to (void *)0 == (sem_t *)0?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Variably modified at file scope due to (void *)0 == (sem_t *)0?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: gcc 8.1 + libc.a
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc 8.1 + libc.a
  • From: "Jost, Gabriele (ARC-TNC)[Supersmith] via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: gcc 8.1 + libc.a
  • From: Dmitry Mikushin <dmitry@xxxxxxxxxxxxx>
• gcc 8.1 + libc.a
  • From: "Jost, Gabriele (ARC-TNC)[Supersmith] via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Effect of using the -rpath linkler option
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Effect of using the -rpath linkler option
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Effect of using the -rpath linkler option
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: struct
  • From: Maximilian <king@xxxxxxxxxxxxxxxxxx>
• Re: struct
  • From: vijay nag <vijunag@xxxxxxxxx>
• Re: struct
  • From: sundaresh <sundaresh@xxxxxxxx>
• Re: Cannot compile on Mac without specifying -isysroot flag
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Cannot compile on Mac without specifying -isysroot flag
  • From: Kyle Martin <martinky24@xxxxxxxxx>
• Cannot compile on Mac without specifying -isysroot flag
  • From: Kyle Martin <martinky24@xxxxxxxxx>
• Re: struct
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Why is ptrdiff_t a volatile?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why is ptrdiff_t a volatile?
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• Re: struct
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Why is ptrdiff_t a volatile?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: struct
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Why is ptrdiff_t a volatile?
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• Re: struct
  • From: sameeran joshi <gsocsameeran@xxxxxxxxx>
• struct
  • From: sundaresh <sundaresh@xxxxxxxx>
• Re: mpc-1.0.3 build errors
  • From: rih5342 <robhickey@xxxxxxx>
• Re: Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: mpc-1.0.3 build errors
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: mpc-1.0.3 build errors
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: What's the recommended linux distro to build gcc?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: mpc-1.0.3 build errors
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Re: mpc-1.0.3 build errors
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: What's the recommended linux distro to build gcc?
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• What's the recommended linux distro to build gcc?
  • From: rih5342 <robhickey@xxxxxxx>
• mpc-1.0.3 build errors
  • From: rih5342 <robhickey@xxxxxxx>
• Re: Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: "C.J." <biocjh@xxxxxxxxx>
• Re: Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: const volatile
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: const volatile
  • From: Rob <robpilling@xxxxxxxxx>
• m68k multilib for -m68020-60
  • From: Miro Kropáček <miro.kropacek@xxxxxxxxx>
• Re: Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• Errors in compiling gcc4.8.5 using gcc8.1.1
  • From: "C.J." <biocjh@xxxxxxxxx>
• Re: problem in compiling gcc6.4.0 using gcc8.1.1
  • From: "C.J." <biocjh@xxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: nosay <chenwen1228@xxxxxxx>
• Re: const volatile
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: const volatile
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: const volatile
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: problem in compiling gcc6.4.0 using gcc8.1.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: problem in compiling gcc6.4.0 using gcc8.1.1
  • From: "C.J." <biocjh@xxxxxxxxx>
• Re: const volatile
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: const volatile
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• const volatile
  • From: Kalamatee <kalamatee@xxxxxxxxx>
• Re: How to use the modified compiler?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to use the modified compiler?
  • From: "wang tom via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: problem in compiling gcc6.4.0 using gcc8.1.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• problem in compiling gcc6.4.0 using gcc8.1.1
  • From: "C.J." <biocjh@xxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc mpfs-0.9 compile error on Open suse leap42.3-64
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: nosay <chenwen1228@xxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Can you give me gcc-2.91.66 please?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Can you give me gcc-2.91.66 please?
  • From: nosay <chenwen1228@xxxxxxx>
• Re: gcc mpfs-0.9 compile error on Open suse leap42.3-64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc mpfs-0.9 compile error on Open suse leap42.3-64
  • From: rih5342 <robhickey@xxxxxxx>
• Re: Unable to build libgcc for target x86_64-w64-mingw32, C preprocessor /lib/cpp fails sanity check
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Unable to build libgcc for target x86_64-w64-mingw32, C preprocessor /lib/cpp fails sanity check
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Unable to build libgcc for target x86_64-w64-mingw32, C preprocessor /lib/cpp fails sanity check
  • From: Juan Pablo Garibotti Arias <jp.garibotti@xxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Pretty print of C / C++ enumerations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Pretty print of C / C++ enumerations
  • From: will wray <wjwray@xxxxxxxxx>
• Pretty print of C / C++ enumerations
  • From: will wray <wjwray@xxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Should rand() return a RAND_MAX value for 32 bit target?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Should rand() return a RAND_MAX value for 32 bit target?
  • From: Neha Gowda <neha.gnu.gcc@xxxxxxxxx>
• Re: MS Variadic extension support for arm64
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Re: Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone.
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone.
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: MS Variadic extension support for arm64
  • From: Martin Storsjö <martin@xxxxxxxxx>
• MS Variadic extension support for arm64
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Vectorization report with call information
  • From: Astor Piaz <appiazzolla@xxxxxxxxx>
• Cache size parameters
  • From: Mohammad Amin <m.t_79@xxxxxxxxxxx>
• Loop Distribution Benefits
  • From: Mohammad Amin <m.t_79@xxxxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: A g++ bug ... or not ?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• A g++ bug ... or not ?
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Position Independent Code for MMU-less MCUs with XIP
  • From: kirkolw kirkolw <kirkolw@xxxxxxxxx>
• Re: Question about a warning message
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Question about a warning message
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Question about a warning message
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question about a warning message
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question about a warning message
  • From: Juan Cabrera <jjcp.91@xxxxxxxxx>
• Re: Question about a warning message
  • From: Ruslan Garipov <ruslanngaripov@xxxxxxxxx>
• Re: Question about a warning message
  • From: Joshua Scoggins <Josh.Scoggins@xxxxxxxxxxxx>
• Question about a warning message
  • From: Juan Cabrera <jjcp.91@xxxxxxxxx>
• Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone.
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: Newb build fails: -Werrors then Bootstrap comparison failure!
  • From: will wray <wjwray@xxxxxxxxx>
• Re: Newb build fails: -Werrors then Bootstrap comparison failure!
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Newb build fails: -Werrors then Bootstrap comparison failure!
  • From: will wray <wjwray@xxxxxxxxx>
• Re: Built compiler cannot create executables during GCC 8.2.0 "make"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Built compiler cannot create executables during GCC 8.2.0 "make"
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: "lejeczek via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Inter library dependency
  • From: Maximilian <king@xxxxxxxxxxxxxxxxxx>
• Inter library dependency
  • From: jim Cruse <crusejim@xxxxxxxxx>
• Re: Question about gcc options '-mapcs-stack-check' and '-mapcs-frame'
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Testsuite question: How to make all execution tests compile-only?
  • From: Eric Gallager <egall@xxxxxxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Is C++11 support considered experimental in GCC 4.8.5 ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Is C++11 support considered experimental in GCC 4.8.5 ?
  • From: Janosch Machowinski <jmachowinski@xxxxxx>
• Re: How are regressions possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How are regressions possible?
  • From: Jeff Donner <jeffrey.donner@xxxxxxxxx>
• Re: COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: "lejeczek via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• COLLECT_LTO_WRAPPER - declaration sys wide - where/how?
  • From: "lejeczek via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Program terminated with signal 6, Aborted
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Program terminated with signal 6, Aborted
  • From: Pankaj Buddhe <pankaj.buddhe@xxxxxxxxx>
• Template Deduction Error Oddity
  • From: Miko Vich <alexmudmiko@xxxxxxxxx>
• gcc compilation error while loading protected data symbols from archive files
  • From: Vyshnav A V <vyshnav.av@xxxxxxxxx>
• RE: help with gcc on opensuse leap 15
  • From: Igor Chudov <Igor_Chudov@xxxxxxxx>
• Re: help with gcc on opensuse leap 15
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• help with gcc on opensuse leap 15
  • From: "KW via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: GCC ABI versions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: GCC ABI versions
  • From: Igor Chudov <Igor_Chudov@xxxxxxxx>
• Re: GCC ABI versions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC ABI versions
  • From: Igor Chudov <Igor_Chudov@xxxxxxxx>
• Re: gcc building is gettting failed because of 32 bit libgcc dependency
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc building is gettting failed because of 32 bit libgcc dependency
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc building is gettting failed because of 32 bit libgcc dependency
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc building is gettting failed because of 32 bit libgcc dependency
  • From: Vyshnav A V <vyshnav.av@xxxxxxxxx>
• Re: build older version
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• build older version
  • From: Andrei Berceanu <andreicberceanu@xxxxxxxxx>
• Re: Change compile target of gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Change compile target of gcc
  • From: "KW via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Question about gcc options '-mapcs-stack-check' and '-mapcs-frame'
  • From: Akhilesh chirlancha <akhileshchirlancha@xxxxxxxxx>
• Re: gcc error stack protection with large files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc error stack protection with large files
  • From: Claudio SRD <tausrd@xxxxxxxxx>
• Re: Program terminated with signal 6, Aborted on class destructor call.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Program terminated with signal 6, Aborted on class destructor call.
  • From: "Liu Hao" <lh_mouse@xxxxxxx>
• Program terminated with signal 6, Aborted on class destructor call.
  • From: Pankaj Buddhe <pankaj.buddhe@xxxxxxxxx>
• Removal of the option -fdump-translation-unit in gcc 8
  • From: Joshua Scoggins <Josh.Scoggins@xxxxxxxxxxxx>
• Re: Relocation Truncated to Fit: R_X86_64_PC32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Relocation Truncated to Fit: R_X86_64_PC32
  • From: R0b0t1 <r030t1@xxxxxxxxx>
• Re: How to regenerate the autotools files
  • From: "R. Diez via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to regenerate the autotools files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to regenerate the autotools files
  • From: "R. Diez via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Solaris 11 Sparc crash in std::call_once
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Solaris 11 Sparc crash in std::call_once
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Solaris 11 Sparc crash in std::call_once
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Solaris 11 Sparc crash in std::call_once
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Solaris 11 Sparc crash in std::call_once
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Using sizeof(unsigned int) is not equal to using a constant in some cases
  • From: A <alexcones@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Useless pointer-to-int-cast warning?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Useless pointer-to-int-cast warning?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• What is the GNU Compiler Collction's current language count?
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: I need help compiling EVERY language on my Mac OS High Sierra based system
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: I need help compiling EVERY language on my Mac OS High Sierra based system
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• I need help compiling EVERY language on my Mac OS High Sierra based system
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: Enable one ISA for my code, and another ISA for GCC code?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Enable one ISA for my code, and another ISA for GCC code?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Enable one ISA for my code, and another ISA for GCC code?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Turning off case checking when linking
  • From: "Neil Frank via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Turning off case checking when linking
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Using clflush
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Nvptx GPU offloading using OpenMP4.5 and GCC 7.3 - internal compiler error
  • From: Flavio Kreiliger <flavio.kreiliger@xxxxxxxxxx>
• Re: Turning off case checking when linking
  • From: "Neil Frank via gcc-help" <gcc-help@xxxxxxxxxxx>
• qcov questions
  • From: daro_ox@xxxxx <daro_ox@xxxxx>
• Re: Turning off case checking when linking
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Turning off case checking when linking
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Relocation Truncated to Fit: R_X86_64_PC32
  • From: R0b0t1 <r030t1@xxxxxxxxx>
• Turning off case checking when linking
  • From: "Neil Frank via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Question about gcc option -mcmodel
  • From: Ramana Radhakrishnan <ramana.radhakrishnan@xxxxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: martin krastev <blu.dark@xxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: GCC 8 released but not successful ?
  • From: Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: YunQiang Su <wzssyqa@xxxxxxxxx>
• Question about gcc option -mcmodel
  • From: "xiebin (F)" <xiebin18@xxxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: martin krastev <blu.dark@xxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: martin krastev <blu.dark@xxxxxxxxx>
• Libasan failed to be build for ARM with -mthumb and -fno-omit-frame-pointer
  • From: Denis Khalikov <d.khalikov@xxxxxxxxxxxxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: YunQiang Su <wzssyqa@xxxxxxxxx>
• Re: Issues building gcc natively on mipsel
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Relocation Truncated to Fit: R_X86_64_PC32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Gcc 8.1, -O2 optimisation build failure
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Comparing pointers to functions for constexpr fails with gcc not with clang
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Comparing pointers to functions for constexpr fails with gcc not with clang
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• Re: Comparing pointers to functions for constexpr fails with gcc not with clang
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Comparing pointers to functions for constexpr fails with gcc not with clang
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• Gcc 8.1, -O2 optimisation build failure
  • From: Wei Liu <wei.liu2@xxxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• SBV: JKT: Blsvn: JV Invite
  • From: "James Kitula." <y-kashihara@xxxxxxxxxxxx>
• Vector variable and undefined behavior
  • From: Florent Hivert <Florent.Hivert@xxxxxx>
• Re: Dynamically allocated array of function pointers
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Fwd: Dynamically allocated array of function pointers
  • From: Vladimir Reshetnikov <v.reshetnikov@xxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Gampu Z <gampuzampe@xxxxxxxxx>
• Re:Re: Re: For help:Unexpected fail about testsuite of GCC
  • From: 陈龙 <18116491546@xxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Gampu Z <gampuzampe@xxxxxxxxx>
• Re: -finstrument-functions
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Gampu Z <gampuzampe@xxxxxxxxx>
• RE: -finstrument-functions
  • From: Ming Cheng <Ming.Cheng@xxxxxxxxxxxxx>
• Re: Help required for GCC structure variable assignment optimization
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Help required for GCC structure variable assignment optimization
  • From: Gampu Z <gampuzampe@xxxxxxxxx>
• Re: -finstrument-functions
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• -finstrument-functions
  • From: Ming Cheng <Ming.Cheng@xxxxxxxxxxxxx>
• Re: makeinfo errors building gcc from git
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: makeinfo errors building gcc from git
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: makeinfo errors building gcc from git
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: makeinfo errors building gcc from git
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• makeinfo errors building gcc from git
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Janke <floss@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Re: For help:Unexpected fail about testsuite of GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Janke <floss@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Janke <floss@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Andrew Janke <floss@xxxxxxxxxxx>
• Re: Compiling GCC for different x86 CPU generation
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re:Re: For help:Unexpected fail about testsuite of GCC
  • From: 陈龙 <18116491546@xxxxxxx>
• Compiling GCC for different x86 CPU generation
  • From: Andrew Janke <floss@xxxxxxxxxxx>
• Re: lto-wrapper: fatal error
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: lto-wrapper: fatal error
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• lto-wrapper: fatal error
  • From: "J.W. Jagersma" <jwjagersma@xxxxxxxxx>
• Re: 128-bit inline assembly addition
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Bugzilla: how to get a copy of own reports and own comments?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Bugzilla: how to get a copy of own reports and own comments?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Bugzilla: how to get a copy of own reports and own comments?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Bugzilla: how to get a copy of own reports and own comments?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Bugzilla: how to get a copy of own reports and own comments?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: GCC 8.1.0 STL vs Valgrind
  • From: Paul Smith <psmith@xxxxxxx>
• Re: GCC 8.1.0 STL vs Valgrind
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: libgfortran.so.3 versus libgfortran.so.4
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• libgfortran.so.3 versus libgfortran.so.4
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 8.1.0 STL vs Valgrind
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• GCC 8.1.0 STL vs Valgrind
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to re-test just 1 failed test src file?
  • From: Jeff Law <law@xxxxxxxxxx>
• Comparing pointers to functions for constexpr fails with gcc not with clang
  • From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
• make check (testing): how to re-test just 1 failed test src file?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Question about adapting LTO source code
  • From: 李宗霖 <fight1995go@xxxxxxxxx>
• Re: About LTO
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• About LTO
  • From: 李宗霖 <fight1995go@xxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: make check (testing): how to clean old test results?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• make check (testing): how to clean old test results?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Problemsbuilding 8.1.0 on AIX 5.3
  • From: Albert Chin <gcc-help@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: 128-bit inline assembly addition
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Building an older gcc
  • From: Zoltán Kócsi <zoltan@xxxxxxxxxxxxx>
• Re: 128-bit inline assembly addition
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• 128-bit inline assembly addition
  • From: Marcel Keller <mks.keller@xxxxxxxxx>
• RE: ARMv8.4 intrinsics?
  • From: Tamar Christina <Tamar.Christina@xxxxxxx>
• Re: Building an older gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Building an older gcc
  • From: Toby Douglass <toby@xxxxxxxxxxxxxx>
• Building an older gcc
  • From: Zoltán Kócsi <zoltan@xxxxxxxxxxxxx>
• Re: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Ignitus Boyone <ignitusboyone@xxxxxxxxx>
• Re: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Fwd: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• ARMv8.4 intrinsics?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Fwd: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Ignitus Boyone <ignitusboyone@xxxxxxxxx>
• Re: REG_WORDS_BIG_ENDIAN
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Fwd: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Fwd: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: REG_WORDS_BIG_ENDIAN
  • From: Jeff Law <law@xxxxxxxxxx>
• Fwd: Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Ignitus Boyone <ignitusboyone@xxxxxxxxx>
• REG_WORDS_BIG_ENDIAN
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• RE: Problem with debugging -m32 program
  • From: Ignitus Boyone <ignitusboyone@xxxxxxxxx>
• Re: Problem with GCC in-tree plugin build (autoconf, libtool).
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with GCC in-tree plugin build (autoconf, libtool).
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Problem with GCC in-tree plugin build (autoconf, libtool).
  • From: Oleg Ogurtsov <o.ogurtsov@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: SOLVED: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: SOLVED: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Frame pointer for Thumb-2 non-leaf functions
  • From: Denis Khalikov <d.khalikov@xxxxxxxxxxxxxxxxxxx>
• SOLVED: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: Frame pointer for Thumb-2 non-leaf functions
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Frame pointer for Thumb-2 non-leaf functions
  • From: Denis Khalikov <d.khalikov@xxxxxxxxxxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: How to include "wide int" in code
  • From: Andrew Haley <aph@xxxxxxxxxx>
• How to include "wide int" in code
  • From: "colinb2 ." <colinb2@xxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: having multiple copies of _GLOBAL__sub_I__xxxx which are calling std::ios_base::Init::Init()@GLIBCXX_3.4
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: having multiple copies of _GLOBAL__sub_I__xxxx which are calling std::ios_base::Init::Init()@GLIBCXX_3.4
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Duplicate Symbols when compiling with arm-linux-gnueabihf
  • From: Ignitus Boyone <ignitusboyone@xxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Danny Milosavljevic <dannym@xxxxxxxxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: having multiple copies of _GLOBAL__sub_I__xxxx which are calling std::ios_base::Init::Init()@GLIBCXX_3.4
  • From: Liu Hao <lh_mouse@xxxxxxx>
• having multiple copies of _GLOBAL__sub_I__xxxx which are calling std::ios_base::Init::Init()@GLIBCXX_3.4
  • From: "Klaus Rudolph" <lts-rudolph@xxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Gábor Boskovits <boskovits@xxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: "Vahith .j" <vahith@xxxxxxxxx>
• gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
  • From: Jan Nieuwenhuizen <janneke@xxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: invalid 'asm': invalid operand for code 'H'
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Problem with debugging -m32 program
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re:Re: For help:Unexpected fail about testsuite of GCC
  • From: 陈龙 <18116491546@xxxxxxx>
• Re: question about "x86 Built-in Functions" to detect cpu type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: question about "x86 Built-in Functions" to detect cpu type
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: question about "x86 Built-in Functions" to detect cpu type
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: question about "x86 Built-in Functions" to detect cpu type
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: question about "x86 Built-in Functions" to detect cpu type
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• question about "x86 Built-in Functions" to detect cpu type
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Help to install the gcc compiler on Windows...I'm using a MacBook Pro (Bootcamp)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Help to install the gcc compiler on Windows...I'm using a MacBook Pro (Bootcamp)
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• invalid 'asm': invalid operand for code 'H'
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Help to install the gcc compiler on Windows...I'm using a MacBook Pro (Bootcamp)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Help to install the gcc compiler on Windows...I'm using a MacBook Pro (Bootcamp)
  • From: Falde Ettore <ettorefalde97@xxxxxxxxx>
• All Language Translation Solutions
  • From: "Vibha Jain via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: "Vahith .j" <vahith@xxxxxxxxx>
• Re: regarding gcc 4.1 to gcc 4.8
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• regarding gcc 4.1 to gcc 4.8
  • From: "Vahith .j" <vahith@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Address of return address
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Address of return address
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Address of return address
  • From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: I'm looking for GCC compiler 6.3 for LINUX
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: I'm looking for GCC compiler 6.3 for LINUX
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: I'm looking for GCC compiler 6.3 for LINUX
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• I'm looking for GCC compiler 6.3 for LINUX
  • From: "Lopez, Juan via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: About a error reported by gcc
  • From: Liu Hao <lh_mouse@xxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: For help:Unexpected fail about testsuite of GCC
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• For help:Unexpected fail about testsuite of GCC
  • From: 陈龙 <18116491546@xxxxxxx>
• Re: complete novice struggling to run the Fortran Compiler
  • From: Tim Zeisloft <tim@xxxxxxxxxxxxxxxxxxxx>
• complete novice struggling to run the Fortran Compiler
  • From: "frank.shed via gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: how to build a faster gcc working on a specific project
  • From: "U.Mutlu" <for-gmane@xxxxxxxxxxx>
• Re: how to build a faster gcc working on a specific project
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: how to build a faster gcc working on a specific project
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: how to build a faster gcc working on a specific project
  • From: "U.Mutlu" <for-gmane@xxxxxxxxxxx>
• Re: list of gcc branches in the repo
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: list of gcc branches in the repo
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: list of gcc branches in the repo
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: list of gcc branches in the repo
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• list of gcc branches in the repo
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• how to build a faster gcc working on a specific project
  • From: 问 题 <ihave1111questions@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: Martin Sebor <msebor@xxxxxxxxx>
• RE: New Allingham_Swift_ copy2618CAS
  • From: Alice <alice@xxxxxxxxxxxxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Weird compiler error [-Werror=discarded-qualifiers], though correct IMO
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Eliminating the dependency on the old C header files
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Eliminating the dependency on the old C header files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Eliminating the dependency on the old C header files
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: gcc c++ compiler?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Fwd: gcc c++ compiler?
  • From: "Eng.Bassam" <bassam86@xxxxxxxxx>
• Re: GCC8
  • From: Janne Blomqvist <blomqvist.janne@xxxxxxxxx>
• GCC8
  • From: Jerome Huck <jeromehuck@xxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Giving hints to the compiler/optimizer (#pragma hint ...)
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: gcc version 4.8.5 20150623 / Meltdown and/or Spectre vulnerabilities
  • From: Vassilena Treneva <treneva@xxxxxxxxx>
• Re: std::filesystem::path::append oddity
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: std::filesystem::path::append oddity
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Extending the core language via a gcc plugin possible?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• std::filesystem::path::append oddity
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: non-bootstrap build always uses the system-compiler. Bug?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• non-bootstrap build always uses the system-compiler. Bug?
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Using -flto in CXXFLAGS_FOR_TARGET
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: gcc version 4.8.5 20150623 / Meltdown and/or Spectre vulnerabilities
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc version 4.8.5 20150623 / Meltdown and/or Spectre vulnerabilities
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• gcc version 4.8.5 20150623 / Meltdown and/or Spectre vulnerabilities
  • From: Vassilena Treneva <treneva@xxxxxxxxx>
• Re: Using -flto in CXXFLAGS_FOR_TARGET
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Using -flto in CXXFLAGS_FOR_TARGET
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: Using -flto in CXXFLAGS_FOR_TARGET
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Using -flto in CXXFLAGS_FOR_TARGET
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Gcc 8.1 OpenMP 4.5 offload to Nvidia GPU
  • From: "Jost, Gabriele (ARC-TNC)[CSRA, LLC]" <gabriele.jost@xxxxxxxx>
• Re: configure for gcc 6.4.0 build on Fedora 27
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: configure for gcc 6.4.0 build on Fedora 27
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: What could cause this SEGV
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: configure for gcc 6.4.0 build on Fedora 27
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: configure for gcc 6.4.0 build on Fedora 27
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• Re: configure for gcc 6.4.0 build on Fedora 27
  • From: "U.Mutlu" <um@xxxxxxxxxxx>
• configure for gcc 6.4.0 build on Fedora 27
  • From: stimits@xxxxxxxxxxx
• Re: What could cause this SEGV
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Building with -m32/-m31 support without multilibs
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Building with -m32/-m31 support without multilibs
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Building with -m32/-m31 support without multilibs
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: What could cause this SEGV
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: What could cause this SEGV
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: What could cause this SEGV
  • From: Andrew Haley <aph@xxxxxxxxxx>
• AW: gcc git repository issue?
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Ajay Garg <ajaygargnsit@xxxxxxxxx>
• Re: gcc git repository issue?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• gcc git repository issue?
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• What could cause this SEGV
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Ajay Garg <ajaygargnsit@xxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Ajay Garg <ajaygargnsit@xxxxxxxxx>
• Re: Unable to disable shared-libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Unable to disable shared-libraries
  • From: Ajay Garg <ajaygargnsit@xxxxxxxxx>
• Re: number of calls to hash function in unordered_set
  • From: Frank Tetzel <s1445051@xxxxxxxxxxxxxxxxxxxxxx>
• Re: number of calls to hash function in unordered_set
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: number of calls to hash function in unordered_set
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• number of calls to hash function in unordered_set
  • From: Frank Tetzel <s1445051@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Is HPUX ia64 a supported target?
  • From: Jeff Law <law@xxxxxxxxxx>
• Is HPUX ia64 a supported target?
  • From: Brian Groose <brian@xxxxxxxxxx>
• Re: -O1 runtime difference between gcc and clang
  • From: Andrew Haley <aph@xxxxxxxxxx>
• -O1 runtime difference between gcc and clang
  • From: "M. Chaturvedi" <mmanu.chaturvedi@xxxxxxxxx>
• Re: Does it safe to link several objects which compiled with different `--std` flags ?
  • From: Remus Clearwater <remus.clearwater@xxxxxxxxx>
• Re: Does it safe to link several objects which compiled with different `--std` flags ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Does it safe to link several objects which compiled with different `--std` flags ?
  • From: Remus Clearwater <remus.clearwater@xxxxxxxxx>
• Re: gfortran not using SIMD / ymm registers while LLVM (Julia) does
  • From: Chris Elrod <elrodc@xxxxxxxxx>
• gfortran not using SIMD / ymm registers while LLVM (Julia) does
  • From: Chris Elrod <elrodc@xxxxxxxxx>
• Re: Adding new rule into compiler
  • From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
• STARTFILE_SPEC and calling a function.
  • From: Kalamatee <kalamatee@xxxxxxxxx>
• Adding new rule into compiler
  • From: 李宗霖 <fight1995go@xxxxxxxxx>
• Re: Gcc precompiled header problem.
  • From: François Leblanc <fleblanc50@xxxxxxxxx>
• Re: Linking a shared library
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Gcc precompiled header problem.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Gcc precompiled header problem.
  • From: François Leblanc <fleblanc50@xxxxxxxxx>