Except when travelling backwards in time and replying to a post that hasn't
been written yet!
cheers,
DaveK
--
Can't think of a witty .sigline today
On 19 March 2007 20:21, Mike Stump wrote:
> Never top post.
>
> On Mar 19, 2007, at 3:13 AM, Markus Franke wrote:
>
>> Just anot
Never top post.
On Mar 19, 2007, at 3:13 AM, Markus Franke wrote:
Just another issue. Everything is working fine if using "-O1", "-
O2" or
"-O3".
Maybe this helps.
Regards,
Markus
Markus Franke wrote:
Again with attachment and CC to the Mailing List. Sorry for missing this.
Regards,
Markus
---
Hello,
thanks for your instructions. Indeed you were right. I mixed up some files.
Again an excerpt of the output-files:
---snip--- // expand
(insn 45 47 46 1 (set (subreg:SI (reg:DI 92 [ D.1212 ]) 4)
Markus Franke wrote:
That means the compiler has to reload the pseudo registers 92 and 93 for
this instruction, right?
First we do register allocation. Then, after register allocation, if
the chosen hard registers don't match the constraints, then we use
reload to fix it.
The relevant dat
Hello,
thanks for your answer.
Here is an excerpt of the .00.expand file for insn 45:
---snip---
(insn 45 47 46 1 (set (subreg:SI (reg:DI 92 [ D.1212 ]) 4)
(reg:SI 93 [ D.1211 ])) -1 (nil)
(expr_list:REG_NO_CONFLICT (reg:SI 93 [ D.1211 ])
(nil)))
---snap---
That means the com
Markus Franke wrote:
Does anybody have an idea what could be wrong in the machine description
or to where start finding the error?
Compile with -da, and starting looking at the RTL dumps, mainly the greg
and lreg ones. The greg one will have a section listing all of the
reloads generated, fi
