public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/104405] Inefficient register allocation on complex arithmetic
Date: Sun, 06 Feb 2022 10:06:33 +0000 [thread overview]
Message-ID: <bug-104405-4-fzJFBUqwH4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104405-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104405
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
CC| |ebotcazou at gcc dot gnu.org
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> But seems to me a simple enough thing that we should be able to handle.
Register allocation is a global problem though, so what happens on toy examples
is not always representative of what happens in real world code because there
is a lot of heuristics involved and you want to tune it for the latter case,
not for the former case.
next prev parent reply other threads:[~2022-02-06 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 7:20 [Bug c/104405] New: " tnfchris at gcc dot gnu.org
2022-02-06 7:29 ` [Bug middle-end/104405] " pinskia at gcc dot gnu.org
2022-02-06 9:19 ` pinskia at gcc dot gnu.org
2022-02-06 9:25 ` [Bug rtl-optimization/104405] " pinskia at gcc dot gnu.org
2022-02-06 9:33 ` tnfchris at gcc dot gnu.org
2022-02-06 9:38 ` pinskia at gcc dot gnu.org
2022-02-06 10:06 ` ebotcazou at gcc dot gnu.org [this message]
2022-02-07 8:44 ` rguenth at gcc dot gnu.org
2022-02-07 9:02 ` ebotcazou 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-104405-4-fzJFBUqwH4@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).