From: David Edelsohn <dje@watson.ibm.com>
To: law@cygnus.com
Cc: Geoffrey KEATING <geoffk@discus.anu.edu.au>, egcs@cygnus.com
Subject: Re: asm clobbers, !SMALL_REGISTER_CLASSES patch.
Date: Sun, 15 Feb 1998 18:47:00 -0000 [thread overview]
Message-ID: <9802160247.AA03674@rios1.watson.ibm.com> (raw)
In-Reply-To: <1597.887561232@hurl.cygnus.com>
>>>>> Jeffrey A Law writes:
Jeff> I wonder if it makes more sense to have asm clobbers specify a
Jeff> register class instead of explicit registers as an option. That
Jeff> would at least give us the option of doing the clobber both ways
Jeff> depending on how the target port handled the register in question.
Exactly! This is the problem most people are encountering and the
solution that I have been trying to recommend all along. If the register
is alone in a class, then the class is preferred -- assuming that the port
did not need to specify SMALL_REGISTER_CLASSES for other reasons.
Once one can specify a register class for a clobber (essentially
creating a clobber match-scratch, it should not be difficult for GCC to
recognize this and convert a register specified by name as a clobber into
the equivalent class containing only one register.
David
next prev parent reply other threads:[~1998-02-15 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-12 19:36 Geoffrey KEATING
1998-02-12 20:24 ` David Edelsohn
1998-02-12 20:24 ` Geoffrey KEATING
1998-02-13 2:28 ` Jeffrey A Law
1998-02-13 2:28 ` Geoffrey KEATING
1998-02-14 0:32 ` Jeffrey A Law
1998-02-14 21:14 ` Geoffrey KEATING
1998-02-15 11:33 ` Jeffrey A Law
1998-02-15 18:47 ` David Edelsohn [this message]
1998-02-13 2:28 ` Richard Henderson
1998-02-13 10:34 ` David Edelsohn
1998-02-13 10:58 ` Richard Henderson
1998-02-13 10:58 ` David Edelsohn
1998-02-14 20:23 ` Geoffrey KEATING
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=9802160247.AA03674@rios1.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=geoffk@discus.anu.edu.au \
--cc=law@cygnus.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).