public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102852] [12 Regression] Compile time hog since r12-4421-g0bd68793921ecf3b
Date: Wed, 20 Oct 2021 06:38:37 +0000	[thread overview]
Message-ID: <bug-102852-4-SMpQca8jNK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102852-4@http.gcc.gnu.org/bugzilla/>

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbglaw@lug-owl.de

--- Comment #1 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
This seems to have been fixed by the loop threading restrictions I just
committed:

$ time ./xgcc -B./ a.c -O3 -c

real    0m0.114s
user    0m0.100s
sys     0m0.013s

However, this looks suspicious, so please leave it open while I investigate. 
The --param's I removed are obviously having deleterious effects.

This may be the same problem Jan-Benedict reported with compiling the Linux
kernel.

Thanks for distilling and reporting this.

  parent reply	other threads:[~2021-10-20  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  6:27 [Bug tree-optimization/102852] New: " marxin at gcc dot gnu.org
2021-10-20  6:27 ` [Bug tree-optimization/102852] " marxin at gcc dot gnu.org
2021-10-20  6:38 ` aldyh at gcc dot gnu.org [this message]
2021-10-20  7:10 ` aldyh at gcc dot gnu.org
2021-10-20  7:11 ` marxin at gcc dot gnu.org
2021-10-20  7:18 ` aldyh 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-102852-4-SMpQca8jNK@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).