public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <andrew_stubbs@mentor.com>
To: <ramrad01@arm.com>, Kyrill Tkachov <kyrylo.tkachov@arm.com>
Cc: James Greenhalgh <james.greenhalgh@arm.com>,
	Andrew Stubbs	<ams@codesourcery.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [arm][patch] fix arm_neon_ok check on !arm_arch7
Date: Wed, 03 Dec 2014 15:03:00 -0000	[thread overview]
Message-ID: <547F2646.7020308@mentor.com> (raw)
In-Reply-To: <CAJA7tRZ_X1zKCW7LRCbnWhxfG-PbKTWpp6qmq1kcHcKiTRzstg@mail.gmail.com>

On 02/12/14 21:45, Ramana Radhakrishnan wrote:
> I've spent some time this evening pondering over your patch. Firstly
> it appears that the current behaviour is going to cause more breakage
> than originally expected. If this is to go in we'd have a number of
> users having to add -mfloat-abi=soft to the command line option to
> ensure that -march=armv5te works just fine on the files where
> march=armv5te in the first places.

Agreed. I've just reverted the patch.

> I'm not sure that the original patch is enough.
>
> The tools have always allowed us to drop down the arch to
> march=armv5te along with using -mfpu=neon. We are now changing command
> line behaviour, so an inform in terms of diagnostics to the user would
> be useful as it states that we don't really have mfpu=neon generating
> neon code any more because of this particular case. If we are to do
> this then the original patch is probably not enough as it then doesn't
> handle the case of TARGET_VFP3 / TARGET_VFP5 / TARGET_NEON_FP16 /
> TARGET_FP16 / TARGET_FPU_ARMV8 etc. etc. etc.

I'll take a look at those shortly.

Andrew

  reply	other threads:[~2014-12-03 15:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 21:39 Andrew Stubbs
2014-09-15  9:46 ` Richard Earnshaw
2014-09-15 10:56   ` Andrew Stubbs
2014-09-15 13:30     ` Richard Earnshaw
2014-09-17 11:00       ` Andrew Stubbs
2014-09-23  8:27     ` James Greenhalgh
2014-09-23 15:22       ` Stubbs, Andrew
2014-10-15 16:37         ` Jiong Wang
2014-10-15 16:59           ` Andrew Stubbs
2014-10-16 13:53             ` Jiong Wang
2014-11-07 10:35               ` Andrew Stubbs
2014-11-14 11:17                 ` Andrew Stubbs
2014-11-26 13:11                   ` Andrew Stubbs
2014-11-27 17:28                     ` Mike Stump
2014-11-27 19:29                       ` Andrew Stubbs
2014-11-28  8:42                         ` Mike Stump
2014-12-02 14:01       ` Kyrill Tkachov
2014-12-02 21:45         ` Ramana Radhakrishnan
2014-12-03 15:03           ` Andrew Stubbs [this message]
2014-12-23 17:32             ` Andrew Stubbs
2015-01-12 14:14               ` Andrew Stubbs
2015-01-12 14:27                 ` Ramana Radhakrishnan
2015-01-13 21:08                   ` Andrew Stubbs
2015-01-14  9:06                     ` Ramana Radhakrishnan
2015-01-14 15:25                       ` Andrew Stubbs

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=547F2646.7020308@mentor.com \
    --to=andrew_stubbs@mentor.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=james.greenhalgh@arm.com \
    --cc=kyrylo.tkachov@arm.com \
    --cc=ramrad01@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).