public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/66849] Incorrect multilib chosen with -mthumb -mfloat-abi=hard
Date: Mon, 03 Aug 2015 20:34:00 -0000	[thread overview]
Message-ID: <bug-66849-4-8SK6Um0JTG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66849-4@http.gcc.gnu.org/bugzilla/>

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

Jim Wilson <wilson at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wilson at gcc dot gnu.org

--- Comment #4 from Jim Wilson <wilson at gcc dot gnu.org> ---
The problem is that we can't have thumb1 hard-float code, so the thumb/hard
multilib is explicitly disabled.  However, we can have thumb2 hard-float code,
and hence this should be enabled for targets that support thumb2, but isn't
yet, as there is no easy and obvious way to do this without breaking support
for older thumb1 targets.

If you don't care whether you have arm or thumb code, then you can just use the
arm hard-float library with an override like you already did.

If you want a proper thumb2 hard multilib, then in the file
gcc/config/arm/t-arm-elf see the line
MULTILIB_EXCEPTIONS    += *mthumb/*mfloat-abi=hard*
Put a # in front of it to disable it, rebuild gcc, and then you will have
thumb2 hard-float libraries.  See also the comments before this section of
code.

The t-aprofile that Ramana mentioned does support thumb/hard multilibs, but
makes this work by requiring armv7 or higher.


  parent reply	other threads:[~2015-08-03 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 16:18 [Bug driver/66849] New: " simon at pushface dot org
2015-07-13  8:25 ` [Bug driver/66849] " simon at pushface dot org
2015-07-29 13:21 ` ramana at gcc dot gnu.org
2015-07-30 17:28 ` simon at pushface dot org
2015-08-03 20:34 ` wilson at gcc dot gnu.org [this message]
2015-08-04 13:40 ` simon at pushface dot org
2015-08-04 15:01 ` jim.wilson at linaro dot 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-66849-4-8SK6Um0JTG@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).