GCC Help

• Thread Index

• Can argv be NULL in C?
  • From: Yao Qi <qiyaoltc@xxxxxxxxx>
• Relocation avoidance for function pointers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: -fno-unwind-tables -fno-asynchronous-unwind-tables versus debugging
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -fno-unwind-tables -fno-asynchronous-unwind-tables versus debugging
  • From: Mason <slash.tmp@xxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: Mason <slash.tmp@xxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: "Michael J. Fuhrman" <mfuhrman@xxxxxxxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: "Michael J. Fuhrman" <mfuhrman@xxxxxxxxxxxx>
• Getting DWARF sub-program pure virtual attribute
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• -fno-unwind-tables -fno-asynchronous-unwind-tables versus debugging
  • From: waltdnes@xxxxxxxxxxxx
• Obtaining a list of a function's aliases in GCC-4.7+
  • From: "Bertram, Alexander" <alex@xxxxxxxxxxxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: Johann Klammer <klammerj@xxxxxx>
• Re: Is "-march=atom" deprecated?
  • From: waltdnes@xxxxxxxxxxxx
• Re: Is "-march=atom" deprecated?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: "mfuhrman@xxxxxxxxxxxx" <mfuhrman@xxxxxxxxxxxx>
• Re: Is "-march=atom" deprecated?
  • From: waltdnes@xxxxxxxxxxxx
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: "Maciej W. Rozycki" <macro@xxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: "Maciej W. Rozycki" <macro@xxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: "Maciej W. Rozycki" <macro@xxxxxxxxxx>
• Re: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Sed LLP
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Sed LLP
  • From: Mason <slash.tmp@xxxxxxx>
• RE: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: "Maciej W. Rozycki" <macro@xxxxxxxxxx>
• RE: Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Is "-march=atom" deprecated?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: gcc v5+ generates code that cause segment faults
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc v5+ generates code that cause segment faults
  • From: "mfuhrman@xxxxxxxxxxxx" <mfuhrman@xxxxxxxxxxxx>
• Why -mxgot on MIPS and not -fpic/-fPIC?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• GCC 6.2: configure: error: uint64_t or int64_t not found
  • From: <yhb@xxxxxxxxxxxxx>
• Re: Is "-march=atom" deprecated?
  • From: waltdnes@xxxxxxxxxxxx
• volatile struct requires static initialisation with asan in c++11 ?
  • From: Jan Smets <jan@xxxxxxxx>
• Re: Is "-march=atom" deprecated?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Is "-march=atom" deprecated?
  • From: waltdnes@xxxxxxxxxxxx
• gcov and logical lines of code spanning multiple source lines
  • From: Gordon Bowring <gordon.bowring@xxxxxxxxxx>
• Re: Order of expressions to minimize branch mis-predictions?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Order of expressions to minimize branch mis-predictions?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Optimization question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ exception handler on gnu arm cortex m4
  • From: Chris Johns <chrisj@xxxxxxxxx>
• Re: Optimization question
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Optimization question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Optimization question
  • From: Nikolaus Dunn <nikdunn1979@xxxxxxxxx>
• Re: Optimization question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -fsanitize=shift compile error
  • From: Mateusz Tabaka <tab.debugteam@xxxxxxxxx>
• Re: Optimization question
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: C++ exception handler on gnu arm cortex m4
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: C++ exception handler on gnu arm cortex m4
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• C++ exception handler on gnu arm cortex m4
  • From: Markus Klemm <m.klemm@xxxxxxxxxxxxxxxxxxxxx>
• Re: -fsanitize=shift compile error
  • From: Mason <slash.tmp@xxxxxxx>
• Re: -fsanitize=shift compile error
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• -fsanitize=shift compile error
  • From: Mateusz Tabaka <tab.debugteam@xxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Possible gcc bug in strict type aliasing
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Possible gcc bug in strict type aliasing
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: int64_t divide crashing on cortex-m3
  • From: drwho <drwho@xxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: int64_t divide crashing on cortex-m3
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: int64_t divide crashing on cortex-m3
  • From: drwho <drwho@xxxxxxxxxxxx>
• Re: int64_t divide crashing on cortex-m3
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• int64_t divide crashing on cortex-m3
  • From: drwho <drwho@xxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: Does Solaris 11 support GCC's init_priority?
  • From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: Does Solaris 11 support GCC's init_priority?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Does Solaris 11 support GCC's init_priority?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Which compiler pass prints a warning?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Which compiler pass prints a warning?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Which compiler pass prints a warning?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: building old gcc3 for i386-linux on recent x86-linux?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• -march=x86-64 (was: illegal instruction (CPU mismatch))
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Which compiler pass prints a warning?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• GCC v6.2.0 Testsuit - High number of unexpected failures on RHEL 5.5
  • From: Rogerio de Souza Moraes <rogerio@xxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: illegal instruction (CPU mismatch)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• illegal instruction (CPU mismatch)
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Sascha Frick <frick@xxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• RE: Compiling soft-fp in libgcc
  • From: "Marc BALEMBOY" <marc.balemboy@xxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Sascha Frick <frick@xxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Sascha Frick <frick@xxxxxx>
• Re: ARC Arctangent A4 toolchain
  • From: Mason <slash.tmp@xxxxxxx>
• ARC Arctangent A4 toolchain
  • From: Daniel Genin <dan.genin@xxxxxxxxx>
• Re: Problem with -m64 on Solaris 11
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Problem with -m64 on Solaris 11
  • From: Sascha Frick <frick@xxxxxx>
• Creating builtins or using the inliner in a GCC plugin
  • From: Evgenii Shatokhin <eugene.shatokhin@xxxxxxxxx>
• Re: -fcode-hoisting in GCC 6.2
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: -fcode-hoisting in GCC 6.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• about kernel configuration CONFIG_CPU_ARM_CORTEX_A15
  • From: yoma sophian <sophian.yoma@xxxxxxxxx>
• Re: -fcode-hoisting in GCC 6.2
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• -fcode-hoisting in GCC 6.2
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Atomics and lock free
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: torque install ubuntu elision broadwell
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Atomics and lock free
  • From: Kurt Roeckx <kurt@xxxxxxxxx>
• Re: Atomics and lock free
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Atomics and lock free
  • From: Kurt Roeckx <kurt@xxxxxxxxx>
• torque install ubuntu elision broadwell
  • From: andrealphus <andrealphus@xxxxxxxxx>
• Re: Configuring a cross compile with --with_sysroot
  • From: Michiel Bacchiani <michiel.bacchiani@xxxxxxxxx>
• Configuring a cross compile with --with_sysroot
  • From: Michiel Bacchiani <michiel.bacchiani@xxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• Compiling soft-fp in libgcc
  • From: "Marc BALEMBOY" <marc.balemboy@xxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Use q modifier for XMM portion of an YMM register?
  • From: Adam Warner <lists@xxxxxxxxxxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• Re: Fw: Possible missed optimization opportunity with const?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Fw: Possible missed optimization opportunity with const?
  • From: Toshi Morita <tm314159@xxxxxxxxx>
• ELF symbol visibility vs. member function template instantiations
  • From: "Schneider, Robert" <robert.schneider03@xxxxxxx>
• Re: GCC 6.1 build fails with offloading support
  • From: Vikram Singh <vikramsingh001@xxxxxxxxx>
• GCC 4.9.x build bootstrap comparison differences
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: request forum post removal
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: request forum post removal
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• request forum post removal
  • From: "jjolic@xxxxxxxxxxxxxx" <jjolic@xxxxxxxxxxxxxx>
• Re: fixincludes and package updates
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• Re: building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• fixincludes and package updates
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re:Cross compiled GCC wrongly builds dynamic executables
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxxx>
• Re: Re: Re: GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: bootstrap gcc for i686-linux-gnu on x86_64 host
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bootstrap gcc for i686-linux-gnu on x86_64 host
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• bootstrap gcc for i686-linux-gnu on x86_64 host
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: Re: Re: GCC ICE bug with segfault...
  • From: "lhmouse"<lh_mouse@xxxxxxx>
• Re: Re: GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Re: GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• RE: building gcc for mipsel
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• Re: How to migrate codebase to C++11
  • From: Tamás Kiss <tkiss80@xxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: How to migrate codebase to C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to migrate codebase to C++11
  • From: Tamás Kiss <tkiss80@xxxxxxxxx>
• Re: Cross compiled GCC wrongly builds dynamic executables
  • From: "H.J. Lu" <hjl.tools@xxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• Re: building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building gcc for mipsel
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• building gcc for mipsel
  • From: Peter Münster <pmlists@xxxxxxx>
• Re: Re: GCC ICE bug with segfault...
  • From: "lhmouse"<lh_mouse@xxxxxxx>
• Re: How to migrate codebase to C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• How to migrate codebase to C++11
  • From: Tamás Kiss <tkiss80@xxxxxxxxx>
• Re: ./configure --with-dwarf3
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: man-page code doesn't compile with `-std=c99'
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• man-page code doesn't compile with `-std=c99'
  • From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC ICE bug with segfault...
  • From: "lhmouse"<lh_mouse@xxxxxxx>
• GCC ICE bug with segfault...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Cross compiled GCC wrongly builds dynamic executables
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re:Cross compiled GCC wrongly builds dynamic executables
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxxx>
• Re: Cross compiled GCC wrongly builds dynamic executables
  • From: "H.J. Lu" <hjl.tools@xxxxxxxxx>
• Cross compiled GCC wrongly builds dynamic executables
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: Re: Gcc compiler advantage and disadvantage of gcc
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Gcc compiler advantage and disadvantage of gcc
  • From: Anna Szekér <kordely@xxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: Surprisingly bad code generated near char*
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Gcc compiler advantage and disadvantage of gcc
  • From: "i.98shaikhh" <i.98shaikhh@xxxxxxxxx>
• Surprisingly bad code generated near char*
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: struct member alignment
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: Cross-compiler for multiple hosts in one installation?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• struct member alignment
  • From: Manfred <mx2927@xxxxxxxxx>
• Re: [Buildroot] bfin c++ problem
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Cross-compiler for multiple hosts in one installation?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• static linking + nostartfiles + exceptions
  • From: d wk <dwksrc@xxxxxxxxx>
• Re: [Buildroot] bfin c++ problem
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• ./configure --with-dwarf3
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• GCC 6.1 build fails with offloading support
  • From: Vikram Singh <vikramsingh001@xxxxxxxxx>
• application frequently map and unmap memory
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Compilation errors with gcc4.9 and c++1y
  • From: madana gopal <madanagopal123@xxxxxxxxx>
• Re: Compilation errors with gcc4.9 and c++1y
  • From: madana gopal <madanagopal123@xxxxxxxxx>
• Re: Compilation errors with gcc4.9 and c++1y
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compilation errors with gcc4.9 and c++1y
  • From: madana gopal <madanagopal123@xxxxxxxxx>
• Re: Compilation errors with gcc4.9 and c++1y
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compilation errors with gcc4.9 and c++1y
  • From: madana gopal <madanagopal123@xxxxxxxxx>
• Re: How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to clear compile error when using rdrand64_step due to typedef'ing a 64-bit type?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• diag colors
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: vmull_p64 failed to compile on armv8
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• vmull_p64 failed to compile on armv8
  • From: Lincoln Thurlow <lthurlow@xxxxxxxx>
• openmp 4.5 and fortran
  • From: Alin M Elena <alinm.elena@xxxxxxxxx>
• Re: Minimun system configuration for GNU comiler collection installation
  • From: Tim Prince <n8tm@xxxxxxx>
• Minimun system configuration for GNU comiler collection installation
  • From: Suzane de Alencar Chaves <suzane.chaves@xxxxxxxxxxx>
• Re: Enable crc32 for armv7?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Enable crc32 for armv7?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Enable crc32 for armv7?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Roger Pack <rogerdpack2@xxxxxxxxx>
• Re: Problems building gcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Problems building gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problems building gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Problems building gcc
  • From: Douglas Houston <dhouston@xxxxxxxxxxxxxxxxxx>
• Enable crc32 for armv7?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Roger Pack <rogerdpack2@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: unclear instructions on how to subscribe to gcc help?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Roger Pack <rogerdpack2@xxxxxxxxx>
• unclear instructions on how to subscribe to gcc help?
  • From: Roger Pack <rogerdpack2@xxxxxxxxx>
• Re: [Buildroot] bfin c++ problem
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• RE: symbian support in gcc
  • From: fedor_qd@xxxxxxx
• Re: symbian support in gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• symbian support in gcc
  • From: fedor_qd@xxxxxxx
• int main(void) pedantry [Was Re: bfin c++ problem]
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bfin c++ problem
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: bfin c++ problem
  • From: Oliver Kullmann <o.kullmann@xxxxxxxxxxxxx>
• Re: bfin c++ problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bfin c++ problem
  • From: Oliver Kullmann <o.kullmann@xxxxxxxxxxxxx>
• Re: bfin c++ problem
  • From: Oliver Kullmann <o.kullmann@xxxxxxxxxxxxx>
• Re: bfin c++ problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bfin c++ problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bfin c++ problem
  • From: Oliver Kullmann <o.kullmann@xxxxxxxxxxxxx>
• Re: bfin c++ problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bfin c++ problem
  • From: Oliver Kullmann <o.kullmann@xxxxxxxxxxxxx>
• bfin c++ problem
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Fwd: Building GCC 7.0 with gpu offloading
  • From: "Kitchen, Ryan Scott" <kitchenr@xxxxxxxxxxxxxxx>
• Re: Check for command line option in my header file
  • From: greg7mdp <greg7mdp@xxxxxxxxx>
• Re: Check for command line option in my header file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Check for command line option in my header file
  • From: greg7mdp <greg7mdp@xxxxxxxxx>
• RE: Check for command line option in my header file
  • From: greg7mdp <greg7mdp@xxxxxxxxx>
• Re: Check for command line option in my header file
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Check for command line option in my header file
  • From: greg7mdp <greg7mdp@xxxxxxxxx>
• Re: Check for command line option in my header file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Check for command line option in my header file
  • From: greg7mdp <greg7mdp@xxxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: David Abdurachmanov <david.abdurachmanov@xxxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -march=<name of native> doesn't seem to set flags -march=native does?
  • From: Roger Pack <rogerdpack2@xxxxxxxxx>
• Re: SPR access
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: SPR access
  • From: tutruong0412@xxxxxxxxx
• Re: GCC 5.3.0 Make install fails
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.3.0 Make install fails
  • From: Glenn Wolosh <gwolosh@xxxxxxxx>
• Re: GCC 5.3.0 Make install fails
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.3.0 Make install fails
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC 5.3.0 Make install fails
  • From: Gedaliah Wolosh <gwolosh@xxxxxxxx>
• Re: GCC++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: what does -fno-pic do
  • From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
• Re: what does -fno-pic do
  • From: Mason <slash.tmp@xxxxxxx>
• Re: what does -fno-pic do
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: what does -fno-pic do
  • From: Mason <slash.tmp@xxxxxxx>
• Re: what does -fno-pic do
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Re: Re: gcc-6.1, cstdlib, fatal error: stdlib.h: No such file or directory
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• what does -fno-pic do
  • From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
• Re: gcc-6.1, cstdlib, fatal error: stdlib.h: No such file or directory
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: gcc-6.1, cstdlib, fatal error: stdlib.h: No such file or directory
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• gcc-6.1, cstdlib, fatal error: stdlib.h: No such file or directory
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• SPR access
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: question about illegal utf-8 encoding in string literals
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• question about illegal utf-8 encoding in string literals
  • From: "Blower, Melanie" <melanie.blower@xxxxxxxxx>
• Disable coalesce sections when using GCC with -Wa,-q and Clang integrated assembler?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Vintage AT&T 3B
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Vintage AT&T 3B
  • From: Steven Starkes <starkes@xxxxxxxxxxxxx>
• Re: strtold("inf",NULL) returns a NaN
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Re: strtold("inf",NULL) returns a NaN
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• strtold("inf",NULL) returns a NaN
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Re: Where do number suffixes in symbol names come from?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: Where do number suffixes in symbol names come from?
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Where do number suffixes in symbol names come from?
  • From: john smith <wempwer@xxxxxxxxx>
• Re: Where do number suffixes in symbol names come from?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Where do number suffixes in symbol names come from?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Where do number suffixes in symbol names come from?
  • From: john smith <wempwer@xxxxxxxxx>
• -static-libstdc++ on OSX
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: static declaration follows non-static one
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: static declaration follows non-static one
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: static declaration follows non-static one
  • From: Martin Sebor <msebor@xxxxxxxxx>
• gcov apis are hidden in libgcov.a of arm-none-eabi
  • From: Ben vin <benvinkorea@xxxxxxxxx>
• Re: static declaration follows non-static one
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• static declaration follows non-static one
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: How to test Aarch32 execution environment on Aarch64?
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• How to test Aarch32 execution environment on Aarch64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: gcc 6.1 generates movaps for unaligned memory
  • From: Justus Schwartz <justus@xxxxxx>
• Re: gcc 6.1 generates movaps for unaligned memory
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• gcc 6.1 generates movaps for unaligned memory
  • From: Justus Schwartz <justus@xxxxxx>
• Re: Running C++11 shared library with older gcc, libc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: double and float in GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Running C++11 shared library with older gcc, libc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Running C++11 shared library with older gcc, libc
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Running C++11 shared library with older gcc, libc
  • From: Dinesh Pathak <dinesh.pathak@xxxxxxxxx>
• Re: Running C++11 shared library with older gcc, libc
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Running C++11 shared library with older gcc, libc
  • From: Dinesh Pathak <dinesh.pathak@xxxxxxxxx>
• double and float in GCC
  • From: Kondi <konrad.p.wojciechowski@xxxxxxxxx>
• Re: gcc testsuite not marking stabs tests as unsupported
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: frame_pointer_needed always true ?
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: How do I tell GCC that a global variable is immutable after initialization?
  • From: Mason <slash.tmp@xxxxxxx>
• How do I tell GCC that a global variable is immutable after initialization?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• [OpenACC] Performance issues on simple example program
  • From: Christopher Guckes <chris@xxxxxxxxxxxxxxxxxxx>
• Re: gmp.h not found, even though sources are found
  • From: Eric Neblock <c_eric@xxxxxxxxxxxxx>
• gcc: alternate activation records
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: gcc testsuite not marking stabs tests as unsupported
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: gcc testsuite not marking stabs tests as unsupported
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Question about -ftree-* optimizations in -O1
  • From: Jeff Law <law@xxxxxxxxxx>
• gcc testsuite not marking stabs tests as unsupported
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Re: gmp.h not found, even though sources are found
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: defects in gcc, please fix, thanks
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: defects in gcc, please fix, thanks
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: permission
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Identifying declared but unreferenced global variables from a plugin
  • From: "Bertram, Alexander" <alex@xxxxxxxxxxxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Re: Confusing error for incorrect struct initialization
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Re: Confusing error for incorrect struct initialization
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: permission
  • From: Libin Dang <libin.dang@xxxxxxxxxxxxx>
• defects in gcc, please fix, thanks
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• permission
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: Confusing error for incorrect struct initialization
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Confusing error for incorrect struct initialization
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Question about -ftree-* optimizations in -O1
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Identifying declared but unreferenced global variables from a plugin
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• gmp.h not found, even though sources are found
  • From: Eric Neblock <c_eric@xxxxxxxxxxxxx>
• Re: Identifying declared but unreferenced global variables from a plugin
  • From: "Bertram, Alexander" <alex@xxxxxxxxxxxxxxxx>
• Re: Identifying declared but unreferenced global variables from a plugin
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Identifying declared but unreferenced global variables from a plugin
  • From: "Bertram, Alexander" <alex@xxxxxxxxxxxxxxxx>
• Re: Question about -ftree-* optimizations in -O1
  • From: Libin Dang <libin.dang@xxxxxxxxxxxxx>
• Question about -ftree-* optimizations in -O1
  • From: Jiaqi Tan <jiaqi.tan@xxxxxxxxx>
• Re: Cross-compiled GCC 6.1.0 has "../lib" instead of "/usr/lib" in -print-search-dirs output
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxx>
• RE: Cross-compiled GCC 6.1.0 has "../lib" instead of "/usr/lib" in -print-search-dirs output
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Re: Cross-compiled GCC 6.1.0 has "../lib" instead of "/usr/lib" in -print-search-dirs output
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxx>
• Re: Bogus unresolved references to vtable when building with lto
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: bug in gcc
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Bogus unresolved references to vtable when building with lto
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Bogus unresolved references to vtable when building with lto
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: bug in gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: bug in gcc
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Bug in template parsing?
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Re: Bug in template parsing?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Bug in template parsing?
  • From: Marcel Keller <M.Keller@xxxxxxxxxxxxx>
• Re: bug in gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• bug in gcc
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• RE: Cross-compiled GCC 6.1.0 has "../lib" instead of "/usr/lib" in -print-search-dirs output
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Cross-compiled GCC 6.1.0 has "../lib" instead of "/usr/lib" in -print-search-dirs output
  • From: Alastair Hughes <hobbitalastair@xxxxxxxxx>
• frame_pointer_needed always true ?
  • From: Aurélien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• RE: Build Error: cannot compute suffix of object files
  • From: Bernd Edlinger <bernd.edlinger@xxxxxxxxxx>
• Re: Historic C++ ABI question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Does GCC 4.4.0 need MPC ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Is it possible to compile gcc-4.4.0 using gcc-4.2.4
  • From: Jeff Law <law@xxxxxxxxxx>
• gcc 6.1.0 emits call to __sync_synchronize
  • From: fedor_qd <fedor_qd@xxxxxxx>
• Is it possible to compile gcc-4.4.0 using gcc-4.2.4
  • From: Sreyan Chakravarty <sreyan.mailing@xxxxxxxxx>
• Does GCC 4.4.0 need MPC ?
  • From: Sreyan Chakravarty <sreyan.mailing@xxxxxxxxx>
• Re: GCC 6.1 compilation fails on CentOS 7.2 - conflicting/ambiguous definitions
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: GCC 6.1 compilation fails on CentOS 7.2 - conflicting/ambiguous definitions
  • From: "Daniel Greenidge" <cdg4@xxxxxxxxxxxxx>
• Build Error: cannot compute suffix of object files
  • From: Sreyan Chakravarty <sreyan.mailing@xxxxxxxxx>
• GCC 6.1 compilation fails on CentOS 7.2 - conflicting/ambiguous definitions
  • From: Daniel Greenidge <cdg4@xxxxxxxxxxxxx>
• Re: arm-none-eabi-gcc 5.3 and LTO, mixing ARM and Thumb instructions
  • From: Christian Bruel <christian.bruel@xxxxxx>
• Re: arm-none-eabi-gcc 5.3 and LTO, mixing ARM and Thumb instructions
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• arm-none-eabi-gcc 5.3 and LTO, mixing ARM and Thumb instructions
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• Re: Historic C++ ABI question
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Historic C++ ABI question
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• AW: float behaivior on ARMv8-A
  • From: N30dG <christian.dreihsig@xxxxxxxxxxx>
• Re: As-if Rule (was: ARMv8, GCC 4.9 and necessary code optimized away)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: LTO + Function Multi Versioning bug
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: As-if Rule (was: ARMv8, GCC 4.9 and necessary code optimized away)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: As-if Rule (was: ARMv8, GCC 4.9 and necessary code optimized away)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• As-if Rule (was: ARMv8, GCC 4.9 and necessary code optimized away)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Trying to understand how libgomp implements the task construct
  • From: Olumide <50295@xxxxxx>
• undefined reference to `__sync_synchronize'
  • From: fedor_qd <fedor_qd@xxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Using __attribute__((target("arm"))) on ARM cross compiler: warning: target attribute is not supported on this machine [-Wattributes]
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• Re: Using __attribute__((target("arm"))) on ARM cross compiler: warning: target attribute is not supported on this machine [-Wattributes]
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• Re: LTO + Function Multi Versioning bug
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Using __attribute__((target("arm"))) on ARM cross compiler: warning: target attribute is not supported on this machine [-Wattributes]
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• Using __attribute__((target("arm"))) on ARM cross compiler: warning: target attribute is not supported on this machine [-Wattributes]
  • From: Gabriel Marcano <gabemarcano@xxxxxxxxx>
• LTO + Function Multi Versioning bug
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• ARMv8, GCC 4.9 and necessary code optimized away?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: float behaivior on ARMv8-A
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <chengang@xxxxxxxxxxxxxxxx>
• Re: float behaivior on ARMv8-A
  • From: N30dG <christian.dreihsig@xxxxxxxxxxx>
• RE: gnu toolchain: x64 host executables
  • From: fedor_qd@xxxxxxx
• Re: gnu toolchain: x64 host executables
  • From: Mason <slash.tmp@xxxxxxx>
• Re: GCC Spec file for ARMv8/Aarch64?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: gcc 6.1.0 bogus placement new warning
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: gcc 6.1.0 bogus placement new warning
  • From: Jason Mancini <Jason.Mancini@xxxxxxx>
• gcc 6.1.0 bogus placement new warning
  • From: Jason Mancini <Jason.Mancini@xxxxxxx>
• Re: GCC Spec file for ARMv8/Aarch64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC Spec file for ARMv8/Aarch64?
  • From: James Greenhalgh <james.greenhalgh@xxxxxxx>
• RE: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: "Joseph, Matthew" <matthew.joseph@xxxxxxxx>
• RE: gnu toolchain: x64 host executables
  • From: fedor_qd@xxxxxxx
• Re: gnu toolchain: x64 host executables
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gnu toolchain: x64 host executables
  • From: fedor_qd@xxxxxxx
• Building gnat-6.1 for arm-rtems fails with '"Kill" is undefined'
  • From: Jan Sommer <soja-lists@xxxxxxxxxxxxxxxxxx>
• Re: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: "Joseph, Matthew" <matthew.joseph@xxxxxxxx>
• Re: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: "Joseph, Matthew" <matthew.joseph@xxxxxxxx>
• Re: GCC 4.1.1 Solaris 10 installation
  • From: Tim Prince <n8tm@xxxxxxx>
• RE: EXTERNAL: Re: GCC 4.1.1 Solaris 10 installation
  • From: "Joseph, Matthew" <matthew.joseph@xxxxxxxx>
• Re: GCC 4.1.1 Solaris 10 installation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC 4.1.1 Solaris 10 installation
  • From: "Joseph, Matthew" <matthew.joseph@xxxxxxxx>
• Code generation for condition of C branch statement
  • From: Леонид Круглов <1kruglovleonid1@xxxxxxx>
• Re: Needed help to build gcc cross compiler for powerpc-linux
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Optimize based on possible enum class values?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Adding new builtin function to gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Adding new builtin function to gcc
  • From: Ons Boutiti <ons.boutiti@xxxxxxxxx>
• Re: GCC Spec file for ARMv8/Aarch64?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Needed help to build gcc cross compiler for powerpc-linux
  • From: "promila.jangra" <promila.jangra@xxxxxxx>
• Re: GCC Spec file for ARMv8/Aarch64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Needed help to resolve Binutils Build problem
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Needed help to resolve Binutils Build problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Needed help to resolve Binutils Build problem
  • From: "promila.jangra" <promila.jangra@xxxxxxx>
• Re: Optimize based on possible enum class values?
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Re: Optimize based on possible enum class values?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• GCC Spec file for ARMv8/Aarch64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Optimize based on possible enum class values?
  • From: "lh mouse"<lh_mouse@xxxxxxx>
• Optimize based on possible enum class values?
  • From: ☂Josh Chia (谢任中) <joshchia@xxxxxxxxx>
• Re: -fsanitize=undefined in a freestanding environment
  • From: "Zdenek Sojka" <zsojka@xxxxxxxxx>
• -fsanitize=undefined in a freestanding environment
  • From: "Zdenek Sojka" <zsojka@xxxxxxxxx>
• Re: I want to get all of compile error message list of gcc about C language.
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Tom Udale <tom@xxxxxxxxxxxx>
• Re: I want to get all of compile error message list of gcc about C language.
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: I want to get all of compile error message list of gcc about C language.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• I want to get all of compile error message list of gcc about C language.
  • From: 유한솔 <yhs1203@xxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Tom Udale <tom@xxxxxxxxxxxx>
• Re: Unable to access gcc svn.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• C++ test program with SJLJ exception crash
  • From: SpaceClown <flyingfriendly@xxxxxxxxx>
• NEON and instruct GCC to move a lane without using a regular register?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unable to access gcc svn.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Unable to access gcc svn.
  • From: Ed Smith-Rowland <3dw4rd@xxxxxxxxxxx>
• WRF metgrid.exe : Note: The following floating-point exceptions are signalling: IEEE_OVERFLOW_FLAG IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
  • From: arindam ghosh <arindamgr@xxxxxxxxx>
• Re: classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: GCC git mirror down?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC git mirror down?
  • From: Fritz Reese <fritzoreese@xxxxxxxxx>
• Re: ARM NEON Intrinsics guide?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: ARM NEON Intrinsics guide?
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• Re: ARM NEON Intrinsics guide?
  • From: Mason <slash.tmp@xxxxxxx>
• ARM NEON Intrinsics guide?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Tom Udale <tom@xxxxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Tom Udale <tom@xxxxxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: extract platform source from a multi-platform package
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: asm volatile("":::"memory) uncertainty.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• extract platform source from a multi-platform package
  • From: David Bradley <kb9qhd@xxxxxxxxxxx>
• asm volatile("":::"memory) uncertainty.
  • From: Tom Udale <tom@xxxxxxxxxxxx>
• Re: how to access the online manuals?
  • From: "Carol LePage" <clepage@xxxxxxxxxxxxxx>
• include-fixed/limits.h does not include_next? (PATH_MAX errors)
  • From: Michael Habibi <mikehabibi@xxxxxxxxx>
• Re: istringstream.rdbuf with custom streambuf does not compile
  • From: 杨岑 <ssawgift@xxxxxxx>
• Re: istringstream.rdbuf with custom streambuf does not compile
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: how to access the online manuals?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re: istringstream.rdbuf with custom streambuf does not compile
  • From: "lh_mouse"<lh_mouse@xxxxxxx>
• Re: istringstream.rdbuf with custom streambuf does not compile
  • From: 杨岑 <ssawgift@xxxxxxx>
• Re: istringstream.rdbuf with custom streambuf does not compile
  • From: "lh_mouse"<lh_mouse@xxxxxxx>
• istringstream.rdbuf with custom streambuf does not compile
  • From: 杨春雷 <ssawgift@xxxxxxx>
• Re: how to access the online manuals?
  • From: carol lepage <clepage@xxxxxxxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Pip Cet <pipcet@xxxxxxxxx>
• Re: why these errors?
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: Re: Errors building mozilla thunderbird 38.7.0 with gcc 6
  • From: "lh_mouse"<lh_mouse@xxxxxxx>
• Re: Errors building mozilla thunderbird 38.7.0 with gcc 6
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• Re: Errors building mozilla thunderbird 38.7.0 with gcc 6
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Errors building mozilla thunderbird 38.7.0 with gcc 6
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Errors building mozilla thunderbird 38.7.0 with gcc 6
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Michael Habibi <mikehabibi@xxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Michael Habibi <mikehabibi@xxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Michael Habibi <mikehabibi@xxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Standardized instructions for cross-compiling toolchain?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Standardized instructions for cross-compiling toolchain?
  • From: Michael Habibi <mikehabibi@xxxxxxxxx>
• Re: lto optimization
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: lto optimization
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: lto optimization
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• lto optimization
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: float behaivior on ARMv8-A
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: float behaivior on ARMv8-A
  • From: N30dG <christian.dreihsig@xxxxxxxxxxx>
• Re: LDD4 expected release date
  • From: Mason <slash.tmp@xxxxxxx>
• Re: a little help beginning (kernel module)
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: a little help beginning (kernel module)
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: a little help beginning (kernel module)
  • From: Xen <list@xxxxxxxxxxxxx>
• a little help beginning (kernel module)
  • From: Xen <list@xxxxxxxxxxxxx>
• Re: float behaivior on ARMv8-A
  • From: Andrew Haley <aph@xxxxxxxxxx>
• classpath/tools/tools.zip:0:0: fatal error: not a valid Java .class file
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: option -mprfchw
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: mpfr / gmp dependency
  • From: NightStrike <nightstrike@xxxxxxxxx>
• float behaivior on ARMv8-A
  • From: N30dG <christian.dreihsig@xxxxxxxxxxx>
• Re: option -mprfchw
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Hard-coded C++ paths and reloation problem on Windows
  • From: "lh_mouse"<lh_mouse@xxxxxxx>
• Re: m68k toolchain
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: m68k toolchain
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: m68k toolchain
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: OpenACC offload to nvptx
  • From: Salvatore Filippone <filippone.salvatore@xxxxxxxxx>
• Re: Detect whether we have a native 64-bit type?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: OpenACC offload to nvptx
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: Detect whether we have a native 64-bit type?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Detect whether we have a native 64-bit type?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: SIGBUS Bus error on sparc64
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Re: SIGBUS Bus error on sparc64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-6.1: no source files...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• OpenACC parallel directives fail to run, libgomp error
  • From: stuberl@xxxxxxxxxxx
• Re: SIGBUS Bus error on sparc64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc-6.1: no source files...
  • From: Branko <brankob@xxxxxxxxxxxxx>
• SIGBUS Bus error on sparc64
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• OpenACC offload to nvptx
  • From: Salvatore Filippone <filippone.salvatore@xxxxxxxxx>
• Detect whether we have a native 64-bit type?
  • From: Jonathan Lennox <jonathan@xxxxxxxxx>
• error compiling gcc 5.3.0 on Red Hat Linux 6
  • From: Irena Johnson <ijohnson@xxxxxxxx>
• Re: Recipe Issue, I don't understand what the fault is
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Recipe Issue, I don't understand what the fault is
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: Recipe Issue, I don't understand what the fault is
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Recipe Issue, I don't understand what the fault is
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: mpfr / gmp dependency
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: option -mprfchw
  • From: NightStrike <nightstrike@xxxxxxxxx>
• mpfr / gmp dependency
  • From: NightStrike <nightstrike@xxxxxxxxx>
• RE: Unexpected MIPS assembly output
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Unexpected MIPS assembly output
  • From: Nathan Cole <nath@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Can someone explain why this code outputs 7 ? （Is this a gcc bug?)
  • From: Manfred <mx2927@xxxxxxxxx>
• Re: m68k toolchain
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Can someone explain why this code outputs 7 ? （Is this a gcc bug?)
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• phase -> phrase
  • From: <chen@xxxxxxxxxxxxxxxxxxxxxxx>
• Can someone explain why this code outputs 7 ? （Is this a gcc bug?)
  • From: <chen@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: m68k toolchain
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Insert debugging symbol using GIMPLE
  • From: "dw.dev" <dw.dev.mailing@xxxxxxxxx>
• bootstrap comparison failures on SPARC/Solaris 10
  • From: Mikael Pettersson <mikpelinux@xxxxxxxxx>
• Re: m68k toolchain
  • From: Jeff Law <law@xxxxxxxxxx>
• 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: Kevin Abbey <kevin.abbey@xxxxxxxxxxx>
• Re: Unclear explanation for some builtins
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Unclear explanation for some builtins
  • From: Eyal Rozenberg <eyalroz@xxxxxxxxxxxxxx>
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Cary Coutant <ccoutant@xxxxxxxxx>
• Re: why these errors?
  • From: Barry Gold <barrydgold@xxxxxxxxx>
• Re: why these errors?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: why these errors?
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: why these errors?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: feature request
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: why doesn't "namespace str" insulate me from stuff in algo.h?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: features add request, bug in 6.0.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Ivan Shapovalov <intelfx@xxxxxxxxxxxx>
• Re: why these errors?
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: feature request
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: features add request, bug in 6.0.0
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• why doesn't "namespace str" insulate me from stuff in algo.h?
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: why these errors?
  • From: Andrew Melo <andrew.melo@xxxxxxxxx>
• why these errors?
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Cary Coutant <ccoutant@xxxxxxxxx>
• Re: feature request
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: features add request, bug in 6.0.0
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• feature request
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• features add request, bug in 6.0.0
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: missing things in c++/gcc
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: missing things in c++/gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Ivan Shapovalov <intelfx@xxxxxxxxxxxx>
• missing things in c++/gcc
  • From: Jim Michaels <jim.michaels@xxxxxxxxxxxxx>
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Cary Coutant <ccoutant@xxxxxxxxx>
• Re: option -mprfchw
  • From: NightStrike <nightstrike@xxxxxxxxx>
• option -mprfchw
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Variable access optimization
  • From: Ángel González <keisial@xxxxxxxxx>
• Variable access optimization
  • From: "Sivanupandi, Pitchumani" <Pitchumani.Sivanupandi@xxxxxxxxx>
• Re: C++ version 11 "auto"
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: C++ version 11 "auto"
  • From: Daniël Bos <corani@xxxxxxxxx>
• C++ version 11 "auto"
  • From: Barry Gold <barrydgold@xxxxxxxxx>
• AW: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• Re: Problems installing GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Problems installing GCC
  • From: Hassan Haddouchi <hhaddouc@xxxxxxxxx>
• Building GCC 5.3.0 with 4.8.2
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Ivan Shapovalov <intelfx@xxxxxxxxxxxx>
• --sysroot selecting system directories!?
  • From: jtc@xxxxxxxxxxxxxxxxxx (J.T. Conklin)
• Re: Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Cary Coutant <ccoutant@xxxxxxxxx>
• Segfault calling dlopen()'ed executable built with -pie and using TLS
  • From: Ivan Shapovalov <intelfx@xxxxxxxxxxxx>
• Re: Issue with templates and asm register constraints
  • From: Andreas Krebbel <krebbel@xxxxxxxxxxxxxxxxxx>
• Re: -fstack-protector and STL string
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Reserve space in stack
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Reserve space in stack
  • From: "sztfg@xxxxxxxxx" <sztfg@xxxxxxxxx>
• Re: -fstack-protector and STL string
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Reserve space in stack
  • From: Florian Weimer <fweimer@xxxxxxxxxx>