public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/60464] [arm] ARM -mthumb version of libgcc contains ARM (non-thumb) code; not safe for thumb-only architectures
Date: Sat, 08 Mar 2014 03:21:00 -0000 [thread overview]
Message-ID: <bug-60464-4-KvWeRCy7EQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60464-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60464
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
Severity|critical |normal
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Configuring and building gcc 4.8.2 for the target 'arm-none-eabi' results in a thumb version of libgcc.a that is not entirely suitable for thumb-only processors
That is correct. The default is to configure arm target to be armv5 processor.
You need to configure for building for armv6m or an armv7m (or even armv7-a)
if you want to use -mthumb for a thumb (or thumb2 only) processor.
next prev parent reply other threads:[~2014-03-08 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-60464-4@http.gcc.gnu.org/bugzilla/>
2014-03-08 2:28 ` jeremygccb at baymoo dot org
2014-03-08 3:21 ` pinskia at gcc dot gnu.org [this message]
2014-03-08 5:42 ` jeremygccb at baymoo dot org
2014-03-08 5:55 ` pinskia at gcc dot gnu.org
2014-03-08 5:56 ` pinskia at gcc dot gnu.org
2014-03-08 7:37 ` jeremygccb at baymoo dot org
2014-03-08 8:33 ` jeremygccb at baymoo dot org
2014-03-10 15:12 ` 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-60464-4-KvWeRCy7EQ@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).