This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Base register restrictions
- From: Dobes <bdobry at udel dot edu>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 29 Jun 2009 11:38:48 -0700 (PDT)
- Subject: Base register restrictions
I am working on a port to an architecture with some strict rules. The
restriction that I am unable to figure out how to enforce is a base register
that is allowed in the destination operand, but not in a source operand.
For example, this would be allowed "add 4($1), $8, $9", but this would not
be allowed "add $8, 4($1), $9" because $1 can only be used a base register
for the destination operand. Is there any way to get that kind of
information in GO_IF_LEGITIMATE_ADDRESS or can you think of some other way
to handle this? Anyone know of a port with something similar that I could
look at? Thanks.
--
View this message in context: http://www.nabble.com/Base-register-restrictions-tp24259346p24259346.html
Sent from the gcc - Dev mailing list archive at Nabble.com.