From: Richard Henderson <rth@redhat.com>
To: Jan Hubicka <jh@suse.cz>
Cc: Janis Johnson <janis187@us.ibm.com>,
gcc@gcc.gnu.org, rodrigc@attbi.com, bangerth@ticam.utexas.edu
Subject: Re: patch that caused regression PR middle-end/8808
Date: Thu, 19 Dec 2002 11:19:00 -0000 [thread overview]
Message-ID: <20021219181844.GA10293@redhat.com> (raw)
In-Reply-To: <20021219093753.GC16671@kam.mff.cuni.cz>
On Thu, Dec 19, 2002 at 10:37:53AM +0100, Jan Hubicka wrote:
> Yes, however I am not at all sure how this can be done. Fixed register,
> for instance can be used in the asm("xxx") in rare situations, so I
> really don't see how one can validate such things.
We could have another array, along side FIXED and CALL_USED,
that was UNAVAILABLE. Errors would be issued for using asm
registers in this set.
r~
next prev parent reply other threads:[~2002-12-19 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 15:22 Janis Johnson
2002-12-19 3:57 ` Jan Hubicka
2002-12-19 11:19 ` Richard Henderson [this message]
2002-12-19 15:31 ` Jan Hubicka
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=20021219181844.GA10293@redhat.com \
--to=rth@redhat.com \
--cc=bangerth@ticam.utexas.edu \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=jh@suse.cz \
--cc=rodrigc@attbi.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).