public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64928] [11 Regression] Inordinate cpu time and memory usage in "phase opt and generate" with -ftest-coverage -fprofile-arcs
Date: Thu, 28 Sep 2023 07:06:08 +0000	[thread overview]
Message-ID: <bug-64928-4-pwulgCtYBI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64928-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|rguenth at gcc dot gnu.org         |unassigned at gcc dot gnu.org
      Known to fail|                            |11.4.0
                 CC|                            |rguenth at gcc dot gnu.org
      Known to work|                            |12.1.0, 13.1.0, 14.0
             Status|ASSIGNED                    |NEW
            Summary|[11/12/13/14 Regression]    |[11 Regression] Inordinate
                   |Inordinate cpu time and     |cpu time and memory usage
                   |memory usage in "phase opt  |in "phase opt and generate"
                   |and generate" with          |with -ftest-coverage
                   |-ftest-coverage             |-fprofile-arcs
                   |-fprofile-arcs              |

--- Comment #44 from Richard Biener <rguenth at gcc dot gnu.org> ---
I tried the first input file with GCC 13.2 and on a Ryzen 9 7900X get a memory
usage of 105MB and 1.1s compile-time.  The larger testcase needs 360MB peak
and 6.3s to compile.  Both with mostly flat -ftime-report profile.

Upping to -O2 shows same memory peak but 13.1s for the larger testcase.  We
then see

 PRE                                :   2.09 ( 16%)   0.01 (  1%)   2.15 ( 15%)
  288k (  0%)

as the biggest thing sticking out (similar for the small testcase).

I think we've come a long way here.  GCC 12.3 behaves the same.  For GCC 11.4
the larger testcase at -O2 I stopped after 3 minutes, the small testcase at -O1
takes 44s and 5GB memory.

Fixed for GCC 12+, I'm not going to look at identifying what to backport (I
usually backported compile-time/memory-usage improvements when reasonable, so
I suspect this was a bigger change).

  parent reply	other threads:[~2023-09-28  7:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 21:09 [Bug other/64928] New: unreasonable " lucier at math dot purdue.edu
2015-02-03 21:11 ` [Bug other/64928] Inordinate " lucier at math dot purdue.edu
2015-02-03 21:33 ` pinskia at gcc dot gnu.org
2015-02-03 21:35 ` pinskia at gcc dot gnu.org
2015-02-03 21:49 ` lucier at math dot purdue.edu
2015-02-06  5:07 ` lucier at math dot purdue.edu
2015-02-06  5:08 ` lucier at math dot purdue.edu
2015-02-09 14:31 ` [Bug middle-end/64928] [4.8/4.9/5 Regression] " rguenth at gcc dot gnu.org
2015-02-09 15:07 ` rguenth at gcc dot gnu.org
2015-02-16 19:57 ` law at redhat dot com
2015-03-05 17:22 ` rguenth at gcc dot gnu.org
2015-03-05 23:07 ` steven at gcc dot gnu.org
2015-03-06  0:45 ` law at redhat dot com
2015-03-06 10:53 ` rguenth at gcc dot gnu.org
2015-03-06 12:35 ` rguenth at gcc dot gnu.org
2015-03-06 12:47 ` rguenth at gcc dot gnu.org
2015-03-06 12:53 ` rguenth at gcc dot gnu.org
2015-03-06 13:01 ` rguenth at gcc dot gnu.org
2015-03-18 12:54 ` rguenth at gcc dot gnu.org
2015-05-20 14:49 ` [Bug middle-end/64928] [4.8/4.9/5/6 " wellnhofer at aevum dot de
2015-05-20 14:49 ` wellnhofer at aevum dot de
2015-06-23  8:19 ` rguenth at gcc dot gnu.org
2015-06-26 19:56 ` [Bug middle-end/64928] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:28 ` jakub at gcc dot gnu.org
2020-09-29  0:14 ` [Bug middle-end/64928] [8/9/10/11 " lucier at math dot purdue.edu
2020-09-29  7:09 ` rguenth at gcc dot gnu.org
2020-09-29 12:17 ` lucier at math dot purdue.edu
2020-09-29 13:06 ` rguenther at suse dot de
2021-03-10  2:10 ` lucier at math dot purdue.edu
2021-03-10  2:13 ` lucier at math dot purdue.edu
2021-03-10  9:47 ` rguenth at gcc dot gnu.org
2021-03-10 14:16 ` lucier at math dot purdue.edu
2021-03-10 15:06 ` rguenth at gcc dot gnu.org
2021-05-14  9:47 ` [Bug middle-end/64928] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug middle-end/64928] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug middle-end/64928] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-09-28  7:06 ` rguenth at gcc dot gnu.org [this message]
2023-10-02  0:26 ` [Bug middle-end/64928] [11 " lucier at math dot purdue.edu
2023-10-04  6:39 ` 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-64928-4-pwulgCtYBI@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).