From: Joseph Myers <joseph@codesourcery.com>
To: Matthew Wahab <matthew.wahab@foss.arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Remove TARGET_INVALID_PARAMETER_TYPE and TARGET_INVALID_RETURN_TYPE hooks.
Date: Tue, 10 May 2016 20:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1605102003030.29007@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5728A641.9070207@foss.arm.com>
On Tue, 3 May 2016, Matthew Wahab wrote:
> Hello,
>
> The target hooks TARGET_INVALID_PARAMETER_TYPE and
> TARGET_INVALID_RETURN_TYPE were only used by the ARM backend and
> are no longer used. This patch removes them.
>
> Tested for arm-none-linux-gnueabihf with native bootstrap and make check
> and for and x86_64-none-linux native bootstrap and check-gcc.
>
> Ok for trunk?
OK once the ARM back-end patch is in (as far as I know, it still needs
review).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-05-10 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:20 [ARM] Enable __fp16 as a function parameter and return type Matthew Wahab
2016-04-28 15:50 ` Joseph Myers
2016-05-03 13:19 ` Matthew Wahab
2016-05-10 20:07 ` Joseph Myers
2016-05-03 13:23 ` [PATCH] Remove TARGET_INVALID_PARAMETER_TYPE and TARGET_INVALID_RETURN_TYPE hooks Matthew Wahab
2016-05-10 20:03 ` Joseph Myers [this message]
2016-05-11 15:03 ` Re: [ARM] Enable __fp16 as a function parameter and return type Tejas Belagod
2016-05-11 15:47 ` Joseph Myers
2016-05-13 9:24 ` Tejas Belagod
2016-05-13 12:11 ` Joseph Myers
2016-05-16 13:16 ` Tejas Belagod
2016-05-18 8:41 ` Ramana Radhakrishnan
2016-05-18 14:33 ` Matthew Wahab
2016-05-18 14:37 ` Ramana Radhakrishnan
2016-05-18 15:55 ` Joseph Myers
2016-05-13 13:41 ` Ramana Radhakrishnan
2016-06-01 14:43 ` Christophe Lyon
2016-06-02 7:40 ` Matthew Wahab
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=alpine.DEB.2.20.1605102003030.29007@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=matthew.wahab@foss.arm.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).