GCC Help

• Thread Index

• Installing gcc 4.7.2 on Solaris 10 - SPARC platform
  • From: Dipanjan Das <its.dipanjan.das@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: gcc 4.8 search path usr/... instead of /usr/...
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: Bare metal ARM Cross compiler - aeabi auto-generated functions for cortex-m0 use wrong instruction set
  • From: jprofesorek <jprofesorek@xxxxx>
• Re: Build ELF Binary File
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Build ELF Binary File
  • From: "ugiwgh" <ugiwgh@xxxxxxxxx>
• Re:
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Fwd:
  • From: dhinesh someone <dhineshflames@xxxxxxxxx>
• Re: Bare metal ARM Cross compiler - aeabi auto-generated functions for cortex-m0 use wrong instruction set
  • From: Maxim Kuvyrkov <maxim@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: gcc 4.8 search path usr/... instead of /usr/...
  • From: tmp15711 <tmp15711@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Bare metal ARM Cross compiler - aeabi auto-generated functions for cortex-m0 use wrong instruction set
  • From: Chris Johns <chrisj@xxxxxxxxx>
• Bare metal ARM Cross compiler - aeabi auto-generated functions for cortex-m0 use wrong instruction set
  • From: Jan K <jprofesorek@xxxxx>
• Re: gcc 4.8 search path usr/... instead of /usr/...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc 4.8 search path usr/... instead of /usr/...
  • From: y y <tmp15711@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Problem updating gcc 4.6.2 under Fedora16
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Problem updating gcc 4.6.2 under Fedora16
  • From: Daniel Tsen <etiger99@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: using -fsplit-stack
  • From: mathieu lacage <mathieu.lacage@xxxxxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Question about gimple frontend
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Question about gimple frontend
  • From: Lyu Mitnick <mitnick.lyu@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: using -fsplit-stack
  • From: mathieu lacage <mathieu.lacage@xxxxxxxxxxxx>
• Building GCC 4.7.2 on Solaris 10 x86 AMD64 - Getting linker error involving eh_frame
  • From: Jim Rice <jmrice6640@xxxxxxxxx>
• Re: using -fsplit-stack
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• using -fsplit-stack
  • From: mathieu lacage <mathieu.lacage@xxxxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Frédéric Buclin <LpSolit@xxxxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Question about gimple frontend
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: loop-unrolling in gcc-4.6.2
  • From: naga raj <gnuuser.raj@xxxxxxxxx>
• Re: loop-unrolling in gcc-4.6.2
  • From: Maxim Kuvyrkov <maxim@xxxxxxxxxxxxxxxx>
• Question about gimple frontend
  • From: Lyu Mitnick <mitnick.lyu@xxxxxxxxx>
• Re: GO_IF_LEGITIMATE_ADDRESS handling different addressing modes for load/store
  • From: Ayonam Ray <ayonam@xxxxxxxxx>
• Re: GO_IF_LEGITIMATE_ADDRESS handling different addressing modes for load/store
  • From: Jeff Law <law@xxxxxxxxxx>
• GO_IF_LEGITIMATE_ADDRESS handling different addressing modes for load/store
  • From: Ayonam Ray <ayonam@xxxxxxxxx>
• Re: ppl-0.11 fails to find gmp-4.3.2
  • From: Ángel González <keisial@xxxxxxxxx>
• Fwd: DRIVER_SELF_SPECS and multilib
  • From: gnubie gnubie <gcc.gnubie@xxxxxxxxx>
• Re: std::multimap preserving order in erase() and insert()?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• std::multimap preserving order in erase() and insert()?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• ppl-0.11 fails to find gmp-4.3.2
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• Re: Fail to configure gcc 4.7.2 with latest version of cloog
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Fail to configure gcc 4.7.2 with latest version of cloog
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: Fail to configure gcc 4.7.2 with latest version of cloog
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• Re: Fail to configure gcc 4.7.2 with latest version of cloog
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• Re: Fail to configure gcc 4.7.2 with latest version of cloog
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Fail to configure gcc 4.7.2 with latest version of cloog
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• GCC 4.7.2 Configure fails with latest version of ppl
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• Configure script for gcc 4.7.2 fails with no ppl
  • From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
• Configuration i386-pc-solaris2.8 not supported
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: how to delete a test result posting
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: how to delete a test result posting
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Defaulted initializer constructor
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Defaulted initializer constructor
  • From: Henrik Mannerström <henrik.mannerstrom@xxxxxxxxx>
• Re: loop-unrolling in gcc-4.6.2
  • From: naga raj <gnuuser.raj@xxxxxxxxx>
• Re: loop-unrolling in gcc-4.6.2
  • From: Maxim Kuvyrkov <maxim@xxxxxxxxxxxxxxxx>
• how to delete a test result posting
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• loop-unrolling in gcc-4.6.2
  • From: naga raj <gnuuser.raj@xxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: [C++] anonymous struct linkage
  • From: "LAMOME Julien CS-SI" <julien.lamome-cs-si@xxxxxxx>
• some question about arm cross toolchain
  • From: loody <miloody@xxxxxxxxx>
• Re: Catch 22 compiling ppl: Internal compiler error: Illegal instruction
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Catch 22 compiling ppl: Internal compiler error: Illegal instruction
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Catch 22 compiling ppl: Internal compiler error: Illegal instruction
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Catch 22 compiling ppl: Internal compiler error: Illegal instruction
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Some bad commits in imported ancient history?
  • From: Harald van Dijk <harald@xxxxxxxxxxx>
• Catch 22 compiling ppl: Internal compiler error: Illegal instruction
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: [C++] anonymous struct linkage
  • From: Andrew Haley <aph@xxxxxxxxxx>
• [C++] anonymous struct linkage
  • From: "LAMOME Julien CS-SI" <julien.lamome-cs-si@xxxxxxx>
• Re: gcda files not getting formed from gcov
  • From: IAMTubby <Aftab_Hassan@xxxxxxxx>
• gcda files not getting formed from gcov
  • From: IAMTubby <Aftab_Hassan@xxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: help with compiling gcc-4.1.2 on CentOS 6.3 x64
  • From: Han Jiang <oglops@xxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: help with compiling gcc-4.1.2 on CentOS 6.3 x64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• help with compiling gcc-4.1.2 on CentOS 6.3 x64
  • From: Han Jiang <oglops@xxxxxxxxx>
• help with compiling gcc-4.1.2 on CentOS 6.3 x64
  • From: Han Jiang <oglops@xxxxxxxxx>
• help with compiling gcc-4.1.2 on CentOS 6.3 x64
  • From: Han Jiang <oglops@xxxxxxxxx>
• help about building native compiler for new target
  • From: santosh tatoju <santosh_tatoju@xxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: gcc 4.7.2 fails to bootstrap in stage 1
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• gcc 4.7.2 fails to bootstrap in stage 1
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Problems in pr26180.c with own backend
  • From: Andreas Geißler <setjem@xxxxxxxxx>
• Re: Incorrect asm constraints or GCC bug?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Incorrect asm constraints or GCC bug?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Incorrect asm constraints or GCC bug?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: How to dump all the warning/error messages list from gcc compiler?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_bool_compare_and_swap() With a Pointer
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• __sync_bool_compare_and_swap() With a Pointer
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: How to dump all the warning/error messages list from gcc compiler?
  • From: Xiaopi Liu <liuxiaopi349@xxxxxxxxx>
• Re: How to dump all the warning/error messages list from gcc compiler?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Bit-fields of enum type
  • From: Владимир Андреев <volodya@xxxxxxxxxxxx>
• Re: How to dump all the warning/error messages list from gcc compiler?
  • From: Xiaopi Liu <liuxiaopi349@xxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __sync_fetch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: A not so stellar result on Solaris 10
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: A not so stellar result on Solaris 10
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: A not so stellar result on Solaris 10
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• A not so stellar result on Solaris 10
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• __sync_fetch
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: How to dump all the warning/error messages list from gcc compiler?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Adding additional system paths to a custom GCC
  • From: Tim Schumacher <schumact@xxxxxxxxx>
• Re: Adding additional system paths to a custom GCC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Adding additional system paths to a custom GCC
  • From: Tim Schumacher <schumact@xxxxxxxxx>
• How to dump all the warning/error messages list from gcc compiler?
  • From: Xiaopi Liu <liuxiaopi349@xxxxxxxxx>
• Sub-blocks
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: Adding additional system paths to a custom GCC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Adding additional system paths to a custom GCC
  • From: Tim Schumacher <schumact@xxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Compile of current trunk failing - asan reconfigure
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Compile of current trunk failing - asan reconfigure
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compile of current trunk failing - asan reconfigure
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Compile of current trunk failing - asan reconfigure
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compile of current trunk failing - asan reconfigure
  • From: larsbj@xxxxxxxxxx (Lars Gullik Bjønnes)
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Problems in pr26180.c with own backend
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Re: pr26180.c
  • From: Andreas Geißler <setjem@xxxxxxxxx>
• Re: pr26180.c
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problems in pr26180.c with own backend
  • From: Andreas Geißler <setjem@xxxxxxxxxxxxxx>
• pr26180.c
  • From: Andreas Geißler <setjem@xxxxxxxxxxxxxx>
• gcc-4.7.2 arm-eabi multilibs
  • From: Chris Johns <chrisj@xxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: mips-gcc : how to disable 8bit and 16bit memory accesses
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• mips-gcc : how to disable 8bit and 16bit memory accesses
  • From: HEITZMANN Frédéric 218168 <frederic.heitzmann@xxxxxx>
• Re: Binutils version for GCC 4.8
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Ryan Johnson <ryan.johnson@xxxxxxxxxxxxxx>
• the struggle for a 64-bit GCC on Solaris 10 - part 2
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Symbol visibility and bypassing PLT for intra-DSO calls
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: Symbol visibility and bypassing PLT for intra-DSO calls
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Symbol visibility and bypassing PLT for intra-DSO calls
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Symbol visibility and bypassing PLT for intra-DSO calls
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Symbol visibility and bypassing PLT for intra-DSO calls
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: gcc compile for code size
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc compile for code size
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc compile for code size
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Charles Smith <cts.private@xxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Charles Smith <cts.private@xxxxxxxxx>
• Re: gcc compile for code size
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• Re: gcc compile for code size
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc compile for code size
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Charles Smith <cts.private@xxxxxxxxx>
• Re: probably an old question about overriding hardcoded library search paths
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• probably an old question about overriding hardcoded library search paths
  • From: Charles Smith <cts.private@xxxxxxxxx>
• Re: DECL_NAME() yields ._69 for anonymous union parsed with g++
  • From: Peter Colberg <peter@xxxxxxxxxxx>
• Re: What is wrong in this code?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: What is wrong in this code?
  • From: Angelo Graziosi <graziosi.angelo@xxxxxxxxx>
• Re: What is wrong in this code?
  • From: Michael Witten <mfwitten@xxxxxxxxx>
• the struggle to create a 64-bit gcc on Solaris 10
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Binutils version for GCC 4.8
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Testing a Canadian cross
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• DECL_NAME() yields ._69 for anonymous union parsed with g++
  • From: Peter Colberg <peter@xxxxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: x86 procedure calling convention (again)
  • From: "Bob Plantz" <plantz@xxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: x86 procedure calling convention (again)
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: Fwd: Help to understand instructions
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• Re: x86 procedure calling convention (again)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• x86 procedure calling convention (again)
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Fwd: Help to understand instructions
  • From: Sergey Ivanov <icegood1980@xxxxxxxxx>
• Testing a Canadian cross
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: Build for multi-platform
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Build for multi-platform
  • From: Colin Sim <Colin.Sim@xxxxxxxxx>
• Re: Runtime Parameters in GCC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Runtime Parameters in GCC
  • From: SANKAR <chnabsankar@xxxxxxxxx>
• Re: Runtime Parameters in GCC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Runtime Parameters in GCC
  • From: SANKAR <chnabsankar@xxxxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [HarfBuzz] does graphite affect the c++ munging? Does -On?
  • From: Jonathan Kew <jfkthame@xxxxxxxxxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: James Cloos <cloos@xxxxxxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: Philipp Thomas <Philipp.Thomas2@xxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: James Cloos <cloos@xxxxxxxxxxx>
• Re: does graphite affect the c++ munging? Does -On?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• does graphite affect the c++ munging? Does -On?
  • From: James Cloos <cloos@xxxxxxxxxxx>
• Re: GCC 3.4.6 Install
  • From: Jake Prasad <jakeprasad@xxxxxxxxx>
• Re: GCC 3.4.6 Install
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC 3.4.6 Install
  • From: Jake Prasad <jakeprasad@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Using GCC to verify code has no "functional change".
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Error with gcc 4.7.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error with gcc 4.7.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error with gcc 4.7.1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error with gcc 4.7.1
  • From: rbmj <rbmj@xxxxxxxxxxx>
• Re: Error with gcc 4.7.1
  • From: larsbj@xxxxxxxxxx (Lars Gullik Bjønnes)
• Error with gcc 4.7.1
  • From: Pranith Kumar <pranith@xxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• writing plugins
  • From: "Klaus Rudolph" <lts-rudolph@xxxxxx>
• Re: How to identify Arch info when building
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: How to identify Arch info when building
  • From: Matthew Gretton-Dann <matthew.gretton-dann@xxxxxxxxxx>
• Re: ARM cross mismatch error
  • From: Matthew Gretton-Dann <matthew.gretton-dann@xxxxxxxxxx>
• ARM cross mismatch error
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• How to identify Arch info when building
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• "gcc-4.1.2 - could not find spill register"
  • From: amith pawar <amith.pawar@xxxxxxxxx>
• Re: Using GCC to verify code has no "functional change".
  • From: John Steele Scott <toojays@xxxxxxxxxxx>
• Using GCC to verify code has no "functional change".
  • From: John Steele Scott <toojays@xxxxxxxxxxx>
• Re: please help me
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• please help me
  • From: amith pawar <amith.pawar@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Rick Springob <rspringob@xxxxxxxxx>
• Re: How does inline definitions affect inlining heuristics for C++?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Ángel González <keisial@xxxxxxxxx>
• How does inline definitions affect inlining heuristics for C++?
  • From: Ulf Magnusson <ulfalizer@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• RE: loading of shared objects and executables
  • From: "Bolshakov, Roman" <Roman.Bolshakov@xxxxxxx>
• RE: loading of shared objects and executables
  • From: "Bolshakov, Roman" <Roman.Bolshakov@xxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: David Edelsohn <dje.gcc@xxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Building cross / multilib gcc question
  • From: "Steve Ellcey " <sellcey@xxxxxxxx>
• libstdc++ 3.x causes linker errors
  • From: Dara Hazeghi <dhazeghi@xxxxxxxxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: David Edelsohn <dje.gcc@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Rick Springob <rspringob@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: David Edelsohn <dje.gcc@xxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: ICE in deps_analyze_insn, at sched-deps.c: GCC-4.6.3
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Rick Springob <rspringob@xxxxxxxxx>
• Re: internal compiler error: in expand_debug_locations, at cfgexpand.c:3683
  • From: Patrick Oppenlander <pattyo.lists@xxxxxxxxx>
• ICE in deps_analyze_insn, at sched-deps.c: GCC-4.6.3
  • From: "ranjan.amit8" <ranjan.amit8@xxxxxxxxx>
• Re: Phase ordering in compiler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Phase ordering in compiler
  • From: SANKAR <chnabsankar@xxxxxxxxx>
• internal compiler error: in expand_debug_locations, at cfgexpand.c:3683
  • From: Patrick Oppenlander <pattyo.lists@xxxxxxxxx>
• Re: Linking issue with _GLIBCXX_DEBUG on 4.7/google
  • From: Oleg Smolsky <oleg.smolsky@xxxxxxxxxxxx>
• Re: Linking issue with _GLIBCXX_DEBUG on 4.7/google
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Linking issue with _GLIBCXX_DEBUG on 4.7/google
  • From: Oleg Smolsky <oleg.smolsky@xxxxxxxxxxxx>
• Re: Phase ordering in compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• How To Analyze Stocks
  • From: "Dennis Walden" <sshebbnn@xxxxxxxxxxxxx>
• RE: loading of shared objects and executables
  • From: "Bolshakov, Roman" <Roman.Bolshakov@xxxxxxx>
• Re: GCC plugins: mapping AST back to source files, missing locations.
  • From: mefyl <mefyl@xxxxxxxxxxxx>
• Phase ordering in compiler
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Re: loading of shared objects and executables
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• loading of shared objects and executables
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Little help for total pleasance
  • From: "Carrie Maldonado" <polly.taylor@xxxxxxxxxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: difference between compiling Kernel modules for linux 2.4 with gcc 3.4 rather than 3.3
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• difference between compiling Kernel modules for linux 2.4 with gcc 3.4 rather than 3.3
  • From: Åke Forslund <aforslund@xxxxxxxxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc mips32r2 register allocation
  • From: Dmytro Milinevskyy <milinevskyy@xxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issu
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• problems building gcc-4.3.5-1 on AIX 6.1 with pthreads
  • From: Rick Springob <rspringob@xxxxxxxxx>
• Re: GCC plugins: mapping AST back to source files, missing locations.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• GCC plugins: mapping AST back to source files, missing locations.
  • From: mefyl <mefyl@xxxxxxxxxxxx>
• Re: Divide by Zero segment fault
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Divide by Zero segment fault
  • From: Deepthi Bokka <dbokka@xxxxxxxxxxxxxxxxx>
• Re: __builtin_extract_return_address undefined
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issues
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: __builtin_extract_return_address undefined
  • From: Alfonso Acosta <alfonso.acosta@xxxxxxxxx>
• Re: __builtin_extract_return_address undefined
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Distinguish between instructions in print_operand_address
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Distinguish between instructions in print_operand_address
  • From: Jan Tlatlik <jantlatlik@xxxxxxxxx>
• __builtin_extract_return_address undefined
  • From: Alfonso Acosta <alfonso.acosta@xxxxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: C++ SEGMENT fault and vtable issues
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Inconsisten error messages on const pointers
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Re: Inconsisten error messages on const pointers
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Inconsisten error messages on const pointers
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• C++ SEGMENT fault and vtable issues
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• libgcc libraries
  • From: "Gary Partis" <gary@xxxxxxxxxxxx>
• An error on building the GCC tic6x cross compiler
  • From: WJ Wang <m9802119@xxxxxxxxxxxxxxxxx>
• Re: gcc compil
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc compil
  • From: samirnext <samir.tidafi@xxxxxxxxx>
• Re: An error on building the GCC tic6x cross compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem with modyfying "addsi3" in machine description
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problem with modyfying "addsi3" in machine description
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: An error on building the GCC tic6x cross compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Passing 64-bit function arguments to assembler
  • From: Andrew Pinski <pinskia@xxxxxxxxx>
• An error on building the GCC tic6x cross compiler
  • From: "m9802119" <m9802119@xxxxxxxxxxxxxxxxx>
• BOOST_FOREACH prevent 100% code coverage
  • From: Marcin Zawadzki <zaba.marcin@xxxxxxxxx>
• Re: How to get LD_DEBUG of forked process
  • From: Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx>
• Re: gcc compil
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: How to get LD_DEBUG of forked process
  • From: David Daney <ddaney.cavm@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc compil
  • From: samirnext <samir.tidafi@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: ludo@xxxxxxx (Ludovic Courtès)
• This Company is our New Explosive Tech Play
  • From: "Winifred Hawkins" <neilsg2001@xxxxxxxxxxxxxxxxxx>
• How to get LD_DEBUG of forked process
  • From: Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: A problem on building GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• A problem on building GCC
  • From: "m9802119" <m9802119@xxxxxxxxxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Torbjorn Granlund <tg@xxxxxxxxxx>
• Re: how to use libcpp (GCC c lexer)
  • From: Giovanni Gherdovich <g.gherdovich@xxxxxxxxx>
• Re: how to use libcpp (GCC c lexer)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Reporting GCC bugs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• how to use libcpp (GCC c lexer)
  • From: Giovanni Gherdovich <g.gherdovich@xxxxxxxxx>
• Re: conditional LABEL_EXPR
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Reporting GCC bugs
  • From: Torbjorn Granlund <tg@xxxxxxxxxx>
• Re: conditional LABEL_EXPR
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• This Company Is Ready To Bounce!
  • From: "Sidney Melton" <g-foxd@xxxxxxxxxxxxxx>
• Re: fprintf control from Environment variable.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• conditional LABEL_EXPR
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• RE: [RFC] Unsolicited usage of VFP registers for Cortex-M4F
  • From: "Joey Ye" <joey.ye@xxxxxxx>
• Re: [RFC] Unsolicited usage of VFP registers for Cortex-M4F
  • From: Ilija Kocho <ilijak@xxxxxxxxxxx>
• Re: fprintf control from Environment variable.
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• fprintf control from Environment variable.
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Inserting function definitions into the tree
  • From: zahed khurasani <sdzahed@xxxxxxxxx>
• Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Headers located in plugin/include
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re[2]: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Ilya Basin <basinilya@xxxxxxxxx>
• Re: Headers located in plugin/include
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Why "'X' used but never defined" is a warning and not error in gcc?
  • From: Ilya Basin <basinilya@xxxxxxxxx>
• Re: Headers located in plugin/include
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Cung cap cac loai MAY BIEN AP, MAY BIEN THE Cong suat tu 25 KVA den 5000 KVA
  • From: Hungnt <nguyenthehung.ach@xxxxxxxxx>
• Re: Problem cross compiling gcc
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Problem cross compiling gcc
  • From: Marian Buschsieweke <m.buschsieweke@xxxxxxxxxxxxxxx>
• Re: building gcc 4.5.4 fails on libiberty/copying-lib.texi
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• Re: building gcc 4.5.4 fails on libiberty/copying-lib.texi
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• building gcc 4.5.4 fails on libiberty/copying-lib.texi
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• Headers located in plugin/include
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: r192002 breaks mingw-w64 cross compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• r192002 breaks mingw-w64 cross compiler
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Pointer Target Error
  • From: Aydın Demirel <aydindem@xxxxxxxxx>
• Re: Segmentation fault when compiling GCC with new RTL pass
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: Pointer Target Error
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Pointer Target Error
  • From: Aydın Demirel <aydindem@xxxxxxxxx>
• Re: svn+ssh: Control socket connect(/tmp/ssh_gcc_control): Connection refused
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: Autovectorization help
  • From: Nicklas Bo Jensen <nbjensen@xxxxxxxxx>
• Re: Autovectorization help
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Pointer Target Error
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: svn+ssh: Control socket connect(/tmp/ssh_gcc_control): Connection refused
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: linking problems with shared objects
  • From: Michael <auinger@xxxxxxx>
• Pointer Target Error
  • From: Aydın Demirel <aydindem@xxxxxxxxx>
• svn+ssh: Control socket connect(/tmp/ssh_gcc_control): Connection refused
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: Autovectorization help
  • From: Nicklas Bo Jensen <nbjensen@xxxxxxxxx>
• Re: Autovectorization help
  • From: Tim Prince <n8tm@xxxxxxx>
• Autovectorization help
  • From: Nicklas Bo Jensen <nbjensen@xxxxxxxxx>
• Re: [RFC] Unsolicited usage of VFP registers for Cortex-M4F
  • From: Ilija Kocho <ilijak@xxxxxxxxxxx>
• Re: Segmentation fault when compiling GCC with new RTL pass
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Segmentation fault when compiling GCC with new RTL pass
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: Segmentation fault when compiling GCC with new RTL pass
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• Re: Segmentation fault when compiling GCC with new RTL pass
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Segmentation fault when compiling GCC with new RTL pass
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: linking problems with shared objects
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• linking problems with shared objects
  • From: Michael <auinger@xxxxxxx>
• Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  • From: Maxim Yegorushkin <maxim.yegorushkin@xxxxxxxxx>
• Problem with 4.8 trunk ADA frontend
  • From: JonY <jon_y@xxxxxxxxxxxxxxxxxxxxx>
• Re: _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• _GLIBCXX_ASYNC_ABI_COMPAT and ~_Async_state_common()
  • From: Maxim Yegorushkin <maxim.yegorushkin@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Dan Hitt <dan.hitt@xxxxxxxxx>
• Re: Extending machine description for custom processor
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Dan Hitt <dan.hitt@xxxxxxxxx>
• RE: __do_global_ctors missing
  • From: "Schmidt, Weston" <Weston_Schmidt@xxxxxxxxxxxxxxxxx>
• Re: Using bt,bts
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Using bt,bts
  • From: Ondřej Bílka <neleai@xxxxxxxxx>
• Re: Fwd: Compile for different machine
  • From: Sergey Ivanov <icegood1980@xxxxxxxxx>
• RE: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: "Vardhan, Sundara (GE Transportation)" <sundara.vardhan@xxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Dan Hitt <dan.hitt@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Dan Hitt <dan.hitt@xxxxxxxxx>
• GFORTRAN_CONVERT_UNIT not working for me in some situations
  • From: Shane Hart <shart6@xxxxxxx>
• Re: using asm() to execute an atomic subtraction instruction
  • From: jonnyjack <jonnyjack7@xxxxxxxxx>
• Re: fsection-anchors for strings literal ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: using asm() to execute an atomic subtraction instruction
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Using bt,bts
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: code question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Fwd: Compile for different machine
  • From: Marcin Mirosław <marcin@xxxxxxxx>
• Fwd: Compile for different machine
  • From: Sergey Ivanov <icegood1980@xxxxxxxxx>
• Re: code question
  • From: JD <jd1008@xxxxxxxxx>
• RE: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: "Feuerbacher, Alan" <AFeuerbacher@xxxxxxxxxxxxxxxx>
• using asm() to execute an atomic subtraction instruction
  • From: jonnyjack <jonnyjack7@xxxxxxxxx>
• Re: Compile for different machine
  • From: Marcin Mirosław <marcin@xxxxxxxx>
• Compile for different machine
  • From: Sergey Ivanov <icegood1980@xxxxxxxxx>
• Why secondary_reload ignores sri->icode ?
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• fsection-anchors for strings literal ?
  • From: "yon ar c'hall" <yon.ar.chall@xxxxxxxxx>
• Re: Using bt,bts
  • From: Ondřej Bílka <neleai@xxxxxxxxx>
• Re: is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• is there any way to change the order of name resolution in linking (aside from putting the libraries in the right order?)
  • From: Dan Hitt <dan.hitt@xxxxxxxxx>
• Re: code question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: corrupted double-linked
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __gthread* on vxworks
  • From: rbmj <rbmj@xxxxxxxxxxx>
• Re: Exception handling not working on 4.7.1
  • From: Zoltan Glozik <zoltan@xxxxxxxxxxxxxxxxxxx>
• code question
  • From: JD <jd1008@xxxxxxxxx>
• corrupted double-linked
  • From: "GHui" <ugiwgh@xxxxxxxxx>
• __gthread* on vxworks
  • From: rbmj <rbmj@xxxxxxxxxxx>
• Re: Using bt,bts
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ivopts-caused "unrecognized insn"
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: ivopts-caused "unrecognized insn"
  • From: Cynbe ru Taren <cynbe@xxxxxxx>
• Re: ivopts-caused "unrecognized insn"
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ivopts-caused "unrecognized insn"
  • From: Cynbe ru Taren <cynbe@xxxxxxx>
• Using bt,bts
  • From: Ondřej Bílka <neleai@xxxxxxxxx>
• Re: __do_global_ctors missing
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: x64 instruction scheduling.
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: Generating a deprecation warning for macros
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: ivopts-caused "unrecognized insn"
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ivopts-caused "unrecognized insn"
  • From: Cynbe ru Taren <cynbe@xxxxxxx>
• Re: x64 instruction scheduling.
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• x64 instruction scheduling.
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: Getting started writing a GIMPLE analysis plugin
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• ivopts-caused "unrecognized insn"
  • From: Cynbe ru Taren <cynbe-kw-gcchelp.bbf6e8@xxxxxxxx>
• __do_global_ctors missing
  • From: "Schmidt, Weston" <Weston_Schmidt@xxxxxxxxxxxxxxxxx>
• RFC: Unsolicited usage of VFP registers for Cortex-M4F
  • From: Ilija Kocho <ilijak@xxxxxxxxxxx>
• Re: STT_GNU_IFUNC with OpenMP
  • From: Johannes Ziegenbalg <johannes.ziegenbalg@xxxxxxxxx>
• Re: --with-gmp, --with-mpfr and/or --with-mpc
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• RE: --with-gmp, --with-mpfr and/or --with-mpc
  • From: "Iyer, Balaji V" <balaji.v.iyer@xxxxxxxxx>
• Re: --with-gmp, --with-mpfr and/or --with-mpc
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: --with-gmp, --with-mpfr and/or --with-mpc
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: --with-gmp, --with-mpfr and/or --with-mpc
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Extending machine description for custom processor
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: STT_GNU_IFUNC with OpenMP
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Trouble with gcc -B option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Extending machine description for custom processor
  • From: Tomasz Jankowski <tomcioj@xxxxxxxxx>
• RE: Trouble with gcc -B option
  • From: "Feuerbacher, Alan" <AFeuerbacher@xxxxxxxxxxxxxxxx>
• STT_GNU_IFUNC with OpenMP
  • From: Johannes Ziegenbalg <johannes.ziegenbalg@xxxxxxxxx>
• Re: fno-diagnostics-show-caret
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• fno-diagnostics-show-caret
  • From: Konstantin Vladimirov <konstantin.vladimirov@xxxxxxxxx>
• Re: Generating a deprecation warning for macros
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Generating a deprecation warning for macros
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• static build is still requiring libgcc_s_seg-1.dll
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Steve Ellcey <sellcey@xxxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: mingw-w64 cross compiling
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Getting started writing a GIMPLE analysis plugin
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: mingw-w64 cross compiling
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: Question on overriding operator=
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: mingw-w64 cross compiling
  • From: niXman <i.nixman@xxxxxxxxx>
• mingw-w64 cross compiling
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Exception handling not working on 4.7.1
  • From: Zoltan Glozik <zoltan@xxxxxxxxxxxxxxxxxxx>
• Re: Question on overriding operator=
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Question on overriding operator=
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Trouble with gcc -B option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Ian Lance Taylor <ian@xxxxxxxx>
• RE: Trouble with gcc -B option
  • From: "Feuerbacher, Alan" <AFeuerbacher@xxxxxxxxxxxxxxxx>
• compact frame descriptions incompatible with DWARF2 .eh_frame
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: GCC 3.4.6 Install
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• GCC 3.4.6 Install
  • From: Jake Prasad <jakeprasad@xxxxxxxxx>
• Re: Why atomic::is_lock_free() is not a constexpr and/or static function?
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: Trouble with gcc -B option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Trouble with gcc -B option
  • From: "Feuerbacher, Alan" <AFeuerbacher@xxxxxxxxxxxxxxxx>
• Re: Failing to compile GCC 4.7.1 on Windows with MinGW.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Failing to compile GCC 4.7.1 on Windows with MinGW.
  • From: "farmdve data.bg" <farmdve@xxxxxxx>
• Failing to compile GCC 4.7.1 on Windows with MinGW.
  • From: "farmdve data.bg" <farmdve@xxxxxxx>
• Re: Shared Memory Access Problem
  • From: Ángel González <keisial@xxxxxxxxx>
• Why atomic::is_lock_free() is not a constexpr and/or static function?
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: x86 procedure calling convention.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• x86 procedure calling convention.
  • From: phi gcc <phi.gcc@xxxxxxxxx>
• Re: Trouble with gcc -B option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Trouble with gcc -B option
  • From: "Feuerbacher, Alan" <AFeuerbacher@xxxxxxxxxxxxxxxx>
• i686-pc-mingw32-gcc: error: unrecognized option '-pthread'
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• compile fail with -I option for gcc 4.7.1
  • From: mei yuhua <progmei@xxxxxxxxx>
• Re: Compiler can not find headers when used '--with-gxx-include-dir'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compiler can not find headers when used '--with-gxx-include-dir'
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: Compiler can not find headers when used '--with-gxx-include-dir'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Compiler can not find headers when used '--with-gxx-include-dir'
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: questions about multilib support for mips
  • From: mei yuhua <progmei@xxxxxxxxx>
• Re: Undefined symbol warning_at when loading gcc-python-plugin
  • From: David Narvaez <david.narvaez@xxxxxxxxxxxx>
• Re: -static with -mieee-fp flags Possible bug?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -static with -mieee-fp flags Possible bug?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• -static with -mieee-fp flags Possible bug?
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Re: cpp and ##: spurious blank causes "error: exponent has no digits"
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• cpp and ##: spurious blank causes "error: exponent has no digits"
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: Undefined symbol warning_at when loading gcc-python-plugin
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Undefined symbol warning_at when loading gcc-python-plugin
  • From: David Narvaez <david.narvaez@xxxxxxxxxxxx>
• Re: Spec strings to pass ʽ-rpathʼ for each ʽ-Lʼ
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Spec strings to pass ‘-rpath’ for each ‘-L’
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Re: Spec strings to pass ʽ-rpathʼ for each ʽ-Lʼ
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Spec strings to pass ‘-rpath’ for each ‘-L’
  • From: ludo@xxxxxxx (Ludovic Courtès)
• lxr for gcc
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: Spec strings to pass ʽ-rpathʼ for each ʽ-Lʼ
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Spec strings to pass ‘-rpath’ for each ‘-L’
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Spec strings to pass ‘-rpath’ for each ‘-L’
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Compiling GCC for Android (ARM)
  • From: "farmdve data.bg" <farmdve@xxxxxxx>
• Re: extern "C" for libstdc++ building
  • From: Dan Schatzberg <dschatz@xxxxxx>
• Re: extern "C" for libstdc++ building
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• extern "C" for libstdc++ building
  • From: Dan Schatzberg <dschatz@xxxxxx>
• Re: Shared Memory Access Problem
  • From: Bob Furber <bob.furber@xxxxxxx>
• Re: Shared Memory Access Problem
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Shared Memory Access Problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: callgrind and sin/cos under GCC
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Strict aliasing violation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: callgrind and sin/cos under GCC
  • From: Pete Flugstad <pete.flugstad@xxxxxxxxx>
• Re: Shared Memory Access Problem
  • From: Bob Furber <burnsmicro@xxxxxxxxx>
• Re: Strict aliasing violation?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Strict aliasing violation?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: questions about multilib support for mips
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: nested function question
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: questions about multilib support for mips
  • From: mei yuhua <progmei@xxxxxxxxx>
• Re: Strict aliasing violation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: callgrind and sin/cos under GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: callgrind and sin/cos under GCC
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Strict aliasing violation?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Strict aliasing violation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: callgrind and sin/cos under GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• callgrind and sin/cos under GCC
  • From: Pete Flugstad <pete.flugstad@xxxxxxxxx>
• Re: questions about multilib support for mips
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: questions about multilib support for mips
  • From: mei yuhua <progmei@xxxxxxxxx>
• Re: nested function question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: nested function question
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• nested function question
  • From: Aurelien Buhrig <aurelien.buhrig.gcc@xxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: gcc option help
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: __ has_include() macro implementation can be accepted in GCC?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: questions about multilib support for mips
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• struct, union and field alignment in gcc
  • From: mike <mikereape@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: __ has_include() macro implementation can be accepted in GCC?
  • From: niXman <i.nixman@xxxxxxxxx>
• questions about multilib support for mips
  • From: mei yuhua <progmei@xxxxxxxxx>
• gcc option help
  • From: lei yang <yanglei.fage@xxxxxxxxx>
• More Info - (Must Read)
  • From: "Felice Neely" <guzman@xxxxxxxx>
• Using dwarf2 for 32bit target for multilib MinGW
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: __ has_include() macro implementation can be accepted in GCC?
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• It Releases Breaking Developments, Bullish Indicators
  • From: "Gloria Drake" <sysadmin@xxxxxxxxxxxxxxxxxxx>
• Re: __ has_include() macro implementation can be accepted in GCC?
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: __ has_include() macro implementation can be accepted in GCC?
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• __ has_include() macro implementation can be accepted in GCC?
  • From: niXman <i.nixman@xxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: PowerPC long double
  • From: Ira Hill <ijh3@xxxxxxx>
• Re: Shared Memory Access Problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Shared Memory Access Problem
  • From: Bob Furber <burnsmicro@xxxxxxxxx>
• Re: PowerPC long double
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• PowerPC long double
  • From: Ira Hill <ijh3@xxxxxxx>
• Re: How to utilize the CVTDQ2PD instruction?
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Re: How to utilize the CVTDQ2PD instruction?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: libgcov issue in GCC_3.23
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: libgcov issue in GCC_3.23
  • From: Georgy Sebastian Pullolickal <georgysebastian@xxxxxxxxx>
• Re: How to utilize the CVTDQ2PD instruction?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: libgcov issue in GCC_3.23
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Installing multiple versions of GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• How to utilize the CVTDQ2PD instruction?
  • From: Henrik Mannerström <henrik.mannerstrom@xxxxxxxxx>
• Re: Installing multiple versions of GCC
  • From: Georg-Johann Lay <gjl@xxxxxxxxxxx>
• libgcov issue in GCC_3.23
  • From: Georgy Sebastian Pullolickal <georgysebastian@xxxxxxxxx>
• g++ dumps
  • From: Денис Зинченко <denxc@xxxxxxxxx>
• Re: Instrumented functions and line numbers
  • From: Patrick Oppenlander <pattyo.lists@xxxxxxxxx>
• Re: Incorrect dereference in argument passage
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Incorrect dereference in argument passage
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: Incorrect dereference in argument passage
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Incorrect dereference in argument passage
  • From: Arthur Schwarz <aschwarz1309@xxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Instrumented functions and line numbers
  • From: Malte Forkel <malte.forkel@xxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Jeff Kenton <jkenton@xxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: trunk build error after revision 189603
  • From: JonY <jon_y@xxxxxxxxxxxxxxxxxxxxx>
• Re: trunk build error after revision 189603
  • From: niXman <i.nixman@xxxxxxxxx>
• CFLAGS_FOR_TARGET / CXX_FLAGS_FOR_TARGET broken?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• Re: Instrumented functions and line numbers
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: The impact of march=
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Generate Function without Prologue and Epilogue
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• Generate Function without Prologue and Epilogue
  • From: Xin Tong <xerox.time.tech@xxxxxxxxx>
• The impact of march=
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: undefined symbol : pow arm gcc compiler
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• undefined symbol : pow arm gcc compiler
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Re: Cannot use static linking with librt.a?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Cannot use static linking with librt.a?
  • From: Hei Chan <structurechart@xxxxxxxxx>