Denis Chertykov [EMAIL PROTECTED] writes:
Ian Lance Taylor ian@airs.com writes:
Denis Chertykov [EMAIL PROTECTED] writes:
I think that better to call update_eliminables() somewhere after
setup_save_areas()
Exactly. We do that. About 15 lines after the lines you quoted
Ian Lance Taylor ian@airs.com writes:
[...]
I think that better to call update_eliminables() somewhere after
setup_save_areas()
Exactly. We do that. About 15 lines after the lines you quoted
above.
What am I missing?
I'm (exactly AVR port) need in call to update_eliminables()
Denis Chertykov [EMAIL PROTECTED] writes:
I think that better to call update_eliminables() somewhere after
setup_save_areas()
Exactly. We do that. About 15 lines after the lines you quoted
above.
What am I missing?
I'm (exactly AVR port) need in call to update_eliminables()
Denis Chertykov [EMAIL PROTECTED] writes:
Code fragment from reload1.c: reload()
if (caller_save_needed)
setup_save_areas ();
/* If we allocated another stack slot, redo elimination bookkeeping. */
if
Hi All.
While I have debugging AVR target bug I found that something wrong in
port code or in reload.
Is it right to use of get_frame_size() inside CAN_ELIMINATE macro valid ?
If yes then reload have a bug.
If no then AVR and probably MIPS ports have invalid definitions of
CAN_ELIMINATE.
Denis.
On Feb 13, 2006, at 7:43 AM, Denis Chertykov wrote:
Hi All.
While I have debugging AVR target bug I found that something wrong in
port code or in reload.
Is it right to use of get_frame_size() inside CAN_ELIMINATE macro
valid ?
If yes then reload have a bug.
If no then AVR and probably
Eric Christopher [EMAIL PROTECTED] writes:
On Feb 13, 2006, at 7:43 AM, Denis Chertykov wrote:
Hi All.
While I have debugging AVR target bug I found that something wrong in
port code or in reload.
Is it right to use of get_frame_size() inside CAN_ELIMINATE macro
valid ?
If yes
