From: Segher Boessenkool <segher@kernel.crashing.org>
To: Steve Ellcey <sellcey@cavium.com>,
Alan.Haward@arm.com,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Francesco Petrogalli <Francesco.Petrogalli@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>,
"Sekhar, Ashwin" <Ashwin.Sekhar@cavium.com>,
gcc <gcc@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
nd <nd@arm.com>,
richard.sandiford@linaro.org
Subject: Re: [Aarch64] Vector Function Application Binary Interface Specification for OpenMP
Date: Sat, 26 May 2018 22:13:00 -0000 [thread overview]
Message-ID: <20180526221240.GT17342@gate.crashing.org> (raw)
In-Reply-To: <87a7smbuej.fsf@linaro.org>
On Sat, May 26, 2018 at 11:09:24AM +0100, Richard Sandiford wrote:
> On the wider point about changing the way call clobber information
> is represented: I agree it would be good to generalise what we have
> now. But if possible I think we should avoid target hooks that take
> a specific call, and instead make it an inherent part of the call insn
> itself, much like CALL_INSN_FUNCTION_USAGE is now. E.g. we could add
> a field that points to an ABI description, with -fipa-ra effectively
> creating ad-hoc ABIs. That ABI description could start out with
> whatever we think is relevant now and could grow over time.
Somewhat related: there still is PR68150 open for problems with
HARD_REGNO_CALL_PART_CLOBBERED in postreload-gcse (it ignores it).
Segher
next prev parent reply other threads:[~2018-05-26 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 21:47 Steve Ellcey
2018-05-15 18:29 ` Francesco Petrogalli
2018-05-16 16:21 ` Steve Ellcey
2018-05-16 16:30 ` Richard Earnshaw (lists)
2018-05-16 17:30 ` Steve Ellcey
2018-05-16 21:11 ` Richard Sandiford
2018-05-24 17:50 ` Steve Ellcey
2018-05-26 10:09 ` Richard Sandiford
2018-05-26 22:13 ` Segher Boessenkool [this message]
2018-05-27 15:59 ` Jeff Law
2018-05-29 10:06 ` Richard Sandiford
2018-05-31 10:39 ` Alan Hayward
2018-06-12 3:11 ` Jeff Law
2018-06-11 23:06 ` Jeff Law
2018-07-02 18:16 ` Francesco Petrogalli
-- strict thread matches above, loose matches on Subject: below --
2017-03-15 9:50 Sekhar, Ashwin
2017-03-17 14:02 ` James Greenhalgh
2017-03-20 4:30 ` Sekhar, Ashwin
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=20180526221240.GT17342@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Alan.Haward@arm.com \
--cc=Ashwin.Sekhar@cavium.com \
--cc=Francesco.Petrogalli@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=nd@arm.com \
--cc=richard.sandiford@linaro.org \
--cc=sellcey@cavium.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).