From: Paolo Bonzini <bonzini@gnu.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PING] Hookization patches (and small related arm/m32c stuff)
Date: Mon, 27 Apr 2009 16:42:00 -0000 [thread overview]
Message-ID: <49F5DEEF.3040409@gnu.org> (raw)
I'm pinging them all, some of them are actually just from last Thursday.
The newest are included either for reference, or because the
PROMOTE_FUNCTION_MODE series actually cures PR39227.
Paolo
Hookize (partially) GO_IF_LEGITIMATE_ADDRESS
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01845.html
[arm] remove bogus conditional in PROMOTE_FUNCTION_MODE
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01732.html
Hookize PROMOTE_FUNCTION_MODE with provision for ARM HFmode:
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01631.html
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01632.html
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01633.html
Remove duplicate implementation of target hooks in m32c
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01561.html
[PATCH] Hookize LEGITIMIZE_ADDRESS
http://gcc.gnu.org/ml/gcc-patches/2009-04/msg01297.html
next reply other threads:[~2009-04-27 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 16:42 Paolo Bonzini [this message]
2009-04-27 22:57 ` DJ Delorie
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=49F5DEEF.3040409@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@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).