public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49448] arm-tab-linux-gnu-eabi enableds big endian when it should not Date: Tue, 28 Feb 2012 15:28:00 -0000 [thread overview] Message-ID: <bug-49448-4-PXoExQRXOt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49448-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49448 --- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-02-28 15:26:13 UTC --- Author: rearnsha Date: Tue Feb 28 15:26:02 2012 New Revision: 184626 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184626 Log: PR target/49448 * config.gcc (arm*-*-linux*): Use an unambiguous pattern for detecting big-endian triplets. Modified: trunk/gcc/ChangeLog trunk/gcc/config.gcc
next prev parent reply other threads:[~2012-02-28 15:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-17 5:34 [Bug other/49448] New: gcc configure script wrongly detect TARGET_BIG_ENDIAN_DEFAULT goughost at yahoo dot com.cn 2011-06-17 7:26 ` [Bug other/49448] " schwab@linux-m68k.org 2012-01-28 20:04 ` [Bug target/49448] arm-tab-linux-gnu-eabi enableds big endian when it should not pinskia at gcc dot gnu.org 2012-02-28 15:28 ` rearnsha at gcc dot gnu.org [this message] 2012-04-12 14:11 ` rearnsha at gcc dot gnu.org 2012-04-12 14:12 ` rearnsha at gcc dot gnu.org 2012-04-12 14:17 ` rearnsha 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-49448-4-PXoExQRXOt@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).