GCC Help
[Prev Page][Next Page]
- Re: Need help debugging likely g++ preprocessor bug
- From: Mike Gulick <mike.gulick@xxxxxxxxxxxxx>
- Re: How to avoid code elimination
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: How to avoid code elimination
- From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
- Re: How to avoid code elimination
- From: phi gcc <phi.gcc@xxxxxxxxx>
- How to avoid code elimination
- From: phi gcc <phi.gcc@xxxxxxxxx>
- Unable to load libgnat-4.4 in runtime
- From: Marco Bevi <bevi.marco.16@xxxxxxxxx>
- Re: Regarding the Linking issue in GCC for Lib.
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Need help debugging likely g++ preprocessor bug
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Regarding the Linking issue in GCC for Lib.
- From: "Banaja Pattanaik via gcc-help" <gcc-help@xxxxxxxxxxx>
- Need help debugging likely g++ preprocessor bug
- From: Mike Gulick <mike.gulick@xxxxxxxxxxxxx>
- Looking for the standard way to build a standalone gcc+glibc+binutils toolchain at Linux
- From: Rostislav Krasny <rosti.bsd@xxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: Jeff Law <law@xxxxxxxxxx>
- Re: The question about using OpenMP taskloop feature in gcc
- From: Nan Xiao <xiaonan830818@xxxxxxxxx>
- Re: The question about using OpenMP taskloop feature in gcc
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: The question about using OpenMP taskloop feature in gcc
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- The question about using OpenMP taskloop feature in gcc
- From: Nan Xiao <xiaonan830818@xxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
- Re: futurist.co.in
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: Jeff Law <law@xxxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: mark.reinhold@xxxxxxxxxx
- futurist.co.in
- From: "bf@xxxxxxx" <bf@xxxxxxx>
- -finstrument-functions-exclude-file-list=include,boost causes segment fault
- From: liang tang <liangtang20080522@xxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: GCC policy on deprecating and removing targets
- From: Jeff Law <law@xxxxxxxxxx>
- GCC policy on deprecating and removing targets
- From: mark.reinhold@xxxxxxxxxx
- Re: Power of two rehash policy
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Power of two rehash policy
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Power of two rehash policy
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Power of two rehash policy
- From: Jason Arnold <jasonar81@xxxxxxxxx>
- Re: Again Boost linking error
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Again Boost linking error
- From: "Mahmood Naderan via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Bug in std::floor?
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: Bug in std::floor?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Bug in std::floor?
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: Bug in std::floor?
- From: Mason <slash.tmp@xxxxxxx>
- Re: Disable calling convention optimization for local functions
- From: Satyam Sharma <satyam.sharma@xxxxxxxxx>
- Re: Disable calling convention optimization for local functions
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Fwd: Relocation R_X86_64_32 against undefined symbol
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Fwd: Relocation R_X86_64_32 against undefined symbol
- From: Himanshu Chauhan <hchauhan@xxxxxxxxxxxxxx>
- Re: Cross compilation
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Cross compilation
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Disable calling convention optimization for local functions
- From: Satyam Sharma <satyam.sharma@xxxxxxxxx>
- Re: Cross compilation
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: Bug in std::floor?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Cross compilation
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: Bug in std::floor?
- From: Marc Glisse <marc.glisse@xxxxxxxx>
- Re: Bug in std::floor?
- From: Nil Geisweiller <ngeiswei@xxxxxxxxxxxxxx>
- Cross compilation
- From: RAVI DEWANGAN <dewangan.ravi@xxxxxxxxx>
- Re: Why is -Wold-style-definition off by default?
- From: Antons Suspans <antox@xxxxx>
- Re: Bug in std::floor?
- From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
- Re: Bug in std::floor?
- From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: "Jonny H via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Bug in std::floor?
- From: Mason <slash.tmp@xxxxxxx>
- Re: --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: Bug in std::floor?
- From: Jonathan Wakely <jwakely@xxxxxxxxxx>
- --target=powerpc-eabi: error: static declaration of ‘strndup’ follows non-static declaration
- From: "Jonny H via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
- Using GCC to compile C and Python Code to one Executable
- From: robertdaleweir <robertdaleweir@xxxxxxxxx>
- Using GCC to compile C and Python Code to one Executable
- From: robertdaleweir <robertdaleweir@xxxxxxxxx>
- Re: will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
- Re: will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: 陳韋任 <chenwj.cs97g@xxxxxxxxxxxxxx>
- will __attribute__((aligned(CACHE_LINE_SIZE))) break struct alignment
- From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
- Why GCC needs a dll image to compile my other dll?
- From: john Stone <profesor.fir@xxxxxxxxx>
- Re: std::stringstream with std::cout error
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: std::stringstream with std::cout error
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: std::stringstream with std::cout error
- From: Andrew Bell <andrew.bell.ia@xxxxxxxxx>
- std::stringstream with std::cout error
- From: "mahmood n via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: GCC Inline Assembler "memory" Clobber don't prevent from re-arrange the code in ARM .
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: GCC Inline Assembler "memory" Clobber don't prevent from re-arrange the code in ARM .
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: GCC Inline Assembler "memory" Clobber don't prevent from re-arrange the code in ARM .
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: GCC Inline Assembler "memory" Clobber don't prevent from re-arrange the code in ARM .
- From: Sergey Organov <sorganov@xxxxxxxxx>
- GCC Inline Assembler "memory" Clobber don't prevent from re-arrange the code in ARM .
- From: stephen lu <lumotuwe@xxxxxxxxx>
- Re: Why is -Wold-style-definition off by default?
- From: Martin Sebor <msebor@xxxxxxxxx>
- Creating BRIG-Files
- From: Anna Arestova <anna_arestova@xxxxxxxxxx>
- std::packaged_task crash on HPUX g++ 4.9.3
- From: Brian Groose <brian@xxxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Brian Groose <brian@xxxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
- Re: 64 bit GCC failing
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: 64 bit GCC failing
- From: vikram1729 <vsp1729@xxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Brian Groose <brian@xxxxxxxxxx>
- Re: 64 bit GCC failing
- From: Andrew Haley <aph@xxxxxxxxxx>
- Why is -Wold-style-definition off by default?
- From: Antons Suspans <antox@xxxxx>
- Re: 64 bit GCC failing
- From: vikram1729 <vsp1729@xxxxxxxxx>
- Re: g++ 5.3 AIX call_once issues
- From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
- g++ 5.3 AIX call_once issues
- From: Brian Groose <brian@xxxxxxxxxx>
- Re: pthread_cancel and C++11 redux
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: pthread_cancel and C++11 redux
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: pthread_cancel and C++11 redux
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- pthread_cancel and C++11 redux
- From: "Vuille, Martin (Martin)" <vmartin@xxxxxxxxx>
- Re: GCC support for 64 bit
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: 64 bit GCC failing
- From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
- GCC support for 64 bit
- From: vikram1729 <vsp1729@xxxxxxxxx>
- 64 bit GCC failing
- From: vikram1729 <vsp1729@xxxxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: niXman <i.nixman@xxxxxxxxxxxxx>
- RE: GCC 7.2 build bugs on Windows 8.1 and Windows 10
- From: David Gressett <DGressett@xxxxxxxxxxxxxxx>
- Re: Stack protector: Suggestions for documentation
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Stack protector: Suggestions for documentation
- From: "Martin Richtarsky" <s@xxxxxxxxxxxx>
- Re: Error in parser
- From: Martin Sebor <msebor@xxxxxxxxx>
- Error in parser
- From: Vivek <vivekrpm@xxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: sugar <aldo.zavala@xxxxxxxxx>
- trunk failure, ix86_cfun_abi() not visible at point of use
- From: Tim Prince <tprince818.tp@xxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: how to compile in one system targeting another?
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- how to compile in one system targeting another?
- From: sugar <aldo.zavala@xxxxxxxxx>
- Fwd: Segmentation fault at gcov exit
- From: Miguel Munoz <miguiman@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: Segmentation fault at gcov exit
- From: Mason <slash.tmp@xxxxxxx>
- Segmentation fault at gcov exit
- From: Miguel Munoz <miguiman@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Mason <slash.tmp@xxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: STM32, Position independent code - function pointers not in GOT?
- From: Robert Sedláček <sedlons451@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Mason <slash.tmp@xxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Mason <slash.tmp@xxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: Boost linking problem
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Boost linking problem
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Variables optimized out at -O0
- From: Ryan Johnson <scovich@xxxxxxxxx>
- Variables optimized out at -O0
- From: Ryan Johnson <scovich@xxxxxxxxx>
- Re: can't make with gcc on solaris 11.3
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Boost linking problem
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Boost linking problem
- From: "Mahmood N via gcc-help" <gcc-help@xxxxxxxxxxx>
- can't make with gcc on solaris 11.3
- From: sugar <aldo.zavala@xxxxxxxxx>
- Re: gcc for microcontroller
- From: Claudio Eterno <eterno.claudio@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- STM32, Position independent code - function pointers not in GOT?
- From: Robert Sedláček <sedlons451@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: asm volatile statement reordering
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Odd warning: array subscript is above array bounds
- From: Mason <slash.tmp@xxxxxxx>
- Re: asm volatile statement reordering
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: Bernd Edlinger <bernd.edlinger@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: asm volatile statement reordering
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- asm volatile statement reordering
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: False positive and false negative from -Wformat-truncation
- From: Jeff Law <law@xxxxxxxxxx>
- Re: False positive and false negative from -Wformat-truncation
- From: Jeff Law <law@xxxxxxxxxx>
- Re: False positive and false negative from -Wformat-truncation
- From: Martin Sebor <msebor@xxxxxxxxx>
- False positive and false negative from -Wformat-truncation
- From: Mason <slash.tmp@xxxxxxx>
- Re: Calling functions through a C function pointer questoin
- From: Mason <slash.tmp@xxxxxxx>
- Re: gcc for microcontroller
- From: Jeff Law <law@xxxxxxxxxx>
- Re: gcc for microcontroller
- From: Andrew Haley <aph@xxxxxxxxxx>
- gcc for microcontroller
- From: Claudio Eterno <eterno.claudio@xxxxxxxxx>
- Re: reinterpret_cast is not a constant expression - needed help to find solution
- From: Zygmunt Ptak <zygmuntptak@xxxxxxxxx>
- Re: Calling functions through a C function pointer questoin
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Calling functions through a C function pointer questoin
- From: "Toshi Morita via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Odd warning: array subscript is above array bounds
- From: Mason <slash.tmp@xxxxxxx>
- Re: Odd warning: array subscript is above array bounds
- From: Jeff Law <law@xxxxxxxxxx>
- Odd warning: array subscript is above array bounds
- From: Mason <slash.tmp@xxxxxxx>
- Re: GCC v6.4 and v7.2 lifecycle dates
- From: Mason <slash.tmp@xxxxxxx>
- Re: GCC v6.4 and v7.2 lifecycle dates
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- RE: GCC v6.4 and v7.2 lifecycle dates
- From: "LEE, BEN S." <ben.s.lee@xxxxxxxxxxx>
- ipad air 2
- From: mostafa shahdadi <mostafa.shahdadi@xxxxxxxxx>
- Re: Intrumenting memory accesses and internal segfault
- From: hugo brunie <hbrunie0@xxxxxxxxx>
- Fwd: Intrumenting memory accesses and internal segfault
- From: hugo brunie <hbrunie0@xxxxxxxxx>
- Fwd: FW: Query regarding initializing memory to specific byte patterns.
- From: Abhijit Verma <averma0875@xxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: nick <xerofoify@xxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Tests Still Fail with mpc/mpfr linking incorrectly
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Tests Still Fail with mpc/mpfr linking incorrectly
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Why does __builtin_ctz clear eax on amd64 targets
- From: Mason <slash.tmp@xxxxxxx>
- Re: gcc4.4 build error in centos7
- From: Mason <slash.tmp@xxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: gcc4.4 build error in centos7
- From: vyshnav <avvyshnav@xxxxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Yubin Ruan <ablacktshirt@xxxxxxxxx>
- AW: Enabling multilib still does not allow us to have soft and hard float
- From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
- Re: gcc4.4 build error in centos7
- From: vyshnav <avvyshnav@xxxxxxxxx>
- Re: Why does __builtin_ctz clear eax on amd64 targets
- From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
- Re: gcc4.4 build error in centos7
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- gcc4.4 build error in centos7
- From: vyshnav <avvyshnav@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Query regarding initializing memory to specific byte patterns.
- From: Mason <slash.tmp@xxxxxxx>
- Re: Why does __builtin_ctz clear eax on amd64 targets
- From: Mason <slash.tmp@xxxxxxx>
- Why does __builtin_ctz clear eax on amd64 targets
- From: Mason <slash.tmp@xxxxxxx>
- Enabling multilib still does not allow us to have soft and hard float
- From: Farzaneh Shalbaf <Farzaneh.Shalbaf@xxxxxxxxxxx>
- Re: reinterpret_cast is not a constant expression - needed help to find solution
- From: Zygmunt Ptak <zygmuntptak@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Query regarding initializing memory to specific byte patterns.
- From: Abhijit Gokaraju <Abhijit.Gokaraju@xxxxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: xgcc running when configured with --disable-bootstrap
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- xgcc running when configured with --disable-bootstrap
- From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: Running Tests Fails with very Minor Fix
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Running Tests Fails with very Minor Fix
- From: nick <xerofoify@xxxxxxxxx>
- Re: [RFC] x86 PTA structure is full
- From: Uros Bizjak <ubizjak@xxxxxxxxx>
- Re: How to combine LTO with symbol versioning
- From: Nikolaus Rath <Nikolaus@xxxxxxxx>
- [RFC] x86 PTA structure is full
- From: "Koval, Julia" <julia.koval@xxxxxxxxx>
- Re: I had problem about the gcc version
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- I had problem about the gcc version
- From: Chen tom <tomcp85@xxxxxxxxxxx>
- Re: GCC 7.1 Fallthrough Warning Question
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- GCC 7.1 Fallthrough Warning Question
- From: Josh <snapcore@xxxxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: could help me to fix the problem when install the gcc-7.2
- From: Mason <slash.tmp@xxxxxxx>
- could help me to fix the problem when install the gcc-7.2
- From: Chen tom <tomcp85@xxxxxxxxxxx>
- Re: Running make check with forced g++ usage
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Running make check with forced g++ usage
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: vec_lvsl is deprecated for little endian; use assignment for unaligned loads
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- RE: Running make check with forced g++ usage
- From: "Peryt, Sebastian" <sebastian.peryt@xxxxxxxxx>
- Re: Running make check with forced g++ usage
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Running make check with forced g++ usage
- From: "Peryt, Sebastian" <sebastian.peryt@xxxxxxxxx>
- Re: Missed optimization opportunity wrt load chains
- From: Mason <slash.tmp@xxxxxxx>
- How to combine LTO with symbol versioning
- From: Nikolaus Rath <Nikolaus@xxxxxxxx>
- Re: Missed optimization opportunity wrt load chains
- From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
- Re: Missed optimization opportunity wrt load chains
- From: Jeff Law <law@xxxxxxxxxx>
- Missed optimization opportunity wrt load chains
- From: Mason <slash.tmp@xxxxxxx>
- vec_lvsl is deprecated for little endian; use assignment for unaligned loads
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: C/C++ Binaries double in size for gcc-4.8.5 compared to gcc-4.4.7
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: C/C++ Binaries double in size for gcc-4.8.5 compared to gcc-4.4.7
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: C/C++ Binaries double in size for gcc-4.8.5 compared to gcc-4.4.7
- From: Mason <slash.tmp@xxxxxxx>
- Re: C/C++ Binaries double in size for gcc-4.8.5 compared to gcc-4.4.7
- From: Andrew Haley <aph@xxxxxxxxxx>
- C/C++ Binaries double in size for gcc-4.8.5 compared to gcc-4.4.7
- From: shagun <shagun.maheshwari@xxxxxxxxxx>
- Global auto target_clones in GCC6
- From: Oliver Becker <der.ole.becker@xxxxxxxxx>
- "The procedure entry point __divmoddi4 could not be located in the dynamic link library libgcc_s_dw2-1.dll"
- From: muff diver <muff.diver@xxxxxxxxx>
- Re: tm vs. std:.tm type in symbol name of std::time_put<>::put()
- From: Marc Glisse <marc.glisse@xxxxxxxx>
- Re: tm vs. std:.tm type in symbol name of std::time_put<>::put()
- From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
- Re: tm vs. std:.tm type in symbol name of std::time_put<>::put()
- From: Marc Glisse <marc.glisse@xxxxxxxx>
- Re: tm vs. std:.tm type in symbol name of std::time_put<>::put()
- From: Marc Glisse <marc.glisse@xxxxxxxx>
- tm vs. std:.tm type in symbol name of std::time_put<>::put()
- From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
- Re: gcc-7.2.0 on solaris 10 x86
- From: "Neal Elliott via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: gcc-7.2.0 on solaris 10 x86
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: gcc-7.2.0 on solaris 10 x86
- From: "Neal Elliott via gcc-help" <gcc-help@xxxxxxxxxxx>
- RE: Running individual tests from c-c++-common directory
- From: "Peryt, Sebastian" <sebastian.peryt@xxxxxxxxx>
- Re: Running individual tests from c-c++-common directory
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Are you consulting?
- From: Michael Powell <mwpowellhtx@xxxxxxxxx>
- Are you consulting?
- From: DavidWhipple@xxxxxxxxxxxxxxxxxx
- Re: gcc-7.2.0 on solaris 10 x86
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Running individual tests from c-c++-common directory
- From: "Peryt, Sebastian" <sebastian.peryt@xxxxxxxxx>
- gcc-7.2.0 on solaris 10 x86
- From: "Neal Elliott via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: Information on usage
- From: Claudio Eterno <eterno.claudio@xxxxxxxxx>
- Information on usage
- From: Claudio Eterno <eterno.claudio@xxxxxxxxx>
- Re: Using _Decimal64
- From: "A.J. Bonnema" <gbonnema@xxxxxxxxx>
- Re: Using _Decimal64
- From: Tadeus Prastowo <tadeus.prastowo@xxxxxxxx>
- Re: Using _Decimal64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Using _Decimal64
- From: "A.J. Bonnema" <gbonnema@xxxxxxxxx>
- Re: Nvptx GPU offloading using OpenMP4 and GCC 7.2
- From: Caspar van Leeuwen <caspar.vanleeuwen@xxxxxxxxxxx>
- Re: Nvptx GPU offloading using OpenMP4 and GCC 7.2
- From: Caspar van Leeuwen <caspar.vanleeuwen@xxxxxxxxxxx>
- Re: Nvptx GPU offloading using OpenMP4 and GCC 7.2
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: I try compile GCC 7.2.0 68k Version. Get errors "attempt to use poisened". GCC 4.5.0 and older compile with that files. how can this change to work ?
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Using _Decimal64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Using _Decimal64
- From: "A.J. Bonnema" <gbonnema@xxxxxxxxx>
- Nvptx GPU offloading using OpenMP4 and GCC 7.2
- From: Caspar van Leeuwen <caspar.vanleeuwen@xxxxxxxxxxx>
- Re: I try compile GCC 7.2.0 68k Version. Get errors "attempt to use poisened". GCC 4.5.0 and older compile with that files. how can this change to work ?
- From: Bernd R <nospamname@xxxxxx>
- Re: I try compile GCC 7.2.0 68k Version. Get errors "attempt to use poisened". GCC 4.5.0 and older compile with that files. how can this change to work ?
- From: Jeff Law <law@xxxxxxxxxx>
- I try compile GCC 7.2.0 68k Version. Get errors "attempt to use poisened". GCC 4.5.0 and older compile with that files. how can this change to work ?
- From: Bernd R <nospamname@xxxxxx>
- Re: Using _Decimal64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Using _Decimal64
- From: "A.J. Bonnema" <gbonnema@xxxxxxxxx>
- Re: Using _Decimal64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Using _Decimal64
- From: "A.J. Bonnema" <gbonnema@xxxxxxxxx>
- How to use Power8 vcipher with 8-bit types?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Documentation clarificiation for gcc-7
- From: L A Walsh <gcc@xxxxxxxxx>
- Re: Initializer List Ctor
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Initializer List Ctor
- From: Julius Witte <julius.witte@xxxxxxxxxxxxxxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: David Brown <david@xxxxxxxxxxxxxxx>
- Re: GCC build in 64 bit OS failure
- From: Jeff Law <law@xxxxxxxxxx>
- Re: GCC build in 64 bit OS failure
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Mason <slash.tmp@xxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Mason <slash.tmp@xxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Does GCC support Power8 extensions like vpmsum?
- From: Mason <slash.tmp@xxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Andrew Makhorin <mao@xxxxxxx>
- GCC build in 64 bit OS failure
- From: vikram1729 <vsp1729@xxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: What is this
- From: Mason <slash.tmp@xxxxxxx>
- Re: How to avoding compiling unreferenced code into .o target file
- From: kipade <kipade@xxxxxxx>
- reinterpret_cast is not a constant expression - needed help to find solution
- From: Zygmunt Ptak <zygmuntptak@xxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Andrew Makhorin <mao@xxxxxxx>
- Re: the same id in the same scope refers to different objects
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- the same id in the same scope refers to different objects
- From: Andrew Makhorin <mao@xxxxxxx>
- Re: Does GCC support Power8 extensions like vpmsum?
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- I try compile GCC 7.2.0 68k Version. Get errors "attempt to use poisened". GCC 4.5.0 and older compile with that files. how can this change to work ?
- From: Bernd R <nospamname@xxxxxx>
- Does GCC support Power8 extensions like vpmsum?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: R: Problem with linking step
- From: Andrew Haley <aph@xxxxxxxxxx>
- R: Problem with linking step
- From: Alessandro Vicini <alessandro.vicini@xxxxxxxxxx>
- Re: Problem with linking step
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- R: Problem with linking step
- From: Alessandro Vicini <alessandro.vicini@xxxxxxxxxx>
- Re: Problem with linking step
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Problem with linking step
- From: Alessandro Vicini <alessandro.vicini@xxxxxxxxxx>
- Re: LTO ltrans name mangling in GCC 4.8.2
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: LTO ltrans name mangling in GCC 4.8.2
- From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
- RE: LTO ltrans name mangling in GCC 4.8.2
- From: Lassi Niemistö <lassi.niemisto@xxxxxxxxxx>
- RE: LTO ltrans name mangling in GCC 4.8.2
- From: Lassi Niemistö <lassi.niemisto@xxxxxxxxxx>
- RE: LTO ltrans name mangling in GCC 4.8.2
- From: Lassi Niemistö <lassi.niemisto@xxxxxxxxxx>
- Re: LTO ltrans name mangling in GCC 4.8.2
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: LTO ltrans name mangling in GCC 4.8.2
- From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
- Re: LTO ltrans name mangling in GCC 4.8.2
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- LTO ltrans name mangling in GCC 4.8.2
- From: Lassi Niemistö <lassi.niemisto@xxxxxxxxxx>
- Re: How to avoding compiling unreferenced code into .o target file
- From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
- Re: How to avoding compiling unreferenced code into .o target file
- From: Andrew Haley <aph@xxxxxxxxxx>
- How to avoding compiling unreferenced code into .o target file
- From: kipade <kipade@xxxxxxx>
- Re: Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Pialy Ghosh <pink.pia@xxxxxxxxx>
- testsuite option to skip cilkplus?
- From: Tim Prince <tprince818.tp@xxxxxxxxx>
- Re: First time help with gcc compile and install.
- From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
- Re: First time help with gcc compile and install.
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- First time help with gcc compile and install.
- From: Chris Kirsten <krakkeroe@xxxxxxxxx>
- Re: Error in Section 2.2
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Martin Sebor <msebor@xxxxxxxxx>
- Error in Section 2.2
- From: "Dale Noble" <dale.noble@xxxxxxxxxxxxx>
- Re: Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Mason <slash.tmp@xxxxxxx>
- Re: Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Pialy Ghosh <pink.pia@xxxxxxxxx>
- Re: Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Mason <slash.tmp@xxxxxxx>
- Regarding GCC 4.9.2 backward compatibility with 3.2.1
- From: Pialy Ghosh <pink.pia@xxxxxxxxx>
- Re: GCC 7.2: Getting "warning: RTTI symbol not found for class" warnings in GDB
- From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
- Re: GCC 7.2: Getting "warning: RTTI symbol not found for class" warnings in GDB
- From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
- Re: GCC 7.2: Getting "warning: RTTI symbol not found for class" warnings in GDB
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- combined source tree and gold build failure
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
- GCC 7.2: Getting "warning: RTTI symbol not found for class" warnings in GDB
- From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
- Re: the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: which registers must be preserved for the caller
- From: Mason <slash.tmp@xxxxxxx>
- the mysery of gcc/go/parse.o different in stage2 and stage3 for 7.2.0
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: which registers must be preserved for the caller
- From: Andrew Makhorin <mao@xxxxxxx>
- Re: five "Bootstrap comparison failure" messages in 7.2.0
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- five "Bootstrap comparison failure" messages in 7.2.0
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: Questions on the result of dependency generation
- From: chran wang <dmmychrnwng@xxxxxxxxx>
- Re: std::deque move constructor
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: std::deque move constructor
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- enable-symvers (was: Re: std::deque move constructor)
- From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
- Re: std::deque move constructor
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Bugzilla (was: GCC does not generate ADCX or ADOX for _addcarryx_u64)
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: which registers must be preserved for the caller
- From: Mason <slash.tmp@xxxxxxx>
- 7.2.0 says "Bootstrap comparison failure!" on entering stage3
- From: "dclarke@xxxxxxxxxxxxx" <dclarke@xxxxxxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Uros Bizjak <ubizjak@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Bugzilla (was: GCC does not generate ADCX or ADOX for _addcarryx_u64)
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Bugzilla (was: GCC does not generate ADCX or ADOX for _addcarryx_u64)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Bugzilla (was: GCC does not generate ADCX or ADOX for _addcarryx_u64)
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Bugzilla (was: GCC does not generate ADCX or ADOX for _addcarryx_u64)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Does GCC need a special switch for ADCX/ADOX?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Marc Glisse <marc.glisse@xxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- GCC does not generate ADCX or ADOX for _addcarryx_u64
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Does GCC need a special switch for ADCX/ADOX?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Does GCC need a special switch for ADCX/ADOX?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Does GCC need a special switch for ADCX/ADOX?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Questions on the result of dependency generation
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: std::deque move constructor
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: std::deque move constructor
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- std::deque move constructor
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: Questions on the result of dependency generation
- From: chran wang <dmmychrnwng@xxxxxxxxx>
- Re: Questions on the result of dependency generation
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- which registers must be preserved for the caller
- From: Andrew Makhorin <mao@xxxxxxx>
- Questions on the result of dependency generation
- From: chran wang <dmmychrnwng@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Ignas Brašiškis <ignas.brasiskis@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Flag to undo --enable-frame-pointer builds on i386
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: niXman <i.nixman@xxxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: Flag to undo --enable-frame-pointer builds on i386
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: Build cross compiler for Raspberry Pi
- From: Avelino Herrera Morales <avelinoherrera@xxxxxxxxx>
- Re: Build cross compiler for Raspberry Pi
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
- Re: Build cross compiler for Raspberry Pi
- From: Avelino Herrera Morales <avelinoherrera@xxxxxxxxx>
- Re: Build cross compiler for Raspberry Pi
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
- Build cross compiler for Raspberry Pi
- From: Avelino Herrera Morales <avelinoherrera@xxxxxxxxx>
- Re: Flag to undo --enable-frame-pointer builds on i386
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Flag to undo --enable-frame-pointer builds on i386
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Flag to undo --enable-frame-pointer builds on i386
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: -msse4.1 causes "SSE4.2 instruction set not enabled"
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Is there any plans or work going on gcc related to c++ coroutines?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Is there any plans or work going on gcc related to c++ coroutines?
- From: Ignas Brašiškis <ignas.brasiskis@xxxxxxxxx>
- Re: Optimization with inline assembly
- From: Liu Hao <lh_mouse@xxxxxxx>
- Re: Optimization with inline assembly
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Optimization with inline assembly
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Optimization with inline assembly
- From: Marcel Keller <m.keller@xxxxxxxxxxxxx>
- Re: prtdiff_t / void *
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: prtdiff_t / void *
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: prtdiff_t / void *
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: prtdiff_t / void *
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: Internal compiler error while compiling gcc 7.1.0
- From: Hector Barrios <hectorb@xxxxxxxxxx>
- prtdiff_t / void *
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Internal compiler error while compiling gcc 7.1.0
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Internal compiler error while compiling gcc 7.1.0
- From: Hector E Barrios Molano <hectorb@xxxxxxxxxx>
- Re: Finding the optimization that is making the change
- From: Will Hawkins <whh8b@xxxxxxxxxxxx>
- Re: Finding the optimization that is making the change
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Finding the optimization that is making the change
- From: Will Hawkins <whh8b@xxxxxxxxxxxx>
- Re: Weird performance behaviour
- From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
- Re: Finding the optimization that is making the change
- From: Will Hawkins <whh8b@xxxxxxxxxxxx>
- Re: Finding the optimization that is making the change
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Finding the optimization that is making the change
- From: Will Hawkins <whh8b@xxxxxxxxxxxx>
- Weird performance behaviour
- From: Marcel Keller <m.keller@xxxxxxxxxxxxx>
- Re: -msse4.1 causes "SSE4.2 instruction set not enabled"
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Build problems with glibc 2.26
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Build problems with glibc 2.26
- From: Rolf Eike Beer <eb@xxxxxxxxx>
- Re: Build problems with glibc 2.26
- From: Rolf Eike Beer <eb@xxxxxxxxx>
- Re: Build problems with glibc 2.26
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: Build problems with glibc 2.26
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Build problems with glibc 2.26
- From: Rolf Eike Beer <eb@xxxxxxxxx>
- Error with LTO and GCC 7.2 RC1
- From: Simon L <stl102@xxxxxxxxx>
- Re: -msse4.1 causes "SSE4.2 instruction set not enabled"
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- -msse4.1 causes "SSE4.2 instruction set not enabled"
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Martin Sebor <msebor@xxxxxxxxx>
- How to merger gcov data
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
- Re: C++ toupper symbol clash?
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- C++ toupper symbol clash?
- From: Jonny Grant <jg@xxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- Re: Invariant is not moved out of loop
- From: Astor Piaz <appiazzolla@xxxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- GCC 6.4.0 : mystery about why libstdc++.so.6.0.22 would be missing an ELF section
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Jeff Law <law@xxxxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: Using SSE2 with the old i386 ABI
- From: Jeff Law <law@xxxxxxxxxx>
- Using SSE2 with the old i386 ABI
- From: Florian Weimer <fweimer@xxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- Re: gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Mason <slash.tmp@xxxxxxx>
- gcov can't collect data when process is executed by systemctl start but it can when executed by ./process
- From: Xiaoli Feng <xifeng@xxxxxxxxxx>
- 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: Invariant is not moved out of loop
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: Invariant is not moved out of loop
- From: Astor Piaz <appiazzolla@xxxxxxxxx>
- Re: Invariant is not moved out of loop
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Invariant is not moved out of loop
- From: Astor Piaz <appiazzolla@xxxxxxxxx>
- Re: GCC 7.1 build error
- Re: prevent (pre_inc ...) from satisfying "movhi" RTL template constraints
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: prevent (pre_inc ...) from satisfying "movhi" RTL template constraints
- From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
- Re: prevent (pre_inc ...) from satisfying "movhi" RTL template constraints
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- prevent (pre_inc ...) from satisfying "movhi" RTL template constraints
- From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
- Re: -Wimplicit-fallthrough broken?
- From: Georg-Johann Lay <avr@xxxxxxxx>
- Re: -Wimplicit-fallthrough broken?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: -Wimplicit-fallthrough broken?
- From: Mason <slash.tmp@xxxxxxx>
- Re: Manual intallation with admin priviledges: what to put in my path?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Manual intallation with admin priviledges: what to put in my path?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Manual intallation with admin priviledges: what to put in my path?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Manual intallation with admin priviledges: what to put in my path?
- From: Sebastian Kroppen <zwiebel.genuss@xxxxxx>
- Re: building gcc-7.1.0 on ubuntu 12.04 failed
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- building gcc-7.1.0 on ubuntu 12.04 failed
- From: Alexey Egorov <alex.only.d@xxxxxxxxx>
- -Wimplicit-fallthrough broken?
- From: Georg-Johann Lay <avr@xxxxxxxx>
- Failed to build with LTO
- From: Csaba Raduly <rcsaba@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
- Re: undefined reference error/g++-6
- From: sothy shan <sothy.e98@xxxxxxxxx>
- Re: undefined reference error/g++-6
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: undefined reference error/g++-6
- From: sothy shan <sothy.e98@xxxxxxxxx>
- Re: undefined reference error/g++-6
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: undefined reference error/g++-6
- From: sothy shan <sothy.e98@xxxxxxxxx>
- Re: undefined reference error/g++-6
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- undefined reference error/g++-6
- From: sothy shan <sothy.e98@xxxxxxxxx>
- GCC 7.1 build error
- From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
- Re: How ship gcc binaries and recompile whole gcc for additional gcc language support
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- How ship gcc binaries and recompile whole gcc for additional gcc language support
- From: mfe userlast <mfe@xxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: restrict vs. __restrict__ (gcc 4.8)
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: restrict vs. __restrict__ (gcc 4.8)
- From: Ian Pilcher <arequipeno@xxxxxxxxx>
- Re: restrict vs. __restrict__ (gcc 4.8)
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
- restrict vs. __restrict__ (gcc 4.8)
- From: Ian Pilcher <arequipeno@xxxxxxxxx>
- Re: preprocessing directive with no new-line character
- From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
- preprocessing directive with no new-line character
- From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
- Re: Should std::byte copy-list-initialization fail?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Should std::byte copy-list-initialization fail?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: gcc-7.1.0 fails to build with flto profiled bootstrap build (with gold linker) + graphite optimisations
- From: Branko <brankob@xxxxxxxxxxxxx>
- Re: gcc-7.1.0 fails to build with flto profiled bootstrap build (with gold linker) + graphite optimisations
- From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
- Re: gcc-7.1.0 fails to build with flto profiled bootstrap build (with gold linker) + graphite optimisations
- From: Branko <brankob@xxxxxxxxxxxxx>
- Incorrect entry on C11Status page: fopen mode "x"
- From: Keith Thompson <Keith.S.Thompson@xxxxxxxxx>
- gcc-7.1.0 fails to build with flto profiled bootstrap build (with gold linker) + graphite optimisations
- From: Branko <brankob@xxxxxxxxxxxxx>
- Re: Should std::byte copy-list-initialization fail?
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Should std::byte copy-list-initialization fail?
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: -Wlto-type-mismatch with flexible array in struct
- From: Martin Sebor <msebor@xxxxxxxxx>
- -Wlto-type-mismatch with flexible array in struct
- From: "Dan Halbert" <halbert@xxxxxxxxxxx>
- Re: Why does GCC reload my array base pointer? (C++, ASM)
- From: David Pfander <David.Pfander@xxxxxxxxxxxxxxxxxxxxx>
- Re: Cntrl-C Exit and Error Exits Question
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Cntrl-C Exit and Error Exits Question
- From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
- Re: Why does GCC reload my array base pointer? (C++, ASM)
- From: Matthias Kretz <m.kretz@xxxxxx>
- Re: Why does GCC reload my array base pointer? (C++, ASM)
- From: Juan Cabrera <jjcp.91@xxxxxxxxx>
- Why does GCC reload my array base pointer? (C++, ASM)
- From: David Pfander <David.Pfander@xxxxxxxxxxxxxxxxxxxxx>
- gcc dwarf DW_OP_mod
- From: phi gcc <phi.gcc@xxxxxxxxx>
- Re: Link to gcc 6.4 documentation is bad
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- g++ 5.4.0 inserting const cast that breaks a constexpr - diagnostics ?
- From: Jason Vas Dias <jason.vas.dias@xxxxxxxxx>
- Re: -Wformat-overflow works strangely with struct members
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: -Wformat-overflow works strangely with struct members
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: -Wformat-overflow works strangely with struct members
- From: Martin Sebor <msebor@xxxxxxxxx>
- -Wformat-overflow works strangely with struct members
- From: Basin Ilya <basinilya@xxxxxxxxx>
- Link to gcc 6.4 documentation is bad
- From: David Gressett <DGressett@xxxxxxxxxxxxxxx>
- Re: GPL Runtime Exception and C++ Inheritance
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- GPL Runtime Exception and C++ Inheritance
- From: Jeremy Vincent Yu <yujeremyvincent@xxxxxxxxx>
- Re: g++ not using ipa-sra for small struct / class
- From: Juan Cabrera <jjcp.91@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: "Richard Earnshaw (lists)" <Richard.Earnshaw@xxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Bug in c++11 mode when instantiating template with local class
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
- g++ not using ipa-sra for small struct / class
- From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Andrew Haley <aph@xxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Alexander Monakov <amonakov@xxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: Jeff Law <law@xxxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- Re: __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64 (correction)
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- __GCC_HAVE_SYNC_COMPARE_AND_SWAP_16 not defined on aarch64
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: "Ian Lance Taylor via gcc-help" <gcc-help@xxxxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
- Re: GCC (LRA): error: unable to find a register to spill
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- GCC (LRA): error: unable to find a register to spill
- From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
- Re: GCC complains about nested functions despite none being present
- From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
- GCC complains about nested functions despite none being present
- From: Maxim Blinov <maxim.a.blinov@xxxxxxxxx>
- Re: Bug in c++11 mode when instantiating template with local class
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: __BIGGEST_ALIGNMENT / more on arch compiler defines
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Bug in c++11 mode when instantiating template with local class
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- Re: Bug in c++11 mode when instantiating template with local class
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: __BIGGEST_ALIGNMENT / more on arch compiler defines
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Value Initialization in GCC
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: std::aligned_storage and [[gnu::may_alias]]
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: std::aligned_storage and [[gnu::may_alias]]
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Pico Geyer <picogeyer@xxxxxxxxx>
- Re: std::aligned_storage and [[gnu::may_alias]]
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: __BIGGEST_ALIGNMENT / more on arch compiler defines
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Value Initialization in GCC
- From: Sam Lunt <sam.lunt@xxxxxxxxxxxxxxxxxxxx>
- Bug in c++11 mode when instantiating template with local class
- From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
- __BIGGEST_ALIGNMENT / more on arch compiler defines
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: Libraries: libusb question
- From: MikeSD <ipscone@xxxxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Martin Sebor <msebor@xxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Pico Geyer <picogeyer@xxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Toebs Douglass <toby@xxxxxxxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- Re: Libraries: libusb question
- From: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Pico Geyer <picogeyer@xxxxxxxxx>
- Re: format-truncation warning with -O2 on gcc 7.1.1
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- format-truncation warning with -O2 on gcc 7.1.1
- From: Pico Geyer <picogeyer@xxxxxxxxx>
- LTO debugging with GDB
- From: "Peryt, Sebastian" <sebastian.peryt@xxxxxxxxx>
- Libraries: libusb question
- From: MikeSD <ipscone@xxxxxxxxxxx>
- Re: std::aligned_storage and [[gnu::may_alias]]
- From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
- std::aligned_storage and [[gnu::may_alias]]
- From: Avi Kivity <avi@xxxxxxxxxxxx>
- Re: Question about extra debug (DWARF) info generated by gcc6/7
- From: Peter Edwards <peadar@xxxxxxxxxx>
- Re: Question about extra debug (DWARF) info generated by gcc6/7
- From: Richard Biener <richard.guenther@xxxxxxxxx>
[Index of Archives]
[Fedora Development]
[Security]
[Netfilter]
[Bugtraq]
