April 2018 Archives by thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Sun Apr 1 10:06:00 GMT 2018
Ending: Mon Apr 30 19:55:00 GMT 2018
Messages: 202

• Gcc bugzilla is down   Thomas König
  • Gcc bugzilla is down   Eric Gallager
• Successful bootstrap and install of gcc (GCC) 7.3.0 on sparc64-unknown-linux-gnu   Aaro Koskinen
• why C++ cannot alias an inline function, C can ?   Jason Vas Dias
  • why C++ cannot alias an inline function, C can ?   Max Filippov
    • why C++ cannot alias an inline function, C can ?   Jason Vas Dias
      • why C++ cannot alias an inline function, C can ?   Max Filippov
      • why C++ cannot alias an inline function, C can ?   Marc Glisse
  • why C++ cannot alias an inline function, C can ?   Jason Merrill
• GSoC (Improvements to GCC on Windows)   JonY
  • GSoC (Improvements to GCC on Windows)   Ko Phyo
    • GSoC (Improvements to GCC on Windows)   Liu Hao
      • GSoC (Improvements to GCC on Windows)   Ko Phyo
• "file name" vs "filename"   Gerald Pfeifer
  • "file name" vs "filename"   Joel Sherrill
    • "file name" vs "filename"   Sandra Loosemore
      • "file name" vs "filename"   Martin Sebor
  • "file name" vs "filename"   Joseph Myers
    • "file name" vs "filename"   Vincent Lefevre
• gcc-8-20180401 is now available   gccadmin@gcc.gnu.org
• 代开发票   林先生
• [cpp,doc] PATCH for Re: CPP documentation minor typo   Gerald Pfeifer
• Internal compiler error building libstdc++ for vax   coypu@sdf.org
  • Internal compiler error building libstdc++ for vax   Jeff Law
    • Internal compiler error building libstdc++ for vax   Maciej W. Rozycki
      • Internal compiler error building libstdc++ for vax   Jeff Law
• count in spill_regs   Vladimir Makarov
• where should C++ options be documented?   Martin Sebor
  • where should C++ options be documented?   David Brown
    • where should C++ options be documented?   Martin Sebor
  • where should C++ options be documented?   Jason Merrill
    • where should C++ options be documented?   Martin Sebor
      • where should C++ options be documented?   Nathan Sidwell
      • where should C++ options be documented?   Martin Sebor
      • where should C++ options be documented?   Jason Merrill
      • where should C++ options be documented?   Martin Sebor
      • where should C++ options be documented?   Jason Merrill
  • where should C++ options be documented?   Eric Gallager
• QBU: [gcc@gcc.gnu.org] 03-04-2018 10:33:07 Your reputation is at stake   Renata Tweten
• Google Summer of Code 2018: Call for mentors and ideas   Peryt, Sebastian
  • Google Summer of Code 2018: Call for mentors and ideas   Martin Jambor
• Patching the GCC build system to build MPICH and OpenCoarrays   Richard Biener
  • Patching the GCC build system to build MPICH and OpenCoarrays   Damian Rouson
    • Patching the GCC build system to build MPICH and OpenCoarrays   Richard Biener
      • Patching the GCC build system to build MPICH and OpenCoarrays   Damian Rouson
      • Patching the GCC build system to build MPICH and OpenCoarrays   Richard Biener
• [wwwdocs] PATCH for Re: Remove *.mirror.babylon.network   Gerald Pfeifer
• gcc-6-20180404 is now available   gccadmin@gcc.gnu.org
• how to generate - "procedure linkage table" for MIPS   Maciej W. Rozycki
• Vincent Forbes's invitation is waiting for your response   Vincent Forbes via Nextdoor
• gcc-7-20180405 is now available   gccadmin@gcc.gnu.org
• GCC changes for Fedora + riscv64   Jeff Law
  • GCC changes for Fedora + riscv64   Richard W.M. Jones
  • GCC changes for Fedora + riscv64   Jim Wilson
    • GCC changes for Fedora + riscv64   Jeff Law
      • GCC changes for Fedora + riscv64   Stef O'Rear
      • GCC changes for Fedora + riscv64   Jeff Law
      • GCC changes for Fedora + riscv64   Kito Cheng
      • GCC changes for Fedora + riscv64   Andreas Schwab
      • GCC changes for Fedora + riscv64   Kito Cheng
      • GCC changes for Fedora + riscv64   Jeff Law
      • GCC changes for Fedora + riscv64   Jeff Law
      • GCC changes for Fedora + riscv64   Richard W.M. Jones
      • GCC changes for Fedora + riscv64   Jeff Law
• gcc-8-20180408 is now available   gccadmin@gcc.gnu.org
• Which compiler version should we use to compile Cadence Compilers   Rogerio de Souza Moraes
  • Which compiler version should we use to compile Cadence Compilers   Jonathan Wakely
• libmvec in gcc to have vector math in fortran   Szabolcs Nagy
  • libmvec in gcc to have vector math in fortran   Janne Blomqvist
    • libmvec in gcc to have vector math in fortran   Szabolcs Nagy
      • libmvec in gcc to have vector math in fortran   Jakub Jelinek
      • libmvec in gcc to have vector math in fortran   Richard Biener
      • libmvec in gcc to have vector math in fortran   Richard Biener
      • libmvec in gcc to have vector math in fortran   Richard Biener
      • libmvec in gcc to have vector math in fortran   Szabolcs Nagy
      • libmvec in gcc to have vector math in fortran   Richard Biener
      • libmvec in gcc to have vector math in fortran   Jakub Jelinek
• www.sgi.com/tech/stl/ is gone   Jonathan Wakely
• gcc-6-20180411 is now available   gccadmin@gcc.gnu.org
• Paid-Invoice   amy.lee@zutachusa.info
• Dealing with default recursive procedures in Fortran   Thomas König
  • Dealing with default recursive procedures in Fortran   N.M. Maclaren
  • Dealing with default recursive procedures in Fortran   Ramana Radhakrishnan
  • Dealing with default recursive procedures in Fortran   Janne Blomqvist
  • Dealing with default recursive procedures in Fortran   Michael Matz
• gcc-7-20180412 is now available   gccadmin@gcc.gnu.org
• image studio for you   Ross
• the studio   Ross
• GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Vivek Kinhekar
  • GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Vivek Kinhekar
  • GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Alexander Monakov
    • GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Vivek Kinhekar
      • GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Vivek Kinhekar
      • GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction   Jakub Jelinek
• Fortran array slices and -frepack-arrays   Wilco Dijkstra
  • Fortran array slices and -frepack-arrays   Bin.Cheng
    • Fortran array slices and -frepack-arrays   Wilco Dijkstra
• Display priority in "Serious" bugs for gcc 8 from web page   Thomas Koenig
• gcc-8-20180415 is now available   gccadmin@gcc.gnu.org
• gcc Digital signage solution   Anna
• style of code examples in changes.html   Martin Sebor
  • style of code examples in changes.html   David Malcolm
• Register conflicts between output memory address and output register   Matthew Fortune
  • Register conflicts between output memory address and output register   Ulrich Weigand
• Deprecation of powerpc*-*-*spe*   Jakub Jelinek
  • Deprecation of powerpc*-*-*spe*   John Paul Adrian Glaubitz
• Should CET be enabled by default in GCC8   Uros Bizjak
  • Should CET be enabled by default in GCC8   Richard Biener
    • Should CET be enabled by default in GCC8   Jakub Jelinek
      • Should CET be enabled by default in GCC8   H.J. Lu
• gcc-6-20180418 is now available   gccadmin@gcc.gnu.org
• How to get best AVX2 performance from gfortran?   Thomas Koenig
  • How to get best AVX2 performance from gfortran?   Richard Biener
• Request for compiler option to disable multiple declarations in a single statement   Manish Jain
  • Request for compiler option to disable multiple declarations in a single statement   David Brown
    • Request for compiler option to disable multiple declarations in a single statement   Manish Jain
      • Request for compiler option to disable multiple declarations in a single statement   David Brown
  • Request for compiler option to disable multiple declarations in a single statement   Jonathan Wakely
    • Request for compiler option to disable multiple declarations in a single statement   Manish Jain
      • Request for compiler option to disable multiple declarations in a single statement   Jonathan Wakely
  • Request for compiler option to disable multiple declarations in a single statement   Eric Gallager
• Stack protector: leak of guard's address on stack   Thomas Preudhomme
  • Stack protector: leak of guard's address on stack   Thomas Preudhomme
  • Stack protector: leak of guard's address on stack   Jakub Jelinek
    • Stack protector: leak of guard's address on stack   Thomas Preudhomme
      • Stack protector: leak of guard's address on stack   Jakub Jelinek
      • Stack protector: leak of guard's address on stack   Thomas Preudhomme
      • Stack protector: leak of guard's address on stack   Jakub Jelinek
      • Stack protector: leak of guard's address on stack   Thomas Preudhomme
      • Stack protector: leak of guard's address on stack   Florian Weimer
      • Stack protector: leak of guard's address on stack   Maxim Kuvyrkov
      • Stack protector: leak of guard's address on stack   Florian Weimer
• GCC-8 branching   Peryt, Sebastian
  • GCC-8 branching   Jeff Law
• gcc-7-20180419 is now available   gccadmin@gcc.gnu.org
• Telecommunication Users list   Katelyn Smith
• ThreadStack Project: a new innovative open source software for multi-thread computing   Erkam Murat Bozkurt
• Survey assignment in your area..   Ronald Connor
• 正a规代s开发zz票159 8935 4995   赵经理
• Loop fusion.   Toon Moene
  • Loop fusion.   Bin.Cheng
    • Loop fusion.   Richard Biener
      • Loop fusion.   Janne Blomqvist
      • Loop fusion.   Richard Biener
  • Loop fusion.   Richard Biener
    • Loop fusion.   Toon Moene
      • Loop fusion.   Richard Biener
      • Loop fusion.   Toon Moene
• Susietos „Google“ paskyros saugos įspėjimas   Google via gcc
  • Susietos „Google“ paskyros saugos įspėjimas   Google via gcc
  • Susietos „Google“ paskyros saugos įspėjimas   Google via gcc
• Ref. Personal Request.   Mrs. Alison.
• gcc-8-20180422 is now available   gccadmin@gcc.gnu.org
• bug ? : -Wpedantic -Wconversion 'short a=1; a-=1;' complaint   Jason Vas Dias
  • bug ? : -Wpedantic -Wconversion 'short a=1; a-=1;' complaint   Jonathan Wakely
• r9 on ARM32?   Jay K
  • r9 on ARM32?   Richard Earnshaw (lists)
• -g and -fvar-tracking   Sandra Loosemore
  • -g and -fvar-tracking   Jakub Jelinek
    • -g and -fvar-tracking   Sandra Loosemore
• GSoC 2018: Hrishikesh Kulkarni has been selected to work on LTO dumping tool   Martin Jambor
  • GSoC 2018: Hrishikesh Kulkarni has been selected to work on LTO dumping tool   Hrishikesh Kulkarni
    • GSoC 2018: Hrishikesh Kulkarni has been selected to work on LTO dumping tool   Richard Biener
      • GSoC 2018: Hrishikesh Kulkarni has been selected to work on LTO dumping tool   Hrishikesh Kulkarni
      • GSoC 2018: Hrishikesh Kulkarni has been selected to work on LTO dumping tool   Richard Biener
• RFC: bash completion   Martin Liška
  • RFC: bash completion   David Malcolm
    • RFC: bash completion   Martin Liška
    • RFC: bash completion   Martin Liška
• GCC 8.0.1 Status Report (2018-04-25)   Jakub Jelinek
• GCC 9.0.0 Status Report (2018-04-25)   Jakub Jelinek
• GCC 8.1 Release Candidate available from gcc.gnu.org   Jakub Jelinek
  • GCC 8.1 Release Candidate available from gcc.gnu.org   Bill Seurer
  • GCC 8.1 Release Candidate available from gcc.gnu.org   Chung-Ju Wu
• [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
  • [RFC] Deprecate "implicit int" for main() in C++   Andrew Haley
    • [RFC] Deprecate "implicit int" for main() in C++   Jason Merrill
      • [RFC] Deprecate "implicit int" for main() in C++   Andrew Haley
      • [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
      • [RFC] Deprecate "implicit int" for main() in C++   Andrew Haley
      • [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
      • [RFC] Deprecate "implicit int" for main() in C++   David Malcolm
      • [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
      • [RFC] Deprecate "implicit int" for main() in C++   Nathan Sidwell
      • [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
    • [RFC] Deprecate "implicit int" for main() in C++   Jonathan Wakely
      • [RFC] Deprecate "implicit int" for main() in C++   Jason Merrill
• MIPS maintainership   Moore, Catherine
  • MIPS maintainership   Matthew Fortune
• gcc-6-20180425 is now available   gccadmin@gcc.gnu.org
• I'm waiting for your response   Vincent Forbes via Nextdoor
• gcc-7-20180426 is now available   gccadmin@gcc.gnu.org
• Second GCC 8.1 Release Candidate available from gcc.gnu.org   Jakub Jelinek
  • Second GCC 8.1 Release Candidate available from gcc.gnu.org   Bill Seurer
• gcc-8-20180427 is now available   gccadmin@gcc.gnu.org
• Bug or feature - merging linkage declarations from static forced-inline functions   Freddie Chopin
  • Bug or feature - merging linkage declarations from static forced-inline functions   Freddie Chopin
    • Bug or feature - merging linkage declarations from static forced-inline functions   Jonathan Wakely
      • Bug or feature - merging linkage declarations from static forced-inline functions   Nathan Sidwell
• gcc-9-20180429 is now available   gccadmin@gcc.gnu.org
• "position independent" vs "position-independent" in documentation   Jonathan Wakely

Last message date: Mon Apr 30 19:55:00 GMT 2018
Archived on: Sat May 2 13:46:26 GMT 2020

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...