public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113910] [12/13 Regression] Factor 15 slowdown compiling AMDGPUDisassembler.cpp on SPARC
Date: Wed, 14 Feb 2024 20:07:48 +0000	[thread overview]
Message-ID: <bug-113910-4-pCU1YV5ghN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113910-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113910

--- Comment #15 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
> The regression should be fixed, can you check we're now no longer slower on
> trunk?  (either use a release checking build or use -fno-checking which should
> get you reasonably close)

I've done a --enable-checking=release build on trunk and compare compile
times of the -save-temps with g++ 11.4.0:

$ time cc1plus -fpreprocessed AMDGPUDisassembler.cpp.ii -quiet -mcpu=v9 -O
-std=c++17 -o AMDGPUDisassembler.cpp.s

* 11.4.0:

real        2:04.33
user        2:03.86
sys            0.30

* 14.0.1:

real        2:17.58
user        2:16.47
sys            0.87

  parent reply	other threads:[~2024-02-14 20:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 15:37 [Bug tree-optimization/113910] New: [12/13/14 regression] " ro at gcc dot gnu.org
2024-02-13 15:38 ` [Bug tree-optimization/113910] " ro at gcc dot gnu.org
2024-02-13 15:39 ` ro at gcc dot gnu.org
2024-02-13 15:40 ` ro at gcc dot gnu.org
2024-02-13 15:55 ` pinskia at gcc dot gnu.org
2024-02-13 16:04 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-14  9:36 ` rguenth at gcc dot gnu.org
2024-02-14  9:37 ` rguenth at gcc dot gnu.org
2024-02-14  9:44 ` rguenth at gcc dot gnu.org
2024-02-14 10:05 ` rguenth at gcc dot gnu.org
2024-02-14 10:26 ` rguenth at gcc dot gnu.org
2024-02-14 11:32 ` rguenth at gcc dot gnu.org
2024-02-14 11:41 ` rguenth at gcc dot gnu.org
2024-02-14 14:51 ` rguenth at gcc dot gnu.org
2024-02-14 14:51 ` cvs-commit at gcc dot gnu.org
2024-02-14 15:11 ` [Bug tree-optimization/113910] [12/13 Regression] " rguenth at gcc dot gnu.org
2024-02-14 20:07 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2024-02-15 10:43 ` rguenth at gcc dot gnu.org
2024-02-16 12:57 ` rguenth at gcc dot gnu.org
2024-03-21 11:49 ` cvs-commit at gcc dot gnu.org
2024-06-04  8:07 ` [Bug tree-optimization/113910] [12 " cvs-commit at gcc dot gnu.org
2024-06-04  8:09 ` rguenth at gcc dot gnu.org

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=bug-113910-4-pCU1YV5ghN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).