From: Eric Botcazou <ebotcazou@adacore.com>
To: "Laurent Rougé" <laurent.rouge@menta.fr>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Reintroduce -mflat option on SPARC
Date: Tue, 17 May 2011 13:06:00 -0000 [thread overview]
Message-ID: <201105171251.20272.ebotcazou@adacore.com> (raw)
In-Reply-To: <4DA73D99.5000800@menta.fr>
> Right, -mflat option should only be for 32-bit SPARC target.
OK, let's keep it that way for now.
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).
--
Eric Botcazou
next prev parent reply other threads:[~2011-05-17 10:52 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 [this message]
2011-05-18 14:36 ` Eric Botcazou
2011-05-26 20:29 ` Laurent Rougé
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=201105171251.20272.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=laurent.rouge@menta.fr \
/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).