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] NEON/VFP registers from inline assembly clobber list are saved/restored incorrectly
Date: Mon, 07 Dec 2009 14:42:00 -0000	[thread overview]
Message-ID: <20091207144213.8888.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42321-14457@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from siarhei dot siamashka at gmail dot com  2009-12-07 14:42 -------
Modifying the program to list q-registers in the clobber list provides even
more interesting results:
/************************/
void f()
{
    asm volatile("veor d8, d8, d8" : : :"q4","q5","q7");
}
/************************/

$ gcc -c -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -O2 test.c
$ objdump -d test.o

00000000 <f>:
   0:   ed2d8b02        vpush   {d8}
   4:   ed2dab02        vpush   {d10}
   8:   ed2deb02        vpush   {d14}
   c:   f3088118        veor    d8, d8, d8
  10:   ecbd8b02        vpop    {d8}
  14:   ecbdab02        vpop    {d10}
  18:   ecbdeb02        vpop    {d14}
  1c:   e12fff1e        bx      lr

Now in addition to the mismatched save/restore order, only lower halves of
q-registers get saved.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42321


  reply	other threads:[~2009-12-07 14:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 14:34 [Bug inline-asm/42321] New: " siarhei dot siamashka at gmail dot com
2009-12-07 14:42 ` siarhei dot siamashka at gmail dot com [this message]
2009-12-07 15:52 ` [Bug inline-asm/42321] " 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=20091207144213.8888.qmail@sourceware.org \
    --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: link
Be 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).