Christian Grössler writes:
It seems that gcc wants to create an instruction like "p2=add(p1,p3)".
How can I tell him not to do that?
I tried to fiddle with the "p_d_general_operand" predication and use a
modified one for operand 2, but
at the time the constraint is called
On 24.02.11 19:27, Christian Grössler wrote:
On 24.02.11 15:38, Jean-Marc Saffroy wrote:
On 02/23/2011 09:52 PM, Christian Grössler wrote:
Hello,
I have a problem with register allocation. Our architecture has some
pointer registers "pX" (24bit)
and some data registers "dX" (32bit). Since poin
On 24.02.11 15:38, Jean-Marc Saffroy wrote:
On 02/23/2011 09:52 PM, Christian Grössler wrote:
Hello,
I have a problem with register allocation. Our architecture has some
pointer registers "pX" (24bit)
and some data registers "dX" (32bit). Since pointers are only 24bit,
we're using PSImode for t
On 02/23/2011 09:52 PM, Christian Grössler wrote:
> Hello,
>
> I have a problem with register allocation. Our architecture has some
> pointer registers "pX" (24bit)
> and some data registers "dX" (32bit). Since pointers are only 24bit,
> we're using PSImode for them.
>
> There are restrictions in
Hello,
I have a problem with register allocation. Our architecture has some pointer registers
"pX" (24bit)
and some data registers "dX" (32bit). Since pointers are only 24bit, we're
using PSImode for them.
There are restrictions in the "add" opcode, we can do
pX = add(pX,)
pX = add(pX,dX)
pX
