On Mon, Apr 24, 2006 at 05:59:30PM +0200, Frank Riese wrote:
> However, I'm still having problems with reloading/register spilling:
>
> -
> /usr/local/src/gcc/objdir/./gcc/xgcc -B/usr/local/src/gcc/objdir/./gcc/
Try this patch: http://people.redhat.com/dj/m32c/gcc-reload1.c.patch
It might help a little, although it doesn't solve the fundamental
design flaw (not being able to restart reload after breaking a complex
insn apart).
On Monday 24 April 2006 17:59, Frank Riese wrote:
> With my limited experience I would say that this tells me that the compiler
> gradually uses up all available registers and then, instead of freeing one,
> it complains that it hasn't any left (as a reminder: registers 3-7 are my
> GENERAL_REGS wi
On Wednesday 12 April 2006 15:43, Rask Ingemann Lambertsen wrote:
> On Wed, Apr 12, 2006 at 07:47:32AM +0200, Frank Riese wrote:
> > On Monday 10 April 2006 19:48, you wrote:
> > > Can it at least add (small) immediates to registers?
> >
> > Nope, sry. The only instructions that take other argument
On 12 April 2006 06:48, Frank Riese wrote:
> Yes, you're right. When I started writing this backend I didn't have much
> experience with it. I took the smallest backend I could find and tried to
> adjust it to me needs. The number of macros in the internals docs was a bit
> overwhelming at first a
On Wed, Apr 12, 2006 at 07:47:32AM +0200, Frank Riese wrote:
> On Monday 10 April 2006 19:48, you wrote:
> > Can it at least add (small) immediates to registers?
>
> Nope, sry. The only instructions that take other arguments than registers are
> the aforementioned LDL/LDH (load low/high), branch
On Monday 10 April 2006 19:48, you wrote:
> Can it at least add (small) immediates to registers?
Nope, sry. The only instructions that take other arguments than registers are
the aforementioned LDL/LDH (load low/high), branch instructions (they take a
memory address) and four bit operations whic
On Mon, Apr 10, 2006 at 03:23:43PM +0200, Frank Riese wrote:
>
> Most of the instructions of the target machine only support registers as
> operands. E.g., a store to a memory location (STO) must always take a
> register containing the address of the memory location and another register
> with
