From: Michael Matz <matz@suse.de>
To: James E Wilson <wilson@specifixinc.com>
Cc: Richard Sandiford <rsandifo@redhat.com>, gcc@gcc.gnu.org
Subject: Re: RFC: Using mode and code macros in *.md files
Date: Mon, 09 Aug 2004 09:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408090937190.7004@wotan.suse.de> (raw)
In-Reply-To: <411574A9.4000704@specifixinc.com>
Hi,
On Sat, 7 Aug 2004, James E Wilson wrote:
> My first question would be how this affects debugging gcc. Being able to
> match rtl insns to the md pattern for them is important. These macros obscure
> the connection.
...
> If I have an insn that hasn't been recognized, then I have a similar but
> slightly different problem.
Perhaps such problems could be solved by emitting a "preprocessed" .md
file (where every such macro is explicitely expanded) when gcc is not
configured with --disable-checking, or with a special option or even in
every case?
Ciao,
Michael.
next prev parent reply other threads:[~2004-08-09 7:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 18:38 Richard Sandiford
2004-08-08 4:30 ` James E Wilson
2004-08-08 8:43 ` Richard Sandiford
2004-08-09 18:29 ` James E Wilson
2004-08-09 9:02 ` Michael Matz [this message]
2004-08-09 18:09 ` James E Wilson
2004-08-10 8:57 ` Segher Boessenkool
2004-08-23 10:32 ` Zack Weinberg
2004-08-26 21:08 ` Richard Sandiford
2004-08-31 18:19 ` Steve Ellcey
2004-08-31 18:37 ` Richard Sandiford
2004-08-31 19:27 ` Joern Rennecke
2004-08-31 21:04 ` Steve Ellcey
2004-09-01 12:20 ` Joern Rennecke
2004-09-01 18:33 ` Steve Ellcey
2004-09-01 19:00 ` James E Wilson
2004-09-02 10:37 ` Joern Rennecke
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=Pine.LNX.4.58.0408090937190.7004@wotan.suse.de \
--to=matz@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=rsandifo@redhat.com \
--cc=wilson@specifixinc.com \
/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).