public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
To: Joern Wolfgang Rennecke <gnu@amylaar.uk>,
	"gcc-patches@gcc.gnu.org"	<gcc-patches@gcc.gnu.org>
Cc: "Francois.Bedard@synopsys.com" <Francois.Bedard@synopsys.com>,
	"jeremy.bennett@embecosm.com" <jeremy.bennett@embecosm.com>
Subject: RE: [PATCH] [ARC] Add single/double IEEE precission FPU support.
Date: Fri, 05 Feb 2016 15:54:00 -0000	[thread overview]
Message-ID: <098ECE41A0A6114BB2A07F1EC238DE896616ECE3@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <56B4AEA1.6090607@amylaar.uk>

> P.S.: if code that is missing prototypes for stdarg functions is of no concern,
> there is another ABI alternative that might give good code density for
> architectures like ARC that have pre-decrement addressing modes and allow
> immediates to be pushed:
> 
> You could put all unnamed arguments on the stack (thus simplifying varargs
> processing), and leave all registers not used for argument passing call-saved.
> Thus, the callers wouldn't have to worry about saving these registers or
> reloading their values from the stack.
> 
> For gcc, this would require making the call fusage really work - probably
> involving a hook to tell the middle-end that the port really wants that - or a
> kludge to make affected call insn not look like call insns, similar to the sfuncs.

Unfortunately, we need to be compatible with the previous ABI for the time being.
I am now investigating passing the DI like modes in non even-odd registers. The biggest challenge is how to pass such a mode partially, without introducing odd/even register classes.

  reply	other threads:[~2016-02-05 15:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 13:58 Claudiu Zissulescu
2016-02-02 22:52 ` Joern Wolfgang Rennecke
2016-02-03 15:02   ` Claudiu Zissulescu
2016-02-03 18:42     ` Joern Wolfgang Rennecke
2016-02-05 14:16   ` Joern Wolfgang Rennecke
2016-02-05 15:54     ` Claudiu Zissulescu [this message]
2016-02-09 15:34     ` Claudiu Zissulescu
2016-02-10  6:39       ` Joern Wolfgang Rennecke
2016-02-10  9:45         ` Claudiu Zissulescu
2016-02-10 12:43         ` Claudiu Zissulescu
2016-02-10 13:31         ` Claudiu Zissulescu
2016-02-12 23:42           ` Joern Wolfgang Rennecke
2016-02-16 14:17             ` Claudiu Zissulescu

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=098ECE41A0A6114BB2A07F1EC238DE896616ECE3@de02wembxa.internal.synopsys.com \
    --to=claudiu.zissulescu@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu@amylaar.uk \
    --cc=jeremy.bennett@embecosm.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).