public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/51743] [ia64] Many gcc.dg/torture/vshuf*.c tests FAIL with -O2 -mbig-endian Date: Wed, 04 Jan 2012 10:35:00 -0000 [thread overview] Message-ID: <bug-51743-4-nRzp83W7DW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51743-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51743 --- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-04 10:34:43 UTC --- (In reply to comment #2) > Uh... can you even force ia64-linux to run in big-endian mode? > Just because you said -mbig-endian doesn't mean it is. I don't > see anything in the linux kernel that allows per-process endian > switching. Hm, should we then reject this switch on linux? > Do these same failures appear for ia64-hpux?
next prev parent reply other threads:[~2012-01-04 10:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-03 16:49 [Bug target/51743] New: " ubizjak at gmail dot com 2012-01-03 16:50 ` [Bug target/51743] " ubizjak at gmail dot com 2012-01-03 20:11 ` rth at gcc dot gnu.org 2012-01-04 7:12 ` ubizjak at gmail dot com 2012-01-04 10:35 ` rguenth at gcc dot gnu.org [this message] 2012-01-05 0:34 ` rth at gcc dot gnu.org 2013-12-12 18:17 ` ubizjak at gmail dot com
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-51743-4-nRzp83W7DW@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).