public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/111619] [14 regression] 'make profiledbootstrap' makes 10+ minutes on insn-recog.cc (x86_64-linux)
Date: Thu, 28 Sep 2023 06:08:15 +0000	[thread overview]
Message-ID: <bug-111619-4-NPD6rButC1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111619-4@http.gcc.gnu.org/bugzilla/>

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mliska at suse dot cz,
                   |                            |rguenth at gcc dot gnu.org

--- Comment #9 from Sam James <sjames at gcc dot gnu.org> ---
See also the discussion in
https://inbox.sourceware.org/gcc-patches/41109217-1bf5-b112-e783-8040196fd410@suse.cz/.

  parent reply	other threads:[~2023-09-28  6:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 22:02 [Bug target/111619] New: " slyfox at gcc dot gnu.org
2023-09-27 22:17 ` [Bug target/111619] " slyfox at gcc dot gnu.org
2023-09-27 22:26 ` [Bug rtl-optimization/111619] " pinskia at gcc dot gnu.org
2023-09-27 22:27 ` pinskia at gcc dot gnu.org
2023-09-28  5:18 ` slyfox at gcc dot gnu.org
2023-09-28  5:35 ` slyfox at gcc dot gnu.org
2023-09-28  5:46 ` slyfox at gcc dot gnu.org
2023-09-28  5:49 ` pinskia at gcc dot gnu.org
2023-09-28  5:50 ` slyfox at gcc dot gnu.org
2023-09-28  6:08 ` sjames at gcc dot gnu.org [this message]
2023-09-28  6:48 ` rguenth at gcc dot gnu.org
2023-09-28  7:39 ` [Bug rtl-optimization/111619] " slyfox at gcc dot gnu.org
2023-09-28  8:30 ` 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-111619-4-NPD6rButC1@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).