From: Aurelien Buhrig <aurelien.buhrig.gcc@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: best ABI strategy ?
Date: Wed, 30 Nov 2011 18:49:00 -0000 [thread overview]
Message-ID: <CAJ-J9_VUxHafjK8z74LCrxeesL_Ord=xviu4bEbP5KTDUKUJ-Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ-J9_WSXZdEs49o+fyoZLpwdJ_VKwJ-gAs6hy8YLwLip3T=Xg@mail.gmail.com>
> Hi,
>
> I'm trying to optimize our target ABI, and I'm wondering what is the
> best strategy to define it.
> Is there a paper, or any hint, dealing with this topic ?
> For instance,
> - which ratio between call-used-reg vs "static regs"
> - which ratio between arg regs vs call-used-reg
> - what should be return regs
> - ...
> I guess this problem is very target dependent, but there are maybe
> general ideas about this.
>
>
> In particular, for now my call-used regs set is the same that arg regs
> set. I noticed GCC would not use arg regs for reloading, (or would
> prefer others), even if they are not actually used by function args.
> and it generates extra push/pop of static regs. I there a way force
> gcc preferring using "free" arg regs ?
>
> Thank you by advance!
>
> Aurélien
Forget the last point. GCC does use free arg regs. The testcases I
looked at were not relevant. Sorry!
Aurélien
next prev parent reply other threads:[~2011-11-30 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 16:18 Aurelien Buhrig
2011-11-30 16:57 ` Georg-Johann Lay
2011-11-30 21:18 ` Aurelien Buhrig
2011-11-30 18:49 ` Aurelien Buhrig [this message]
[not found] ` <mcrfwh5saxu.fsf@dhcp-172-18-216-180.mtv.corp.google.com>
2011-12-01 13:09 ` Aurelien Buhrig
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='CAJ-J9_VUxHafjK8z74LCrxeesL_Ord=xviu4bEbP5KTDUKUJ-Q@mail.gmail.com' \
--to=aurelien.buhrig.gcc@gmail.com \
--cc=gcc-help@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).