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] New: [SH] sh4-linux configured compiler rejects -m4-nofpu Date: Fri, 21 Nov 2014 02:04:00 -0000 [thread overview] Message-ID: <bug-64008-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64008 Bug ID: 64008 Summary: [SH] sh4-linux configured compiler rejects -m4-nofpu Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: olegendo at gcc dot gnu.org CC: kkojima at gcc dot gnu.org, segher at gcc dot gnu.org Target: sh*-*-* This issue has been mentioned by Segher while he was trying to build an SH4 linux kernel on a powerpc host. Segher, could you please add the configure options you have used for that? Looking at the SUPPORT_SH* macros in sh.h starting at line 161, it's not entirely clear to me what those are trying to accomplish. For instance: #if SUPPORT_SH1 #define SUPPORT_SH2 1 #endif ... to me reads that when SH1 support is enabled (-m1 option), then support for SH2 (-m2 option) is also enabled. This looks like it should be the other way around. Kaz, do you have any idea why these SUPPORT_SH* macros are needed? Why isn't just every CPU/FPU type marked as supported?
next reply other threads:[~2014-11-21 2:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-21 2:04 olegendo at gcc dot gnu.org [this message] 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 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@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: linkBe 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).