public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Laurent Rougé" <laurent.rouge@menta.fr>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Reintroduce -mflat option on SPARC
Date: Thu, 26 May 2011 20:29:00 -0000	[thread overview]
Message-ID: <4DDE9EA9.5080206@menta.fr> (raw)
In-Reply-To: <201105181231.21495.ebotcazou@adacore.com>

Dear Eric,

In fact, I haven't tried to make big changes in how mflat option was
implemented. From my point of view, the goal was to facilitate mflat
option reintroduction first, and then improve it after. I hope you
understand. I know there's some place to improve, maybe you have start
to do it ?

So why mflat is like that we should ask the questions to 'wilson' who
did it in 92 (see revision 1275) !

Regards,
Laurent.

Le 18/05/2011 12:31, Eric Botcazou a écrit :
>> Another question: why does the model hijack %i7 to use it as frame pointer,
>> instead of just using %fp?  AFAICS both are kept as fixed registers by the
>> code so the model seems to be wasting 1 register (2 without frame pointer).
> Related question: why saving the Local and In registers in the frame instead of 
> at their standard location, right above the stack pointer?  It would seem to 
> me that the layout of the frame can be identical to the standard one.

  reply	other threads:[~2011-05-26 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 13:51 Laurent Rougé
2011-02-26  0:18 ` Eric Botcazou
2011-04-12 17:44 ` Eric Botcazou
2011-04-14 18:55   ` Laurent Rougé
2011-05-17 13:06     ` Eric Botcazou
2011-05-18 14:36       ` Eric Botcazou
2011-05-26 20:29         ` Laurent Rougé [this message]
2011-05-26 21:54           ` Eric Botcazou
2011-06-10 11:11             ` Eric Botcazou

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=4DDE9EA9.5080206@menta.fr \
    --to=laurent.rouge@menta.fr \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).