Re: git conversion of GCC wwwdocs repository

2019-10-04 Thread Thomas Schwinge
Hi Joseph! On 2019-09-30T19:56:39+, Joseph Myers wrote: > As far as I can tell from the discussion, people are happy with the > version of the conversion using @gcc.gnu.org addresses. When shall we (do > a final conversion if there are any commits postdating that one and) > switch over to

Re: compatibility of structs/unions/enums in the middle end

2019-10-04 Thread Richard Biener
On Wed, Oct 2, 2019 at 8:24 PM Uecker, Martin wrote: > > Am Mittwoch, den 02.10.2019, 17:37 +0200 schrieb Richard Biener: > > On October 2, 2019 3:55:43 PM GMT+02:00, "Uecker, Martin" > > > > wrote: > > > Am Mittwoch, den 02.10.2019, 15:12 +0200 schrieb Richard Biener: > > > > On Wed, Oct 2, 201

Re: [EXT] Re: Modifying types during optimization

2019-10-04 Thread Richard Biener
On Wed, Oct 2, 2019 at 8:50 PM Gary Oblock wrote: > > On 10/2/19 3:15 AM, Richard Biener wrote: > > External Email > > > > -- > > On Wed, Oct 2, 2019 at 1:43 AM Gary Oblock wrote: > >> I'm working on structure reorganization opti

Re: compatibility of structs/unions/enums in the middle end

2019-10-04 Thread Uecker, Martin
Am Freitag, den 04.10.2019, 12:29 +0200 schrieb Richard Biener: > On Wed, Oct 2, 2019 at 8:24 PM Uecker, Martin > wrote: > > > > Am Mittwoch, den 02.10.2019, 17:37 +0200 schrieb Richard Biener: > > > > ... > > > > > > > Oh, and LTO does _not_ merge types declared inside a function, > > > > > s

Re: compatibility of structs/unions/enums in the middle end

2019-10-04 Thread Richard Biener
On Fri, Oct 4, 2019 at 1:55 PM Uecker, Martin wrote: > > Am Freitag, den 04.10.2019, 12:29 +0200 schrieb Richard Biener: > > On Wed, Oct 2, 2019 at 8:24 PM Uecker, Martin > > wrote: > > > > > > Am Mittwoch, den 02.10.2019, 17:37 +0200 schrieb Richard Biener: > > > > > > > ... > > > > > > > > > Oh

Re: compatibility of structs/unions/enums in the middle end

2019-10-04 Thread Uecker, Martin
Am Freitag, den 04.10.2019, 14:28 +0200 schrieb Richard Biener: > On Fri, Oct 4, 2019 at 1:55 PM Uecker, Martin > wrote: > > > > Am Freitag, den 04.10.2019, 12:29 +0200 schrieb Richard Biener: > > > On Wed, Oct 2, 2019 at 8:24 PM Uecker, Martin > > > wrote: > > > > > > > > Am Mittwoch, den 02.1

SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)

2019-10-04 Thread Steve Ellcey
I am curious if anyone has tried running 'peak' SPEC 2017 numbers using profiling. Now that the cactus lto bug has been fixed I can run all the SPEC intrate and fprate benchmarks with '-Ofast -flto -march=native' on my aarch64 box and get accurate results but when I try to use these options along

Re: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)

2019-10-04 Thread Bill Schmidt
On 10/4/19 10:13 AM, Steve Ellcey wrote: I am curious if anyone has tried running 'peak' SPEC 2017 numbers using profiling. Now that the cactus lto bug has been fixed I can run all the SPEC intrate and fprate benchmarks with '-Ofast -flto -march=native' on my aarch64 box and get accurate results

Re: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)

2019-10-04 Thread Thomas Koenig
Am 04.10.19 um 22:58 schrieb Bill Schmidt: Have you tried -fno-strict-aliasing?  There is a known issue with spec_qsort() that affects both of these benchmarks.  See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83201. Reading that bug report (another refusal to correct a glaring standards v

Re: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)

2019-10-04 Thread Steve Ellcey
On Fri, 2019-10-04 at 15:58 -0500, Bill Schmidt wrote: > > > Has anyone else seen these failures? > > > Have you tried -fno-strict-aliasing? There is a known issue with > spec_qsort() that affects both of these benchmarks. See > https://urldefense.proofpoint.com/v2/url?u=https-3A__gcc.gnu.o

gcc-8-20191004 is now available

2019-10-04 Thread gccadmin
Snapshot gcc-8-20191004 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20191004/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8