public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104455] Cannot select -march=armv7-a using GCC 11
Date: Thu, 10 Feb 2022 20:44:58 +0000	[thread overview]
Message-ID: <bug-104455-4-v3LTyum9gV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104455-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455

Jeffrey Walton <noloader at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |FIXED

--- Comment #4 from Jeffrey Walton <noloader at gmail dot com> ---
(In reply to Richard Earnshaw from comment #3)
> Your compiler is configured to pick the fp architecture up from the -march
> (or -mcpu) option (it's using an 'auto' fpu).  Your ABI requires an FPU, so
> you need to specify that as part of the -march command.  Use
> -march=armv7-a+fp or something like -march=armv7-a+simd.  The various
> options are described in the manual.

Thanks again Richard.

So stepping back to 10,000 feet, we now need to specify options and ISA's we
are not using. That seems like a bug to me. I'm not sure I would consider this
fixed.

Where is it going to stop? How many non-used options that I am not aware of
will I need to specify?

I think either GCC or Debian needs to fix this. This could be a GCC bug because
GCC apparently knows there's a fp unit but it chooses to ignore it. Instead it
wants me to say it again. This could be a Debian bug because they need to
completely (not partially) configure things.

  parent reply	other threads:[~2022-02-10 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 23:45 [Bug c++/104455] New: " noloader at gmail dot com
2022-02-09 11:47 ` [Bug target/104455] " rearnsha at gcc dot gnu.org
2022-02-10  3:12 ` noloader at gmail dot com
2022-02-10 11:17 ` rearnsha at gcc dot gnu.org
2022-02-10 20:44 ` noloader at gmail dot com [this message]
2022-02-10 21:16 ` schwab@linux-m68k.org
2022-02-11 15:24 ` rearnsha at gcc dot gnu.org

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=bug-104455-4-v3LTyum9gV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).