public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Yvan Roux <yvan.roux@linaro.org>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM] PR62248 - Configure error with --with-fpu=fp-armv8
Date: Wed, 27 Aug 2014 09:25:00 -0000	[thread overview]
Message-ID: <53FDA3EB.2060703@arm.com> (raw)
In-Reply-To: <CAD57uCfdEcjrvyYPASp1VPR-LRr=3fxMuMuXgVjZhzDwafT4cA@mail.gmail.com>

On 27/08/14 09:04, Yvan Roux wrote:
> Hi,
> 
> as reported in PR62248 there is a typo in gcc/config.gcc where
> --with-fpu doesn't match -mfpu option for fp-armv8 value (fp-arm-v8 in
> config.gcc). Here is the patch to fix it.
> 
> Thanks,
> Yvan
> 
> 2014-08-27  Yvan Roux  <yvan.roux@linaro.org>
> 
>         * config.gcc:  Fix fp-armv8 option for arm*-*-* targets.
> 
> 
> pr62248.diff
> 
> 
> diff --git a/gcc/config.gcc b/gcc/config.gcc
> index 6862c127..3f68e3e 100644
> --- a/gcc/config.gcc
> +++ b/gcc/config.gcc
> @@ -3528,7 +3528,7 @@ case "${target}" in
>  		| vfp | vfp3 | vfpv3 \
>  		| vfpv3-fp16 | vfpv3-d16 | vfpv3-d16-fp16 | vfpv3xd \
>  		| vfpv3xd-fp16 | neon | neon-fp16 | vfpv4 | vfpv4-d16 \
> -		| fpv4-sp-d16 | neon-vfpv4 | fp-arm-v8 | neon-fp-armv8 \
> +		| fpv4-sp-d16 | neon-vfpv4 | fp-armv8 | neon-fp-armv8 \
>                  | crypto-neon-fp-armv8)
>  			# OK
>  			;;
> 

Ok; but better still would be to change this to use the official list in
arm-fpus.def (like we do for CPU names).

R.

  reply	other threads:[~2014-08-27  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  8:04 Yvan Roux
2014-08-27  9:25 ` Richard Earnshaw [this message]
2014-08-27 10:35   ` Yvan Roux
2014-08-27 11:10     ` Yvan Roux
2014-08-27 11:35       ` Yvan Roux
2014-08-27 12:26         ` Richard Earnshaw
2014-08-27 14:22           ` Yvan Roux
2014-08-27 16:51             ` Bernhard Reutner-Fischer
2014-08-27 17:07               ` Yvan Roux
2014-08-27 17:13                 ` Yvan Roux

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=53FDA3EB.2060703@arm.com \
    --to=rearnsha@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=yvan.roux@linaro.org \
    /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).