GCC Help

• Thread Index

• Re: how can I put c++ global destructor in a specific section
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: how can I put c++ global destructor in a specific section
  • From: Olivier Diotte <olivier@xxxxxxxxx>
• Re: how can I put c++ global destructor in a specific section
  • From: <papa@xxxxxxxxxxx>
• Re: how can I put c++ global destructor in a specific section
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: how can I put c++ global destructor in a specific section
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: how can I put c++ global destructor in a specific section
  • From: <papa@xxxxxxxxxxx>
• how can I put c++ global destructor in a specific section
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: How to clear unknown pragma warning for OpenMP?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unknown pragma warning for OpenMP?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear unknown pragma warning for OpenMP?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unknown pragma warning for OpenMP?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to clear unknown pragma warning for OpenMP?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: <papa@xxxxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: <papa@xxxxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear unused variable warnings created by static assert?
  • From: Niklas Gürtler <profclonk@xxxxxxxxx>
• How to clear unused variable warnings created by static assert?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Attribute directive ignored for naked procedure in Ada
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Using structs in target .opt file?
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Re: gcc on 64 bit && different behaviour while 'cast to pointer from integer of different size'
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc on 64 bit && different behaviour while 'cast to pointer from integer of different size'
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc on 64 bit && different behaviour while 'cast to pointer from integer of different size'
  • From: Matthias Apitz <guru@xxxxxxxxxxx>
• Re: When did 'pragma diagnostic' become available?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: When did 'pragma diagnostic' become available?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• When did 'pragma diagnostic' become available?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: compile options for libstdc++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• compile options for libstdc++
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Disable optimizations on one function (was: 'pragma optimize' ...)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did 'pragma optimize' become available?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: When did 'pragma optimize' become available?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: -flto=N
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• -flto=N
  • From: Dilyan Palauzov <dilyan.palauzov@xxxxxxxxx>
• Re: When did 'pragma optimize' become available?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: When did 'pragma optimize' become available?
  • From: David Wohlferd <dw@xxxxxxxxxxxxxxxxxx>
• When did 'pragma optimize' become available?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Rebuilding gcc/gnat after changes
  • From: Jan Sommer <soja-lists@xxxxxxxxxxxxxxxxxx>
• Re: To debug C program on assembly level
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc-help@xxxxxxxxxxx
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Specify multiple --with-native-system-header-dir
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• gcc-help@xxxxxxxxxxx
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: To debug C program on assembly level
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: Re: To debug C program on assembly level
  • From: johnsfine@xxxxxxxxxxx
• Re: To debug C program on assembly level
  • From: Andrew Haley <aph@xxxxxxxxxx>
• To debug C program on assembly level
  • From: xparmenides <xparmenides@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: achkan <ashsalehi4133@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: johnsfine@xxxxxxxxxxx
• Re: segfault when functions are defined in headers or inlined
  • From: achkan <ashsalehi4133@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: achkan <ashsalehi4133@xxxxxxxxx>
• Re: segfault when functions are defined in headers or inlined
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• segfault when functions are defined in headers or inlined
  • From: achkan <ashsalehi4133@xxxxxxxxx>
• GCC 4.9.2 dwarf problem
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Position-independent code; fixed-address data and bss
  • From: Christopher Collins <ccollins476ad@xxxxxxxxx>
• Re: Need help to complile gcc-5.1.0
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Need help to complile gcc-5.1.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: Need help to complile gcc-5.1.0
  • From: "Rai, Raj (CSSA)" <Raj.Rai@xxxxxxxxxxxx>
• Re: Need help to complile gcc-5.1.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Need help to complile gcc-5.1.0
  • From: "Rai, Raj (CSSA)" <Raj.Rai@xxxxxxxxxxxx>
• Re: where is unwind.h
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: where is unwind.h
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: where is unwind.h
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: where is unwind.h
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: where is unwind.h
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: where is unwind.h
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: unique_ptr and operator<<
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• unique_ptr and operator<<
  • From: <papa@xxxxxxxxxxx>
• where is unwind.h
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Segment fault s-attrtab genattrtab (solved)
  • From: bruce m beach <brucembeach@xxxxxxxxx>
• Re: How to solve the relationship between gcc and glibc when building cross compiler toolchain?
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• RE: How to solve the relationship between gcc and glibc when building cross compiler toolchain?
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Re: [Mingw-w64-public] toUpper()
  • From: <papa@xxxxxxxxxxx>
• Re: [Mingw-w64-public] toUpper()
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: [Mingw-w64-public] toUpper()
  • From: <papa@xxxxxxxxxxx>
• std::locale
  • From: <papa@xxxxxxxxxxx>
• Re: toUpper()
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
  • From: Ondrej Jakubcik <ojakubcik@xxxxxxxxx>
• Re: [Mingw-w64-public] toUpper()
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Bootstrapping GCC 5.1.0 together with Binutils 2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [Mingw-w64-public] toUpper()
  • From: Riot <rain.backnet@xxxxxxxxx>
• toUpper()
  • From: <papa@xxxxxxxxxxx>
• Bootstrapping GCC 5.1.0 together with Binutils 2.25
  • From: Ondrej Jakubcik <ojakubcik@xxxxxxxxx>
• Re: LAPACK installation on Windows
  • From: Tim Prince <n8tm@xxxxxxx>
• LAPACK installation on Windows
  • From: Borut Černe <borut.cerne@xxxxxxxxxxxxxxxxxx>
• Re: Issue with inline functions in dynamic libraries since GCC 5.1.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Issue with inline functions in dynamic libraries since GCC 5.1.0
  • From: Bas Mevissen <abuse@xxxxxxxxxxxxxx>
• Re: -fvisibility=hidden vs. typeinfo
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -fvisibility=hidden vs. typeinfo
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: -fvisibility=hidden vs. typeinfo
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -fvisibility=hidden vs. typeinfo
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: VLA parameters
  • From: shiv <00shiv@xxxxxxxxx>
• Re: VLA parameters
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• VLA parameters
  • From: shiv <00shiv@xxxxxxxxx>
• Re: Issue with inline functions in dynamic libraries since GCC 5.1.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Issue with inline functions in dynamic libraries since GCC 5.1.0
  • From: Bas Mevissen <abuse@xxxxxxxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Siddhartha Jain <tmfs10@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to solve the relationship between gcc and glibc when building cross compiler toolchain?
  • From: jpcstpj7281 <jpcstpj7281@xxxxxxx>
• Re: Custom gcc installation include files
  • From: Siddhartha Jain <tmfs10@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Siddhartha Jain <tmfs10@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Siddhartha Jain <tmfs10@xxxxxxxxx>
• Re: Custom gcc installation include files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: internal compiler error: verify_type failed
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• internal compiler error: verify_type failed
  • From: Alex Markin <alexanius@xxxxxxxxx>
• Custom gcc installation include files
  • From: Siddhartha Jain <tmfs10@xxxxxxxxx>
• Mapping between variables and GIMPLE statements
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Which version of the libstdc++ is shipped with gcc5.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Enable Pragma assert for all adb-files
  • From: Jan Sommer <soja-lists@xxxxxxxxxxxxxxxxxx>
• Re: The issue of libgomp on MIC
  • From: Kirill Yukhin <kirill.yukhin@xxxxxxxxx>
• Re: The issue of libgomp on MIC
  • From: Ilya Verbin <iverbin@xxxxxxxxx>
• Re: The issue of libgomp on MIC
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Which version of the libstdc++ is shipped with gcc5.1
  • From: Laurent Thévenoux <laurent.thevenoux@xxxxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: The issue of libgomp on MIC
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: How to support C++ in a new OS
  • From: Tim Prince <n8tm@xxxxxxx>
• How to support C++ in a new OS
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Include and lib search paths
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Include and lib search paths
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Include and lib search paths
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: GCOV Cross Profiling: __gcov_flush() does not flush coverage data for shared libraries
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCOV Cross Profiling: __gcov_flush() does not flush coverage data for shared libraries
  • From: Utpal Patel <utpal.patel@xxxxxxxxx>
• Re: GCOV Cross Profiling: __gcov_flush() does not flush coverage data for shared libraries
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Parameter pack in non-last position in function formal parameter list?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Parameter pack in non-last position in function formal parameter list?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Parameter pack in non-last position in function formal parameter list?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCOV Cross Profiling: __gcov_flush() does not flush coverage data for shared libraries
  • From: Utpal Patel <utpal.patel@xxxxxxxxx>
• Re: Parameter pack in non-last position in function formal parameter list?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Parameter pack in non-last position in function formal parameter list?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Parameter pack in non-last position in function formal parameter list?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Error Building GCC as PIE
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: finding the data file
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: finding the data file
  • From: "Max S." <king@xxxxxxxxxxxxxxxxxx>
• Re: [Mingw-w64-public] finding the data file
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: finding the data file
  • From: LRN <lrn1986@xxxxxxxxx>
• finding the data file
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: Problem with -static-libstdc++ on Mac OS X
  • From: Iain Sandoe <iain@xxxxxxxxxxxxxxxx>
• Re: Problem with -static-libstdc++ on Mac OS X
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: Problem with -static-libstdc++ on Mac OS X
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: Problem with -static-libstdc++ on Mac OS X
  • From: Iain Sandoe <iain@xxxxxxxxxxxxxxxx>
• Re: Problem with -static-libstdc++ on Mac OS X
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Problem with -static-libstdc++ on Mac OS X
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: std::function and shared object libraries
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: std::function and shared object libraries
  • From: johnsfine@xxxxxxxxxxx
• Re: std::function and shared object libraries
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: AutoFDO totorial
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: default alignment
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: AutoFDO totorial
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: Can the GCC toolchain be built AS a PIE?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Can the GCC toolchain be built AS a PIE?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Can the GCC toolchain be built AS a PIE?
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: default alignment
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: default alignment
  • From: Andrew Haley <aph@xxxxxxxxxx>
• default alignment
  • From: Pawel Por <porparek@xxxxxxxxx>
• Re: __GXX_ABI_VERSION: 1002 vs. 1008
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• __GXX_ABI_VERSION: 1002 vs. 1008
  • From: Nathan Ridge <zeratul976@xxxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• How to make gfortran give a warning for reading variables declared as intent(out) without initializing it first?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Sebastian <sebastianspublicaddress@xxxxxxxxxxxxxx>
• Re: Can the GCC toolchain be built AS a PIE?
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Sebastian <sebastianspublicaddress@xxxxxxxxxxxxxx>
• Re: std::function and shared object libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• std::function and shared object libraries
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Sebastian <sebastianspublicaddress@xxxxxxxxxxxxxx>
• Re: how to analysis and measure the GCC OpenMP performance and overhead
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: how to analysis and measure the GCC OpenMP performance and overhead
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: how to analysis and measure the GCC OpenMP performance and overhead
  • From: "xingjing lu" <xingjinglu@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Sebastian <sebastianspublicaddress@xxxxxxxxxxxxxx>
• Can the GCC toolchain be built AS a PIE?
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: "Ellis N. Thomas" <ExtraLeveLInSoftware@xxxxxxxxxxxx>
• Re: bitwise & optimization
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bitwise & optimization
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Are arrays guaranteed to be affected by a "memory" clobber?
  • From: Sebastian <sebastianspublicaddress@xxxxxxxxxxxxxx>
• Re: GCC 5.1 and sanitizer issue
  • From: Millad Ghane <millad.mg@xxxxxxxxx>
• Re: bitwise & optimization
  • From: Vincent Diepeveen <diep@xxxxxxxxx>
• Re: bitwise & optimization
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Norbert Lange <lange@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Norbert Lange <lange@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Norbert Lange <lange@xxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: "Ellis N. Thomas" <ExtraLeveLInSoftware@xxxxxxxxxxxx>
• Re: GCC 5.1 and sanitizer issue
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: bitwise & optimization
  • From: Vincent Diepeveen <diep@xxxxxxxxx>
• bitwise & optimization
  • From: Fisnik Kastrati <kastrati@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: GCC 5.1 and sanitizer issue
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.1 and sanitizer issue
  • From: Millad Ghane <millad.mg@xxxxxxxxx>
• Re: GCC 5.1 and sanitizer issue
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is configure (with bootstrap) same as configuring in three build directories (without bootstrap)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: "Ellis N. Thomas" <ExtraLeveLInSoftware@xxxxxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Lars Gullik Bjønnes <larsbj@xxxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Support for C++14 shared_mutex in libstdc++
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCC 5.1 and sanitizer issue
  • From: Millad Ghane <millad.mg@xxxxxxxxx>
• Support for C++14 shared_mutex in libstdc++
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• floating point exception calling cpu_time()
  • From: Nicolas Bock <nicolasbock@xxxxxxxxx>
• Re: Is configure (with bootstrap) same as configuring in three build directories (without bootstrap)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Is configure (with bootstrap) same as configuring in three build directories (without bootstrap)
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Lars Gullik Bjønnes <larsbj@xxxxxxxxxx>
• Re: Problems building Binutils-2.25
  • From: Tim Prince <n8tm@xxxxxxx>
• Problems building Binutils-2.25
  • From: "Ellis N. Thomas" <ExtraLeveLInSoftware@xxxxxxxxxxxx>
• Re: gcc/cc1plus without executable bit, small, and "data" rather than "ELF 64-bit executable"
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• gcc/cc1plus without executable bit, small, and "data" rather than "ELF 64-bit executable"
  • From: james harvey <jamespharvey20@xxxxxxxxx>
• AutoFDO totorial
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: gcc 5.1.1 requires linkage with -lpthread?
  • From: Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx>
• Re: gcc 5.1.1 requires linkage with -lpthread?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc 5.1.1 requires linkage with -lpthread?
  • From: Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx>
• Re: GCC 4.8.4 mpfr configuration error
  • From: Ritchie Cai <ritchiecai@xxxxxxxxx>
• Re: GCC 4.8.4 mpfr configuration error
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: GCC 4.8.4 mpfr configuration error
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC 4.8.4 mpfr configuration error
  • From: Ritchie Cai <ritchiecai@xxxxxxxxx>
• Re: [RFC] Using SPEC CPU2006
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: [RFC] Using SPEC CPU2006
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: [RFC] Using SPEC CPU2006
  • From: Vincent Diepeveen <diep@xxxxxxxxx>
• Re: [RFC] Using SPEC CPU2006
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• [RFC] Using SPEC CPU2006
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• arm thumb instruction compiled by GCC is not match with spec
  • From: loody <miloody@xxxxxxxxx>
• Valgrind with dynamically linked GCC plugin
  • From: Suryansh Kumar <suryansh.1234@xxxxxxxxx>
• building libsanitizer independently of gcc
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• standalone cpp linked with libcpp
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: static_casting from Parent to Child??
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• static_casting from Parent to Child??
  • From: "ArbolOne" <ArbolOne@xxxxxxxxxx>
• GCC Plugin: How to replace an existing pass from plugin
  • From: Tarun Prabhu <tarunprabhu@xxxxxxxxx>
• g++ interface to ScalaLab scientific programming environment routines
  • From: sterg <sterg@xxxxxxxxxxxxx>
• Re: Specify named registers for ARM inline asm
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Specify named registers for ARM inline asm
  • From: Jeremy Hall <jeremy.m0jnx@xxxxxxxxx>
• Re: [[ noreturn ]]
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: [[ noreturn ]]
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: [[ noreturn ]]
  • From: Andrew Melo <andrew.melo@xxxxxxxxx>
• Re: [[ noreturn ]]
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: [[ noreturn ]]
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Thread sanitizer blocking the program
  • From: brahim brahim <brahimalekhine@xxxxxxxxx>
• Re: [[ noreturn ]]
  • From: Andrew Melo <andrew.melo@xxxxxxxxx>
• [[ noreturn ]]
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Lars Gullik Bjønnes <larsbj@xxxxxxxxxx>
• Re: -fsanitize=nonnull-attribute failing on empty container
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to test 4 compiler version
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCCG with C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: __builtin_types_compatible_p or__is_array() alternative for g++?
  • From: Eduardo Piombino <drakorg@xxxxxxxxx>
• Re: How to test 4 compiler version
  • From: Michael Powell <mwpowellhtx@xxxxxxxxx>
• Re: How to test 4 compiler version
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• How to test 4 compiler version
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• -fsanitize=nonnull-attribute failing on empty container
  • From: Lars Gullik Bjønnes <larsbj@xxxxxxxxxx>
• Re: GCCG with C++11
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: GCCG with C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCCG with C++11
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: GCCG with C++11
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Re: GCCG with C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCCG with C++11
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: I am in a in-path
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE:Problem build gcc 5.1 with openacc support for nvptx
  • From: KESTENER Pierre <pierre.kestener@xxxxxx>
• Re: I am in a in-path
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: Checking for -fstrict-aliasing
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: __builtin_types_compatible_p or__is_array() alternative for g++?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: I am in a in-path
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: I am in a in-path
  • From: Andrew Haley <aph@xxxxxxxxxx>
• I am in a in-path
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• __builtin_types_compatible_p or__is_array() alternative for g++?
  • From: Eduardo Piombino <drakorg@xxxxxxxxx>
• Re: _Static_warning?
  • From: Eduardo Piombino <drakorg@xxxxxxxxx>
• Re: Checking for -fstrict-aliasing
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Checking for -fstrict-aliasing
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: O flags
  • From: Robert Mijakovic <mijakovi@xxxxxxxxx>
• Re: O flags
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: O flags
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• O flags
  • From: Robert Mijakovic <mijakovi@xxxxxxxxx>
• Re: to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: hilary <hilary.law@xxxxxxxxx>
• Re: to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: hilary <hilary.law@xxxxxxxxx>
• Problem build gcc 5.1 with openacc support for nvptx
  • From: KESTENER Pierre <pierre.kestener@xxxxxx>
• Re: to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: Scott Davies <code-poet@xxxxxxxxxxx>
• to install c and c++ compiler on OS X Yosemite 10.10 3
  • From: hilary <hilary.law@xxxxxxxxx>
• Re: libgomp build: undeclared openacc stuff
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: libgomp build: undeclared openacc stuff
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: how do I remove this window
  • From: Ángel González <keisial@xxxxxxxxx>
• how do I remove this window
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• libgomp build: undeclared openacc stuff
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Norbert Lange <lange@xxxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Re: Is gcc allowed to eliminate writes in a destructor?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: _Static_warning?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Is gcc allowed to eliminate writes in a destructor?
  • From: Norbert Lange <nolange79@xxxxxxxxx>
• Re: _Static_warning?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: _Static_warning?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: _Static_warning?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: ARM: How does __attribute__((pcs("aapcs"))) should be used in HardFP ABI programs?
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Maintaining full frame information without -mapcs-frame on ARM
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: c++ generic function extension question
  • From: Kenny Simpson <theonetruekenny@xxxxxxxxx>
• Problem in using BDD libraries with GCC Plugin
  • From: Nishant Sahni <nishantsahni1994@xxxxxxxxx>
• Re: _Static_warning?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: GAS
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GAS
  • From: Saidgani <saidgani@xxxxxxxxxxx>
• Re: PlaySoundW
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: PlaySoundW
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: PlaySoundW
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• PlaySoundW
  • From: "Hotmail \(ArbolOne\)" <ArbolOne@xxxxxxxxxx>
• Re: _Static_warning?
  • From: Eduardo Piombino <drakorg@xxxxxxxxx>
• Re: _Static_warning?
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• _Static_warning?
  • From: Eduardo Piombino <drakorg@xxxxxxxxx>
• Re: c++ generic function extension question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• c++ generic function extension question
  • From: Kenny Simpson <theonetruekenny@xxxxxxxxx>
• Re: How to use -nostdlib?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: How to use -nostdlib?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: How to use -nostdlib?
  • From: Ángel González <keisial@xxxxxxxxx>
• Address Sanitizer fails due to odd system library mappings
  • From: Richard Sewards <richard.sewards@xxxxxxxx>
• Memory leaks when using openmp
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Reference declaration with self-assignment. Is it legal? G++ says it is!
  • From: Carlos Ferreira <carlosmf.pt@xxxxxxxxx>
• Re: Reference declaration with self-assignment. Is it legal? G++ says it is!
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Reference declaration with self-assignment. Is it legal? G++ says it is!
  • From: Carlos Ferreira <carlosmf.pt@xxxxxxxxx>
• Re: Re: No error message when format string is passed as variable to printf functions family
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: How to use -nostdlib?
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• How to use -nostdlib?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: No error message when format string is passed as variable to printf functions family
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: No error message when format string is passed as variable to printf functions family
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: No error message when format string is passed as variable to printf functions family
  • From: john smith <wempwer@xxxxxxxxx>
• Re: No error message when format string is passed as variable to printf functions family
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• libubsan with dynamic TLS
  • From: Philipp Ochsendorf <ochsendorf@xxxxxxxxxxxxxx>
• No error message when format string is passed as variable to printf functions family
  • From: john smith <wempwer@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: Linking OpenMP Statically on Mac
  • From: Ángel González <keisial@xxxxxxxxx>
• How to register a gimple pass in a gcc-5.1.0 plugin?
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Why are RB-trees used to implement std::set?
  • From: Michael Powell <mwpowellhtx@xxxxxxxxx>
• Re: Why are RB-trees used to implement std::set?
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why are RB-trees used to implement std::set?
  • From: Michael Powell <mwpowellhtx@xxxxxxxxx>
• Re: Why are RB-trees used to implement std::set?
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Re: Fwd: Why are RB-trees used to implement std::set?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Fwd: Why are RB-trees used to implement std::set?
  • From: Andrew Bell <andrew.bell.ia@xxxxxxxxx>
• Re: Why are RB-trees used to implement std::set?
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Why are RB-trees used to implement std::set?
  • From: Jakub Arnold <darthdeus@xxxxxxxxx>
• Question on "help=optimizers"
  • From: "Pawar, Amit" <Amit.Pawar@xxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: m-h-l <markus.lehmann@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: m-h-l <markus.lehmann@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Linking OpenMP Statically on Mac
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: msebor@xxxxxxxxxx
• long long bitfield layout (i686-linux-gnu)
  • From: "Daniel C. Klauer" <daniel.c.klauer@xxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Didier Kryn <kryn@xxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Toon Moene <toon@xxxxxxxxx>
• omp.h for windows xp 32 bits and turbo borland c++ ver 3.00
  • From: Ali Firouzbakht <firouzbakht.ali@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: m-h-l <markus.lehmann@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Didier Kryn <kryn@xxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: m-h-l <markus.lehmann@xxxxxxxxx>
• Re: gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc: why is "abcdef"[3] not a constant (error: initializer element is not constant)
  • From: m-h-l <markus.lehmann@xxxxxxxxx>
• Re: -mtls-dialect=gnu2
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• -mtls-dialect=gnu2
  • From: Sverd Johnsen <sverd.johnsen@xxxxxxxxxxxxxx>
• -fdirectives-only question
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Unary Operator ‘&&’
  • From: Jose Javier Gil <kasuki842@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Hogren <hogren@xxxxxxxxx>
• Re: question for gcc 4.9.2 which will generate debug symbol w/o any debug flag
  • From: Yixuan Huang <yixuan178@xxxxxxxxx>
• Re: v1 = (v2 == v3); generate branching instructions
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• v1 = (v2 == v3); generate branching instructions
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Test Error on GMP6.0.0.a
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Test Error on GMP6.0.0.a
  • From: "Henning Thedens" <hete2@xxxxxx>
• converting 1.475740e+19 to uint64_t: well-defined or undefined behaviour?
  • From: Mikael Pettersson <mikpelinux@xxxxxxxxx>
• Segment fault s-attrtab genattrtab
  • From: bruce m beach <brucembeach@xxxxxxxxx>
• Segment fault s-attrtab genattrtab
  • From: bruce m beach <brucembeach@xxxxxxxxx>
• Linking OpenMP Statically on Mac
  • From: Rob McDonald <rob.a.mcdonald@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Hogren <hogren@xxxxxxxxx>
• Re: SF soft-fp for i386
  • From: Ilya Enkovich <enkovich.gnu@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GCC 4.9.1 OpenMP 4.0 task nesting
  • From: Raúl Vidal <raulvior.bcn@xxxxxxxxx>
• GCC 4.9.1 OpenMP 4.0 task nesting
  • From: Raúl Vidal <raulvior.bcn@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Hogren <hogren@xxxxxxxxx>
• Re: SF soft-fp for i386
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• SF soft-fp for i386
  • From: Ilya Enkovich <enkovich.gnu@xxxxxxxxx>
• Re: Problem in g++ ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem in g++ ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem in g++ ?
  • From: Roger Ferrer Ibáñez <rofirrim@xxxxxxxxx>
• Problem in g++ ?
  • From: Andrew <ajc@xxxxxxx>
• Re: TRAMPOLINE
  • From: Jeff Law <law@xxxxxxxxxx>
• TRAMPOLINE
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Makefile:901 error when I trying to compile gcc 5.1 on cygwin
  • From: Hogren <hogren@xxxxxxxxx>
• memory address in gcc
  • From: Jose Javier Gil <kasuki842@xxxxxxxxx>
• question for gcc 4.9.2 which will generate debug symbol w/o any debug flag
  • From: Yixuan Huang <yixuan178@xxxxxxxxx>
• Re: Error building MinGW-W64 based on gcc-5.1.0
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: Error building MinGW-W64 based on gcc-5.1.0
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Error building MinGW-W64 based on gcc-5.1.0
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: Temporary Hard register
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Temporary Hard register
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Temporary Hard register
  • From: Jeff Law <law@xxxxxxxxxx>
• Temporary Hard register
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Disabling cmov for x86_64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Disabling cmov for x86_64
  • From: "ArbolOne" <ArbolOne@xxxxxxxxxx>
• 5.1.0/4.9.2 native mingw64 lto-wrapper.exe issues (PR 65559 and 65582)
  • From: Matt Breedlove <breedlove.matt@xxxxxxxxx>
• AIX - gcc debug mode - segfaults with static data
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• Re: Trouble cross-compiling GCC on Linux.
  • From: Tim Prince <n8tm@xxxxxxx>
• Trouble cross-compiling GCC on Linux.
  • From: Maxwell Dreytser <admin@xxxxxxxxx>
• Disabling cmov for x86_64
  • From: Rudra Siva <rudrasiva11@xxxxxxxxx>
• Re: Long compile times due mangling of return types in function templates
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Long compile times due mangling of return types in function templates
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Long compile times due mangling of return types in function templates
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Can't cross compile GCC 5.1.0 on Ubuntu 14.04.1 (LTS) using mingw-w64
  • From: Maxwell Dreytser <admin@xxxxxxxxx>
• Long compile times due mangling of return types in function templates
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Can't cross compile GCC 5.1.0 on Ubuntu 14.04.1 (LTS) using mingw-w64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Can't cross compile GCC 5.1.0 on Ubuntu 14.04.1 (LTS) using mingw-w64
  • From: Maxwell Dreytser <admin@xxxxxxxxx>
• Re: Help request compiling GNAT 4.8.2
  • From: Olivier Diotte <olivier@xxxxxxxxx>
• Re: Help request compiling GNAT 4.8.2
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Help request compiling GNAT 4.8.2
  • From: Didier Kryn <kryn@xxxxxxxx>
• Re: Help request compiling GNAT 4.8.2
  • From: Olivier Diotte <olivier@xxxxxxxxx>
• Re: OS and Inter Application Communication‏‏
  • From: Andrew Haley <aph@xxxxxxxxxx>
• OS and Inter Application Communication‏‏
  • From: Andrew Saxsma <ma_saxsma@xxxxxxx>
• Re: rpath question
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• rpath question
  • From: Aaron Cody <aaron@xxxxxxxxxxxxx>
• how i can clone a function?
  • From: Jose Javier Gil <kasuki842@xxxxxxxxx>
• Re: How to implement atomic swap with asm on PowerPC
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• How to implement atomic swap with asm on PowerPC
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: How to implement atomic swap with asm on PowerPC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimizes out TLS variable called in a child function
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• How to implement atomic swap with asm on PowerPC
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: Question about __builtin_add_overflow and friends
  • From: Scotty <sbauer@xxxxxxxxxxxx>
• Re: Question about __builtin_add_overflow and friends
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: gnu_parallel STL not vectorized?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: gcc -g options
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gnu_parallel STL not vectorized?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• [4.9.2] var-tracking size limit exceeded
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: gnu_parallel STL not vectorized?
  • From: Tim Prince <n8tm@xxxxxxx>
• gcc -g options
  • From: rac8006 <rac8006@xxxxxxx>
• Fwd: gnu_parallel STL not vectorized?
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Re: gnu_parallel STL not vectorized?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• gnu_parallel STL not vectorized?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GCC 5/6: C++'s std::string with "qsort" - works with old ABI, fails with new one
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCC 5/6: C++'s std::string with "qsort" - works with old ABI, fails with new one
  • From: Tobias Burnus <tobias.burnus@xxxxxxxxxxxxxxxxxxx>
• Question about __builtin_add_overflow and friends
  • From: Scotty <sbauer@xxxxxxxxxxxx>
• Help request compiling GNAT 4.8.2
  • From: Olivier Diotte <olivier@xxxxxxxxx>
• Re: Optimizes out TLS variable called in a child function
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Building a position independent binary with position independent data
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Downloading a C++ compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Infinite recursive call of extract_fixed_bit_field() and extract_split_bit_field()
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Re: Infinite recursive call of extract_fixed_bit_field() and extract_split_bit_field()
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Infinite recursive call of extract_fixed_bit_field() and extract_split_bit_field()
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Infinite recursive call of extract_fixed_bit_field() and extract_split_bit_field()
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Downloading a C++ compiler
  • From: John Kreutzberg <johnkreutzberg@xxxxxx>
• Re: Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Re: Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• AVR: Constants and loops
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Segment fault s-attrtab genattrtab
  • From: bruce m beach <brucembeach@xxxxxxxxx>
• Re: Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Re: Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• extract_fixed_bit_field() and extract_split_bit_field() infinite recursive call
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: William S Fulton <wsf@xxxxxxxxxxxxxxxxxxx>
• Help working out where GCC decides the size of 0xFFFFFFFF
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Problem with using VSX register constrains in extended asm
  • From: Sam Yates <sam.yates@xxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: William S Fulton <wsf@xxxxxxxxxxxxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <sin.pecado@xxxxxxxxx>
• Re: Specify -fno-exceptions in source file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Specify -fno-exceptions in source file
  • From: William S Fulton <wsf@xxxxxxxxxxxxxxxxxxx>
• Re: v8 LTO build fails on arm-linux-gnueabihf
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• RE: dlopen with RTLD_NOLOAD returns handle for library that failed to load previously
  • From: David Aldrich <David.Aldrich@xxxxxxxxxxxx>
• Re: dlopen with RTLD_NOLOAD returns handle for library that failed to load previously
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• dlopen with RTLD_NOLOAD returns handle for library that failed to load previously
  • From: David Aldrich <David.Aldrich@xxxxxxxxxxxx>
• Re: Compiling gcc 4.9.2 with ISL 0.14 fails at graphite-clast-to-gimple.c
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• cgraph_function_versioning
  • From: Jose Javier Gil <kasuki842@xxxxxxxxx>
• Re: Fail to compile trunk
  • From: Harald Servat <redcrash@xxxxxxxxx>
• Re: Fail to compile trunk
  • From: Peter Bergner <bergner@xxxxxxxxxxxx>
• Compiling gcc 4.9.2 with ISL 0.14 fails at graphite-clast-to-gimple.c
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• Re: SIGSEGV at df_ref_record()
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: SIGSEGV at df_ref_record()
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: SIGSEGV at df_ref_record()
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <sin.pecado@xxxxxxxxx>
• Re: SIGSEGV at df_ref_record()
  • From: Jeff Law <law@xxxxxxxxxx>
• SIGSEGV at df_ref_record()
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Error compiling gcc-4.9.2 when -arch=native
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Error compiling gcc-4.9.2 when -arch=native
  • From: "reachjlight@xxxxxxxxx" <reachjlight@xxxxxxxxx>
• Re: Need help to install C++ compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Need help to install C++ compiler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Need help to install C++ compiler
  • From: Lars Nielsen <lars@xxxxxxxxxxxxx>
• Need help to install C++ compiler
  • From: Kumar Aditya <kumaraditya86@xxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: backtrace a segfault
  • From: andre maute <andre.maute@xxxxxx>
• Re: What optimizations are included in -Og?
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: What optimizations are included in -Og?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: What optimizations are included in -Og?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• What optimizations are included in -Og?
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: backtrace a segfault
  • From: Bernhard Reutner-Fischer <rep.dot.nop@xxxxxxxxx>
• Re: backtrace a segfault
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: backtrace a segfault
  • From: Janne Blomqvist <blomqvist.janne@xxxxxxxxx>
• Re: backtrace a segfault
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <sin.pecado@xxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <pszilard@xxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: backtrace a segfault
  • From: Tobias Burnus <burnus@xxxxxxxx>
• Re: backtrace a segfault
  • From: Toon Moene <toon@xxxxxxxxx>
• Re: backtrace a segfault
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: backtrace a segfault
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: backtrace a segfault
  • From: Andrew Haley <aph@xxxxxxxxxx>
• backtrace a segfault
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• ARM: How does __attribute__((pcs(“aapcs”))) should be used in HardFP ABI programs?
  • From: Juan Gómez <atilag@xxxxxxxxx>
• Re: Code Error or Misleading Error Message?
  • From: Mike Harrold <alexmudmiko@xxxxxxxxx>
• Re: Code Error or Misleading Error Message?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Code Error or Misleading Error Message?
  • From: Marcin Sobieszczanski <marciso.gcc@xxxxxxxxx>
• Re: Code Error or Misleading Error Message?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Code Error or Misleading Error Message?
  • From: Mike Harrold <alexmudmiko@xxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Marek Polacek <polacek@xxxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Bobby Moretti <bobmoretti@xxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Bobby Moretti <bobmoretti@xxxxxxxxx>
• Re: c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: rbmj <rbmj@xxxxxxxxxxx>
• c++11 issue with static constexpr member initializer, constexpr constructor and member function pointer
  • From: Bobby Moretti <bobmoretti@xxxxxxxxx>
• Re: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: gcc parameter uncertainty
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• Re: gcc parameter uncertainty
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: v8 LTO build fails on arm-linux-gnueabihf
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• gcc parameter uncertainty
  • From: "Hooao" <hooao@xxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: Jeff Law <law@xxxxxxxxxx>
• Fwd: gcc internal failure during optimization delete_trivially_dead_insns
  • From: ftwilliam <ftwilliam@xxxxxxxxx>
• Re: v8 LTO build fails on arm-linux-gnueabihf
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: v8 LTO build fails on arm-linux-gnueabihf
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• v8 LTO build fails on arm-linux-gnueabihf
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: Use -O1 optimization but avoid <optimized out>?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Use -O1 optimization but avoid <optimized out>?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: C++ enums and shadowing
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ enums and shadowing
  • From: Ulrich Drepper <drepper@xxxxxxxxx>
• Re: C++ enums and shadowing
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• C++ enums and shadowing
  • From: Ulrich Drepper <drepper@xxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Martin Sebor <msebor@xxxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Andreas Schuh <andreas.schuh.84@xxxxxxxxx>
• Re: GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC 4.8.4 4.9.2 nifti_swap_2bytes optimization bug
  • From: Andreas Schuh <andreas.schuh.84@xxxxxxxxx>
• Re: .a file not linking correctly
  • From: Marcelo Utikawa da Fonseca <utikawa@xxxxxxxxx>
• Re: .a file not linking correctly
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• .a file not linking correctly
  • From: Marcelo Utikawa da Fonseca <utikawa@xxxxxxxxx>
• Re: compiling error for version 4.9.0 and 4.9.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: compiling error for version 4.9.0 and 4.9.2
  • From: Pengcheng Yang <yangpc@xxxxxxxxxxxxxxxx>
• Re: compiling error for version 4.9.0 and 4.9.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: compiling error for version 4.9.0 and 4.9.2
  • From: Pengcheng Yang <yangpc@xxxxxxxxxxxxxxxx>
• Re: Tcsh - Gentoo
  • From: David Kredba <nheghathivhistha@xxxxxxxxx>
• static-libgcc in multiple shared libraries
  • From: Cosmin Apreutesei <cosmin.apreutesei@xxxxxxxxx>
• Re: Tcsh - Gentoo
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Tcsh - Gentoo
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Tcsh - Gentoo
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Tcsh - Gentoo
  • From: David Kredba <nheghathivhistha@xxxxxxxxx>
• Re: __attribute__ aligned could be more efficient
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• how to disable stack protector per function?
  • From: Stas Sergeev <stsp@xxxxxxx>
• Re: __attribute__ aligned could be more efficient
  • From: Mason <slash.tmp@xxxxxxx>
• Re: __attribute__ aligned could be more efficient
  • From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
• __attribute__ aligned could be more efficient
  • From: Mason <slash.tmp@xxxxxxx>
• Howto build gcc for arm-uclinuxeabi
  • From: Mike Peterson <mikepe@xxxxxxxxxxx>
• Re: pre-processor strips out __attribute__((__packed_)_), is this expected?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: pre-processor strips out __attribute__((__packed_)_), is this expected?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Maintaining full frame information without -mapcs-frame on ARM
  • From: Austin Lund <austin.lund@xxxxxxxxx>
• pre-processor strips out __attribute__((__packed_)_), is this expected?
  • From: Daniel Dickman <didickman@xxxxxxxxx>
• [AArch64] Missed vectorization opportunity in cactusADM
  • From: "Ekanathan, Saravanan" <Saravanan.Ekanathan@xxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <pszilard@xxxxxx>
• Re: Recursive calloc() due to optimization
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Recursive calloc() due to optimization
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Recursive calloc() due to optimization
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Recursive calloc() due to optimization
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Re: libgccjit.so build fails with ISL enabled
  • From: Szilárd Páll <pszilard@xxxxxx>
• static linking with gnatmake
  • From: Didier Kryn <kryn@xxxxxxxx>
• gfortran question regarding dummy procedures
  • From: Roger Ferrer Ibáñez <rofirrim@xxxxxxxxx>
• gnat 5 ftbfs if ZCX_By_Default is set False
  • From: YunQiang Su <wzssyqa@xxxxxxxxx>
• FW: Another test with cross-compilig for BSD system from a Linux system.
  • From: Niccolò Ferrari <niccolo.ferrari@xxxxxxxxxx>
• Another test with cross-compilig for BSD system from a Linux system.
  • From: Niccolò Ferrari <niccolo.ferrari@xxxxxxxxxx>
• Re: Input stream with
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Input stream with
  • From: Andre-Marcel Hellmund <hellmund@xxxxxx>
• RE: Trying to build gcc cross compiler from linux to freebsd‏
  • From: Niccolò Ferrari <niccolo.ferrari@xxxxxxxxxx>