public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siarhei dot siamashka at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/42321] New: NEON/VFP registers from inline assembly clobber list are saved/restored incorrectly Date: Mon, 07 Dec 2009 14:34:00 -0000 [thread overview] Message-ID: <bug-42321-14457@http.gcc.gnu.org/bugzilla/> (raw) Test program: /************************/ void f() { asm volatile("veor d8, d8, d8" : : :"d8","d9","d10","d11","d14","d15"); } /************************/ $ gcc -c -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -O2 test.c $ objdump -d test.o 00000000 <f>: 0: ed2d8b08 vpush {d8-d11} 4: ed2deb04 vpush {d14-d15} 8: f3088118 veor d8, d8, d8 c: ecbd8b08 vpop {d8-d11} 10: ecbdeb04 vpop {d14-d15} 14: e12fff1e bx lr The order of the last two vpop instructions is messed up. -- Summary: NEON/VFP registers from inline assembly clobber list are saved/restored incorrectly Product: gcc Version: 4.4.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: inline-asm AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: siarhei dot siamashka at gmail dot com GCC build triplet: armv4tl-softfloat-linux-gnueabi GCC host triplet: armv4tl-softfloat-linux-gnueabi GCC target triplet: armv4tl-softfloat-linux-gnueabi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42321
next reply other threads:[~2009-12-07 14:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-07 14:34 siarhei dot siamashka at gmail dot com [this message] 2009-12-07 14:42 ` [Bug inline-asm/42321] " siarhei dot siamashka at gmail dot com 2009-12-07 15:52 ` ramana at gcc dot gnu dot org 2009-12-07 15:56 ` rearnsha at gcc dot gnu dot org 2009-12-09 16:55 ` ramana at gcc dot gnu dot org 2010-01-14 16:21 ` ramana at gcc dot gnu dot org 2010-03-21 15:59 ` rearnsha at gcc dot gnu dot org 2010-03-21 20:27 ` rearnsha at gcc dot gnu dot org 2010-03-21 20:30 ` [Bug target/42321] " rearnsha at gcc dot gnu 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-42321-14457@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).