public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egnor at ofb dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/16350] gcc only understands little endian ARM systems Date: Thu, 09 Feb 2012 17:54:00 -0000 [thread overview] Message-ID: <bug-16350-4-HRN1CbOLRl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-16350-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16350 Dan Egnor <egnor at ofb dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egnor at ofb dot net --- Comment #27 from Dan Egnor <egnor at ofb dot net> 2012-02-09 17:53:24 UTC --- The precise scope of this bug is unclear to me. Big endian Linux targets _do_ seem to work now, and -mbig-endian generates correct code regardless; however, non-Linux big-endian targets do not seem to be recognized as big-endian by default (which means libgcc is built in little endian mode, etc.). See bug 52187 (which may be a dupe of this one, depending on how you interpret the scope of this bug).
next parent reply other threads:[~2012-02-09 17:54 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-16350-4@http.gcc.gnu.org/bugzilla/> 2012-02-09 17:54 ` egnor at ofb dot net [this message] 2012-02-13 23:25 ` mkl at pengutronix dot de 2012-02-13 23:28 ` mkl at pengutronix dot de 2013-01-09 11:37 ` sam.thursfield at codethink dot co.uk 2013-01-09 11:47 ` sam.thursfield at codethink dot co.uk 2013-03-20 0:46 ` pinskia at gcc dot gnu.org [not found] <bug-16350-8873@http.gcc.gnu.org/bugzilla/> 2006-04-12 4:01 ` vapier at gentoo dot org 2006-08-08 13:31 ` mkl at pengutronix dot de 2006-08-08 13:33 ` mkl at pengutronix dot de 2006-11-03 13:49 ` mkl at pengutronix dot de 2006-11-29 9:55 ` mkl at pengutronix dot de 2007-11-07 20:50 ` aldot at gcc dot gnu dot org 2007-11-08 13:44 ` nickc at gcc dot gnu dot org 2007-11-08 13:47 ` nickc at redhat dot com 2007-11-08 14:26 ` buytenh at wantstofly dot org 2007-11-10 3:53 ` patchapp at dberlin dot org 2007-11-10 3:53 ` patchapp at dberlin dot org 2007-11-10 18:05 ` patchapp at dberlin dot org 2007-11-22 19:01 ` patchapp at dberlin dot org 2008-07-04 13:19 ` pmaydell at chiark dot greenend dot org dot uk 2009-05-06 10:53 ` ramana at gcc dot gnu dot org 2009-06-07 22:51 ` aldot at gcc dot gnu dot org 2009-12-09 16:10 ` ramana at gcc dot gnu dot org 2010-01-26 17:44 ` aldot at gcc dot gnu dot org 2004-07-03 15:45 [Bug driver/16350] New: " buytenh at wantstofly dot org 2004-07-03 22:12 ` [Bug target/16350] " pinskia at gcc dot gnu dot org 2004-07-03 22:16 ` pinskia at gcc dot gnu dot org 2004-07-03 23:41 ` dank at kegel dot com 2004-08-08 18:44 ` dank at kegel dot com 2004-10-13 1:20 ` pinskia at gcc dot gnu dot org 2005-02-25 21:31 ` vapier at gentoo dot 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-16350-4-HRN1CbOLRl@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).