public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50694] SH Target: SH2A little endian does not actually work Date: Thu, 20 Oct 2011 22:40:00 -0000 [thread overview] Message-ID: <bug-50694-4-ACvK1yDIBY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50694-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50694 --- Comment #8 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2011-10-20 22:40:27 UTC --- (In reply to comment #7) This problem doesn't require the theoretical/mathematical completeness. There are many inappropriate combinations of options which don't get any warning when running compiler and configurations. The important thing is to warn very confusing ones from the user's point of view. So your patch in #6 or even one liner in #2 would be OK and enough for this PR, I think.
next prev parent reply other threads:[~2011-10-20 22:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-11 0:06 [Bug target/50694] New: " oleg.endo@t-online.de 2011-10-13 19:54 ` [Bug target/50694] " oleg.endo@t-online.de 2011-10-16 23:29 ` kkojima at gcc dot gnu.org 2011-10-18 21:33 ` oleg.endo@t-online.de 2011-10-18 22:24 ` kkojima at gcc dot gnu.org 2011-10-18 22:37 ` oleg.endo@t-online.de 2011-10-18 22:51 ` kkojima at gcc dot gnu.org 2011-10-20 18:44 ` oleg.endo@t-online.de 2011-10-20 22:40 ` kkojima at gcc dot gnu.org [this message] 2011-10-30 12:46 ` oleg.endo@t-online.de 2011-11-14 0:32 ` kkojima at gcc dot gnu.org 2012-02-26 23:26 ` 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-50694-4-ACvK1yDIBY@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).