From: "Andreas Krebbel" <Andreas.Krebbel@de.ibm.com>
To: gcc-patches@gcc.gnu.org
Subject: [PING^3] INSN attribute to enable/disable alternatives
Date: Tue, 20 Nov 2007 17:10:00 -0000 [thread overview]
Message-ID: <20071120150351.GA8440@homer.boeblingen.de.ibm.com> (raw)
Hi,
these 3 patches introduce a new special attribute to be used in INSN
definitions in order to enable or disable certain INSN alternatives.
I think this comes in quite handy when enhancing a back end with new
instructions. I've posted these patches in stage 2 and really need
them to go in since I've a few back end patches relying on that
feature.
Ian already had a look. Although the feature was considered
reasonable I can understand that he was unhappy with the genattr
changes in patch 3 introducing new attribute 'getter' functions with
an additional 'alternative' parameter. These changes are the part
which unfortunately make the introduction of that simple feature look
rather complicated.
I would be happy to rework that part of the patch if someone comes up
with a better/simpler solution. Any suggestions?!
Here is the mail from Ian:
http://gcc.gnu.org/ml/gcc/2007-09/msg00458.html
[PATCH 1/3] S/390: New `enabled' insn attribute
http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01908.html
[PATCH 2/3] reload,recog: New `enabled' insn attribute
http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01909.html
[PATCH 3/3] genattr: New `enabled' insn attribute
http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01910.html
Bye,
-Andreas-
next reply other threads:[~2007-11-20 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 17:10 Andreas Krebbel [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 14:03 Andreas Krebbel
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=20071120150351.GA8440@homer.boeblingen.de.ibm.com \
--to=andreas.krebbel@de.ibm.com \
--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).