public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52066] IRA and reginfo initialization too expensive
Date: Tue, 09 Oct 2012 20:46:00 -0000 [thread overview]
Message-ID: <bug-52066-4-9cMaKtD0xx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52066-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52066
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #4 from Steven Bosscher <steven at gcc dot gnu.org> 2012-10-09 20:46:39 UTC ---
(In reply to comment #1)
> Patch to inline them. Quite ugly, but I can't use extern inline
> __attribute__((gnu_inline)), because it uses static inline functions, and
> unfortunately some callers of these functions can't include hard-reg-set.h
> (targhooks.c).
Huh, if it's ok to know about reg-classes in targhooks, why is it not also OK
to know about HARD_REG_SET?
prev parent reply other threads:[~2012-10-09 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 13:21 [Bug middle-end/52066] New: " jakub at gcc dot gnu.org
2012-01-31 13:25 ` [Bug middle-end/52066] " jakub at gcc dot gnu.org
2012-01-31 13:57 ` rguenth at gcc dot gnu.org
2012-01-31 15:48 ` jakub at gcc dot gnu.org
2012-10-09 20:46 ` steven at gcc dot gnu.org [this message]
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-52066-4-9cMaKtD0xx@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).