From: fche@redhat.com (Frank Ch. Eigler)
To: dje@transmeta.com (Doug Evans)
Cc: <brolley@redhat.com>, cgen@sources.redhat.com
Subject: Re: [patch][rfa] Ordering insns in hash chain for cgen disassemblers
Date: Thu, 15 Nov 2001 12:42:00 -0000 [thread overview]
Message-ID: <o54rnvhikm.fsf@toenail.toronto.redhat.com> (raw)
Message-ID: <20011115124200.jipMPmR980TNImrpATWP4vf_w_N8ZhRAmpwiY8nQGnA@z> (raw)
In-Reply-To: <15348.168.750723.846784.cygnus.local.cgen@casey.transmeta.com>
dje wrote:
: [...]
: I'm not going to argue for it's removal but fwiw it slightly bothers me.
: I worry it's just going to cause headaches.
Yeah, I worried too, for a little while.
: [While not being the only cause of the worry, question: how will this
: sort play with ifield assertion support when it's added,
What value do you see for the ifield-assertion mechanism (the "(andif
(eq FOO 0) ...)" clauses in derived-operands, right?), beyond what
the encoding fields ("+ (f-FOO 0) ...") can/should provide? As it is,
RTL-rich code appears legal in too many contexts.
: and the user's expectation that things are picked based on order in
: the file. [...]
IMO, such expectations are just desperate measures to try to get
around some cgen limitations. As those limitations start to disappear
(and brolley is going to work on one of the most annoying: insn
encoding special cases), these measures will no longer be needed.
(Thanks for still keeping an eye on cgen!)
- FChE
next prev parent reply other threads:[~2001-11-15 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 13:20 Dave Brolley
2001-10-09 12:09 ` [patch][rfa] Ordering insns in hash chain for cgen disassemblers -- committed Dave Brolley
2001-11-14 12:09 ` Dave Brolley
2001-10-09 16:29 ` [patch][rfa] Ordering insns in hash chain for cgen disassemblers Doug Evans
2001-10-10 2:11 ` Dave Brolley
2001-10-10 3:33 ` Doug Evans
2001-10-10 6:33 ` Dave Brolley
2001-11-15 10:11 ` Dave Brolley
2001-11-15 9:52 ` Doug Evans
[not found] ` <15348.168.750723.846784.cygnus.local.cgen@casey.transmeta.com>
2001-10-13 2:39 ` Frank Ch. Eigler [this message]
2001-11-15 12:42 ` Frank Ch. Eigler
2001-11-15 9:21 ` Dave Brolley
2001-11-14 12:52 ` Doug Evans
2001-11-13 11:46 ` Dave Brolley
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=o54rnvhikm.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).