public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Bruel <christian.bruel@st.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       Richard Earnshaw	<Richard.Earnshaw@arm.com>,
	       "nickc@redhat.com" <nickc@redhat.com>
Subject: Re: [PATCH, ARM] attribute target (thumb,arm) [4/6] respin (4th)
Date: Mon, 18 May 2015 07:18:00 -0000	[thread overview]
Message-ID: <55598F35.1010709@st.com> (raw)
In-Reply-To: <554C7459.4000806@arm.com>

Hi Ramana,

On 05/08/2015 10:31 AM, Ramana Radhakrishnan wrote:
>
> I'm still playing with the code, so this is a partial review.
>
> We should prevent inlining of ARM state functions into functions we know
> will be T16 if !TARGET_SOFT_FLOAT on the grounds that the architecture
> doesn't have floating point instruction encodings in the T16 ISA
> (Thumb1). We'll just cause internal compiler errors if we allow this.
>

I tried to forge a bit with this situation, but I couldn't generate such 
inconsistencies, as the situation is rejected with a :
"sorry, unimplemented: Thumb-1 hard-float VFP ABI"
when using -march=armv6 -mthumb -mhard-float (would that match with T16 
&& !TARGET_SOFT_FLOAT)

Do you have the example producing an ICE ? That would be interesting to 
add it in the testsuite.

by the way, I think the error message should be changed from

"sorry, unimplemented: Thumb-1 hard-float VFP ABI"

to a user error:

"Can't use Thumb-1 hard-float VFP ABI"

Christian


  reply	other threads:[~2015-05-18  7:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 14:25 Christian Bruel
2015-05-06 23:04 ` Sandra Loosemore
2015-05-08  8:31   ` Ramana Radhakrishnan
2015-05-18  7:18     ` Christian Bruel [this message]
2015-05-18  8:16     ` [PATCH, ARM] attribute target (thumb,arm) [4/6] respin (5th) Christian Bruel
2015-06-01 10:39       ` Kyrill Tkachov
2015-06-01 11:30         ` Christian Bruel
2015-06-01 12:41           ` Kyrill Tkachov
2015-06-01 12:55             ` Christian Bruel
2015-06-08  9:26             ` Christian Bruel
2015-06-08  9:33               ` Ramana Radhakrishnan
2015-06-10  8:26                 ` [PATCH, ARM] (commited) attribute target (thumb,arm) [4/6] Christian Bruel
2015-06-15 10:15                   ` James Greenhalgh
2015-06-15 12:05                     ` Christian Bruel
2015-05-07  8:13 ` [PATCH, ARM] attribute target (thumb,arm) [4/6] respin (4th) Christian Bruel

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=55598F35.1010709@st.com \
    --to=christian.bruel@st.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@redhat.com \
    --cc=ramana.radhakrishnan@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).