This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [Aarch64] Vector Function Application Binary Interface Specification for OpenMP
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Steve Ellcey <sellcey at cavium dot com>, Alan dot Haward at arm dot com, "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, Francesco Petrogalli <Francesco dot Petrogalli at arm dot com>, James Greenhalgh <James dot Greenhalgh at arm dot com>, "Sekhar, Ashwin" <Ashwin dot Sekhar at cavium dot com>, gcc <gcc at gcc dot gnu dot org>, Marcus Shawcroft <Marcus dot Shawcroft at arm dot com>, nd <nd at arm dot com>, richard dot sandiford at linaro dot org
- Date: Sat, 26 May 2018 17:12:40 -0500
- Subject: Re: [Aarch64] Vector Function Application Binary Interface Specification for OpenMP
- References: <1518212868.14236.47.camel@cavium.com> <32617133-64DC-4F62-B7A0-A6B417C5B14E@arm.com> <1526487700.29509.6.camel@cavium.com> <a8761c95-e4fb-dd92-8988-825c8b34475f@arm.com> <1526491802.29509.19.camel@cavium.com> <87a7sznw5c.fsf@linaro.org> <1527184223.22014.13.camel@cavium.com> <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