public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tp+gcc at pambor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46164] Local variables in specified registers don't work correctly with inline asm operands
Date: Wed, 13 Aug 2014 07:47:00 -0000	[thread overview]
Message-ID: <bug-46164-4-tT1qjMXWRu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46164-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46164

--- Comment #4 from Tim Pambor <tp+gcc at pambor dot com> ---
Created attachment 33307
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33307&action=edit
testcase for gcc 4.9.1

I think this bug is still present in gcc 4.9.1 and 4.8.4.

I could reproduce the problem with the attached testcase using gcc 4.8.4 with
-O1 and -Og and 4.9.1 with -O1. -O0, -O2, -O3, -Os generated correct code. It
generated the following assembler code:

...
  mov r0, r0    @ r0
  mov r4, r4    @ r1
  mov r2, r2    @ r2
...

Expected would have been:

...
  mov r0, r0    @ r0
  mov r1, r1    @ r1
  mov r2, r2    @ r2
...


  parent reply	other threads:[~2014-08-13  7:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 10:13 [Bug middle-end/46164] New: " siarhei.siamashka at gmail dot com
2010-10-25 10:37 ` [Bug middle-end/46164] " siarhei.siamashka at gmail dot com
2010-10-25 12:32 ` siarhei.siamashka at gmail dot com
2010-10-27 21:13 ` pinskia at gcc dot gnu.org
2014-08-13  7:47 ` tp+gcc at pambor dot com [this message]
2014-08-13  7:51 ` tp+gcc at pambor dot com
2014-08-13  7:55 ` tp+gcc at pambor dot com
2015-01-22 11:02 ` Hale.Wang at arm dot com
2015-01-26 10:00 ` Hale.Wang at arm dot com
2015-01-27  8:03 ` Hale.Wang at arm dot com
2024-03-26 22:21 ` 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-46164-4-tT1qjMXWRu@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: 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).