public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siarhei.siamashka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45886] [ARM] support for __ARM_PCS_VFP predefined symbol in gcc 4.5.x would be very nice
Date: Mon, 11 Oct 2010 14:31:00 -0000	[thread overview]
Message-ID: <20101011143100.6VQmd3f-BagRj_RlmkdBxf2gXTDkfdHHXoJZ-TIp4PY@z> (raw)
In-Reply-To: <bug-45886-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45886

--- Comment #2 from Siarhei Siamashka <siarhei.siamashka at gmail dot com> 2010-10-11 14:31:29 UTC ---
(In reply to comment #1)
> Confirmed though I think this isn't an "enhancement" but more a bug because
> code can't identify whether -mfloat-abi=hard is chosen by use of a
> pre-processor directive.

Thanks. Can we expect this problem to be fixed in gcc 4.5.2 (backported from
trunk)?

For now I'm going to use the following guard code to make sure that using
unpatched gcc will result in compilation problem instead of runtime failure:

#if defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >=
5)) \
    && defined(__ARM_EABI__) && !defined(__ARM_PCS_VFP) && !defined(__ARM_PCS)
#error "Can't identify floating point calling conventions.\nPlease ensure that
your toolchain defines __ARM_PCS or __ARM_PCS_VFP."
#endif


  parent reply	other threads:[~2010-10-11 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 22:05 [Bug target/45886] New: " siarhei.siamashka at gmail dot com
2010-10-07  8:16 ` [Bug target/45886] " ramana at gcc dot gnu.org
2010-10-11 14:31 ` siarhei.siamashka at gmail dot com [this message]
2010-11-12 14:29 ` rguenth at gcc dot gnu.org
2010-11-12 15:57 ` siarhei.siamashka at gmail dot com
2010-12-18 17:23 ` siarhei.siamashka at gmail dot com
2011-01-16 15:26 ` koen at dominion dot thruhere.net

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=20101011143100.6VQmd3f-BagRj_RlmkdBxf2gXTDkfdHHXoJZ-TIp4PY@z \
    --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).