gcc-9-20200807 is now available

2020-08-07 Thread GCC Administrator via Gcc
Snapshot gcc-9-20200807 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20200807/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

PowerPC long double Mangling

2020-08-07 Thread Michael Meissner via Gcc
One issue with doing the transition is what mangling should be used with the new long double. At the moment, the current mangling is: long double "g" __float128 "u9__ieee128" __ibm128"g" Obviously this will have to change in the future. It is unfortunate

Changes to allow PowerPC to change the long double type to use the IEEE 128-bit floating point format

2020-08-07 Thread Michael Meissner via Gcc
I want to discuss changes that I think we need to make across the open source toochain to allow us to change the long double type on PowerPC hardware from using the IBM extended double (i.e. a pair of doubles) to the IEEE 128-bit format defined in IEEE 754. I wasn't sure whom to address this to, s

Re: Coding style for C++ constructs going forward

2020-08-07 Thread Christian Biesinger via Gcc
On Fri, Aug 7, 2020 at 9:06 AM Luis Machado via Gdb wrote: > > Hi, > > cc-ing the GCC mailing list, as we may want to use the same coding style > for GDB and GCC. > > Yesterday I brought this topic up on IRC. I notice we started using more > and more the "auto" keyword. In some cases, this is actu

Re: Coding style for C++ constructs going forward

2020-08-07 Thread Jonathan Wakely via Gcc
On Fri, 7 Aug 2020 at 15:08, Luis Machado via Gcc wrote: > > Hi, > > cc-ing the GCC mailing list, as we may want to use the same coding style > for GDB and GCC. > > Yesterday I brought this topic up on IRC. I notice we started using more > and more the "auto" keyword. In some cases, this is actual

Re: Coding style for C++ constructs going forward

2020-08-07 Thread Jakub Jelinek via Gcc
On Fri, Aug 07, 2020 at 07:56:03AM -0700, Joel Brobecker wrote: > > Pedro has pointed out LLVM's coding standards for "auto", which we may or > > may not want to follow/adopt: > > https://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-readable Also see the https://gc

Re: Coding style for C++ constructs going forward

2020-08-07 Thread Joel Brobecker
Hi Luis, > cc-ing the GCC mailing list, as we may want to use the same coding style for > GDB and GCC. > > Yesterday I brought this topic up on IRC. I notice we started using more and > more the "auto" keyword. In some cases, this is actually useful and makes > the code a bit more compact. GDB ha

Coding style for C++ constructs going forward

2020-08-07 Thread Luis Machado via Gcc
Hi, cc-ing the GCC mailing list, as we may want to use the same coding style for GDB and GCC. Yesterday I brought this topic up on IRC. I notice we started using more and more the "auto" keyword. In some cases, this is actually useful and makes the code a bit more compact. GDB has been using

Re: Has FSF stopped processing copyright paperwork?

2020-08-07 Thread Richard Biener via Gcc
On Fri, Aug 7, 2020 at 3:14 PM H.J. Lu via Gcc wrote: > > On Tue, May 5, 2020 at 6:42 PM Kaylee Blake wrote: > > > > On 2/5/20 11:49 pm, H.J. Lu wrote: > > > On Wed, Mar 18, 2020 at 6:46 PM Kaylee Blake via Binutils > > > wrote: > > >> > > >> On 19/3/20 12:02 pm, H.J. Lu wrote: > > >>> Kaylee, i

Has FSF stopped processing copyright paperwork?

2020-08-07 Thread H.J. Lu via Gcc
On Tue, May 5, 2020 at 6:42 PM Kaylee Blake wrote: > > On 2/5/20 11:49 pm, H.J. Lu wrote: > > On Wed, Mar 18, 2020 at 6:46 PM Kaylee Blake via Binutils > > wrote: > >> > >> On 19/3/20 12:02 pm, H.J. Lu wrote: > >>> Kaylee, is your paper work with FSF in order? I will submit the updated > >>> patc