public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "christophe.lyon at st dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54517] New: wrong inlining of builtin_shuffle on ARM/big-endian Date: Fri, 07 Sep 2012 12:10:00 -0000 [thread overview] Message-ID: <bug-54517-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54517 Bug #: 54517 Summary: wrong inlining of builtin_shuffle on ARM/big-endian Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: christophe.lyon@st.com Created attachment 28146 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28146 testcase As exposed by the attached sample code, GCC for ARM/big-endian produces incorrect code when inlining functions performing builtin_shuffle. Compile the attached program at -O2 with GCC configured for armeb-none-linux-gnueabi) and execute it with qemu-armeb, it should be OK. Then edit the source code such that NOINLINE now expands into the empty string: #define NOINLINE, re-compile & execute: the code aborts.
next reply other threads:[~2012-09-07 12:10 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-07 12:10 christophe.lyon at st dot com [this message] 2013-02-20 0:14 ` [Bug target/54517] " ramana at gcc dot gnu.org 2013-02-20 0:25 ` pinskia 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-54517-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).