public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: Marc Glisse via Gcc-help <gcc-help@gcc.gnu.org>
Cc: "Stéphane Glondu" <stephane.glondu@inria.fr>,
	"Marc Glisse" <marc.glisse@inria.fr>,
	sibid@uvic.ca, "Paul Zimmermann" <Paul.Zimmermann@inria.fr>
Subject: Re: slowdown with -std=gnu18 with respect to -std=c99
Date: Thu, 5 May 2022 17:56:26 +0300 (MSK)	[thread overview]
Message-ID: <74dc894-7774-e5bb-81-c5955c94ee4@ispras.ru> (raw)
In-Reply-To: <4d36d96-2de9-f8ac-2d52-ea32b1cc6d9@grove.saclay.inria.fr>

On Thu, 5 May 2022, Marc Glisse via Gcc-help wrote:

> On Thu, 5 May 2022, Stéphane Glondu via Gcc-help wrote:
> 
> > As additional data points, the performance with several versions of gcc
> > (as packaged in Debian testing/unstable):
> >
> >             | gcc-9 | gcc-10 | gcc-11 | gcc-12 |
> > ------------|-------|--------|--------|--------|
> >  -std=c99   | 24    | 23.5   | 23     | 23     |
> >  -std=gnu18 | 43    | 16.8   | 38     | 38     |
> >
> > One can see that the performance stays relatively constant with
> > -std=c99, but varies significantly with -std=gnu18.
> 
> Could you compare with c18 or gnu99, to determine if the issue is with c vs
> gnu (most likely since fma seems important) or 99 vs 18?

Good point. Also could you please add latency metrics, I see that your testing
framework already exposes the '--latency' flag.

I could reproduce a similar though less dramatic slowdown and am investigating.

Alexander

  reply	other threads:[~2022-05-05 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  8:28 Paul Zimmermann
2022-05-03  9:09 ` Alexander Monakov
2022-05-03 11:45   ` Paul Zimmermann
2022-05-03 12:12     ` Alexander Monakov
2022-05-05  8:57   ` Stéphane Glondu
2022-05-05 14:31     ` Stéphane Glondu
2022-05-05 14:41       ` Marc Glisse
2022-05-05 14:56         ` Alexander Monakov [this message]
2022-05-06  7:46           ` Paul Zimmermann
2022-05-06  9:27             ` Alexander Monakov
2022-05-07  6:11               ` Paul Zimmermann
2022-05-11 13:26               ` Alexander Monakov
2022-05-05 17:50         ` Paul Zimmermann

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=74dc894-7774-e5bb-81-c5955c94ee4@ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=Paul.Zimmermann@inria.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=marc.glisse@inria.fr \
    --cc=sibid@uvic.ca \
    --cc=stephane.glondu@inria.fr \
    /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).