This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Constraints and reload

From: Joern Rennecke <joern dot rennecke at embecosm dot com>
To: Jean Christophe Beyler <jean dot christophe dot beyler at gmail dot com>
Cc: Richard Henderson <rth at redhat dot com>, gcc at gcc dot gnu dot org
Date: Wed, 16 Sep 2009 19:58:24 -0400
Subject: Re: Constraints and reload
References: <c568a2600909141018i624dc624q5e4ea916ea240a60@mail.gmail.com> <4AAE8164.7080906@redhat.com> <c568a2600909141116t30731abdh3dfa592749551997@mail.gmail.com> <c568a2600909161300u1fa8b32fm4ed1f6ed7cdc0e8c@mail.gmail.com> <4AB149F0.4050903@redhat.com> <c568a2600909161342pda961a8r19a3e6e439338d78@mail.gmail.com>

Quoting Jean Christophe Beyler <jean.christophe.beyler@gmail.com>:

I have an expand_move that rejects anything not accepted, a check_move
that makes sure everything is ok and the constraints that go with (my
'R' constraint).

The instruction generated during greg should normally be refused.

From what you've said, it seems that I did forget to define something
so I will look at the secondary reload stuff ?


When reload decides if something is suitable for reg_equiv_mem or
only for reg_equiv_address, it uses strict_memory_address_p.

If you don't have patterns that can handle certain addresses in DFmode,
you should reject these addresses in GO_IF_LEGITIMATE_ADDRESS /
TARGET_LEGITIMATE_ADDRESS_P.

References:
- Constraints and reload
  - From: Jean Christophe Beyler
- Re: Constraints and reload
  - From: Richard Henderson
- Re: Constraints and reload
  - From: Jean Christophe Beyler
- Re: Constraints and reload
  - From: Richard Henderson
- Re: Constraints and reload
  - From: Jean Christophe Beyler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]