public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "corsepiu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55175] i386/sfp-exceptions.c:52:7: error: impossible constraint in 'asm'
Date: Mon, 05 Nov 2012 12:42:00 -0000 [thread overview]
Message-ID: <bug-55175-4-re26yFqP3N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55175-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55175
--- Comment #12 from Ralf Corsepius <corsepiu at gcc dot gnu.org> 2012-11-05 12:41:56 UTC ---
(In reply to comment #11)
> You should use t-softfp instead of 386/t-softfp for i[34567]86-*-rtems* in
> libgcc/config.host.
>
> In fact, there should be no i386/t-softfp for any x86 target.
You mean, we should apply a patch similar to this?
--- a/libgcc/config.host
+++ b/libgcc/config.host
@@ -568,7 +568,7 @@ i[34567]86-*-nto-qnx*)
extra_parts=crtbegin.o
;;
i[34567]86-*-rtems*)
- tmake_file="$tmake_file i386/t-softfp i386/t-crtstuff"
+ tmake_file="$tmake_file i386/t-crtstuff"
extra_parts="$extra_parts crti.o crtn.o"
;;
i[34567]86-*-solaris2* | x86_64-*-solaris2.1[0-9]*)
@@ -1165,6 +1165,7 @@ i[34567]86-*-darwin* | x86_64-*-darwin* | \
i[34567]86-*-kfreebsd*-gnu | x86_64-*-kfreebsd*-gnu | \
i[34567]86-*-linux* | x86_64-*-linux* | \
i[34567]86-*-gnu* | \
+ i[34567]86-*-rtems* | \
i[34567]86-*-solaris2* | x86_64-*-solaris2.1[0-9]* | \
i[34567]86-*-cygwin* | i[34567]86-*-mingw* | x86_64-*-mingw* | \
i[34567]86-*-freebsd* | x86_64-*-freebsd*)
The breakdown above is with this patch applied.
next prev parent reply other threads:[~2012-11-05 12:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 5:24 [Bug bootstrap/55175] New: " corsepiu at gcc dot gnu.org
2012-11-02 10:02 ` [Bug bootstrap/55175] " ubizjak at gmail dot com
2012-11-02 10:05 ` ubizjak at gmail dot com
2012-11-02 13:30 ` joel at gcc dot gnu.org
2012-11-02 14:09 ` uros at gcc dot gnu.org
2012-11-02 14:26 ` [Bug target/55175] " ubizjak at gmail dot com
2012-11-03 6:25 ` corsepiu at gcc dot gnu.org
2012-11-04 18:58 ` uros at gcc dot gnu.org
2012-11-04 19:00 ` ubizjak at gmail dot com
2012-11-04 19:00 ` ubizjak at gmail dot com
2012-11-05 11:44 ` corsepiu at gcc dot gnu.org
2012-11-05 12:12 ` ubizjak at gmail dot com
2012-11-05 12:29 ` ubizjak at gmail dot com
2012-11-05 12:42 ` corsepiu at gcc dot gnu.org [this message]
2012-11-05 14:15 ` ubizjak at gmail dot com
2012-11-05 14:25 ` ubizjak at gmail dot com
2012-11-05 14:39 ` corsepiu 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-55175-4-re26yFqP3N@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).