public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Chertykov <denisc@overta.ru>
To: Denis Chertykov <denisc@overta.ru>
Cc: Ian Lance Taylor <ian@airs.com>,
	 Eric Christopher <echristo@apple.com>,
		  gcc@gcc.gnu.org
Subject: Re: CAN_ELIMINATE question
Date: Tue, 28 Mar 2006 20:45:00 -0000	[thread overview]
Message-ID: <irpyo0we.fsf@overta.ru> (raw)
In-Reply-To: <zmkpyirw.fsf@overta.ru>

Denis Chertykov <denisc@overta.ru> writes:

> Ian Lance Taylor <ian@airs.com> writes:
> 
> > Denis Chertykov <denisc@overta.ru> 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() somewhere
> > > between setup_save_areas() and calculate_needs_all_insns()
> > > (Not "about 15 lines after" ;) because all bad things happened inside
> > > calculate_needs_all_insns(). 
> > > 
> > > calculate_needs_all_insns() collect wrong reloads because
> > > reg_eliminate structure for FP->SP have wrong can_eliminate field.
> > 
> > But then we go around the loop again, so everything should get
> > recalculated based on the new assumptions.  Doesn't that happen for
> > you?
> 
> If you mean the "continue" here:
>       if (caller_save_needed)
> 	setup_save_areas ();
> 
>       /* If we allocated another stack slot, redo elimination bookkeeping.  */
>       if (starting_frame_size != get_frame_size ())
> 	continue;
> -------^^^^^^^^^
> then answer no because only set_initial_elim_offsets() will be called.
> set_initial_elim_offsets() doesn't change reg_eliminate[].can_eliminate
> flag.
> 
> If you mean a call update_eliminables() after
> calculate_needs_all_insns() then answer no (again :) because all wrong
> things already happened inside calculate_needs_all_insns() and
> compiler will call
> select_reload_regs() -> find_reload_regs() -> spill_failure()

Can somebody comment the problem, please ?

Denis.

      reply	other threads:[~2006-03-28 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 15:43 Denis Chertykov
2006-02-13 17:48 ` Eric Christopher
2006-02-13 19:07   ` Denis Chertykov
2006-02-15 23:48     ` Ian Lance Taylor
2006-02-16 17:28       ` Denis Chertykov
2006-02-16 23:56         ` Ian Lance Taylor
2006-02-17 17:49           ` Denis Chertykov
2006-03-28 20:45             ` Denis Chertykov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=irpyo0we.fsf@overta.ru \
    --to=denisc@overta.ru \
    --cc=echristo@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ian@airs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).