public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64008] [SH] sh4-linux configured compiler rejects -m4-nofpu
Date: Sat, 22 Nov 2014 04:30:00 -0000 [thread overview]
Message-ID: <bug-64008-4-LrFGAW7IpC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64008-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64008
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iwamatsu at nigauri dot org
--- Comment #2 from Oleg Endo <olegendo at gcc dot gnu.org> ---
I guess the SUPPORT_* macros are there to prevent scenarios like:
- SH4 machine with a GCC configured to produce SH4 code (with FPU, double
precision by default) without any -m options.
- No soft-fpu support code nor other multilib support code is present on the
SH4 machine
- Compiling a program with -m2 would produce SH2 code which might use soft-fpu
support code and various libgcc functions (e.g. dynamic shifts)
- Link error
Looking at config.gcc, it seems that specifying --enable-incomplete-targets
solves the problem, as it effectively enables all the target options.
Some related links:
https://lkml.org/lkml/2014/7/8/732
http://lists.openwall.net/linux-kernel/2014/07/08/1071
and a patch from somewhere else that seems related:
http://cgit.openembedded.org/openembedded/plain/recipes/gcc/gcc-4.5/sh4-multilib.patch
Maybe Nobuhiro has some comments regarding this issue...
next prev parent reply other threads:[~2014-11-22 4:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 2:04 [Bug target/64008] New: " olegendo at gcc dot gnu.org
2014-11-21 5:09 ` [Bug target/64008] " kkojima at gcc dot gnu.org
2014-11-22 4:30 ` olegendo at gcc dot gnu.org [this message]
2014-11-22 7:59 ` kkojima at gcc dot gnu.org
2014-11-22 14:58 ` segher at gcc dot gnu.org
2014-11-23 1:23 ` kkojima at gcc dot gnu.org
2014-12-21 20:56 ` olegendo 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-64008-4-LrFGAW7IpC@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).