public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jason Mancini <jayrusman@hotmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: gcc9 snapshot 20190414 is 30x slower than gcc 6.3
Date: Wed, 17 Apr 2019 08:38:00 -0000	[thread overview]
Message-ID: <CAH6eHdS8XW+MEVn0FkA+a7aDjq-X104vtUUE3zA9wm=jdFDxGg@mail.gmail.com> (raw)
In-Reply-To: <c64c9a5e0b3edd951c286aa3e22d6ab90b54b4a3.camel@mengyan1223.wang>

On Wed, 17 Apr 2019 at 03:20, Xi Ruoyao wrote:
>
> On 2019-04-17 02:09 +0000, Jason Mancini wrote:
> > > Using gcc 6.3, my C++ source file compiles in 1m2s with -O0.  With snapshot
> > > 20190414 (compiled with --disable-checking
> > > and -O2 and make install-strip), it takes 31 minutes to compile the same
> > > file with -O0.  Have I overlooked disabling some
> > > snapshot self-checking code?  Are there known configuration mistakes that
> > > could result in this sort of performance
> > > degradation?  Thanks!  It will take a while to go back and try other gcc 6,
> > > 7, 8, and 9 snapshots to collect points of reference.
> > > Both are pretty heavy on memory, gcc6 uses 3.7G and gcc9 uses 5.4G for this
> > > file.  There's a lot of templatized headers.
> >
> > Latest data points:
> > gcc-6.3/6.4 take about 43 seconds
> > gcc-7.2 takes 30 minutes
> > gcc-8.2 takes 27 minutes
> > gcc-9.0 takes 31 minutes (snapshot 20190414)
> > clang 6.0.1/7.01 take about 31 seconds
> >
> > This is frustrating, as I'm going to have to capitulate to using clang here
> > for a very large user base.  We've been a gcc
> > shop for decades.
>
> We'll never know why unless you can give a testcase to reproduce this issue.

Even better would be a bug report.

The chances of it ever getting fixed are much higher if we know
there's a problem. If you just complain that you have to switch to
clang then nothing will change. And if you'd told us two years ago
that your program started compiling 40 times slower, maybe it would
have been fixed already.

  reply	other threads:[~2019-04-17  8:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  0:28 Jason Mancini
2019-04-17  2:10 ` Jason Mancini
2019-04-17  2:20   ` Xi Ruoyao
2019-04-17  8:38     ` Jonathan Wakely [this message]
2019-04-17  9:07       ` Segher Boessenkool
2019-04-18 16:06       ` Jason Mancini
2019-04-18 19:07         ` Segher Boessenkool
2019-04-18 19:38           ` Jeff Law
2019-04-19  2:03             ` Jason Mancini
2019-04-22 22:01             ` Jason Mancini
2019-04-22 22:17               ` Jason Mancini
2019-04-23  0:18             ` Jason Mancini
2019-04-23 12:58               ` Jonathan Wakely
2019-04-29 20:33               ` Jason Mancini
2019-05-01 13:31                 ` C11, <stdatomic.h> and atomic pointers Chris Hall
2019-05-01 14:15                   ` Martin Sebor
2019-05-02  7:54                     ` Jonathan Wakely
2019-06-20 11:28                   ` __STDC_NO_THREADS__ and late model gcc/glibc Chris Hall
2019-06-20 12:17                     ` Jonathan Wakely
2019-06-21  9:39                       ` Chris Hall
2019-06-21  9:51                         ` Jonathan Wakely
2020-01-06 15:09                     ` Function returning struct on x86_64 (at least) Chris Hall
2020-01-06 15:19                       ` Marc Glisse
2020-01-07 16:20                         ` Chris Hall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH6eHdS8XW+MEVn0FkA+a7aDjq-X104vtUUE3zA9wm=jdFDxGg@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jayrusman@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).