public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54983] ARM gcc creates invalid assembly: bad immediate value for 8-bit offset (1024)
Date: Fri, 19 Oct 2012 11:01:00 -0000	[thread overview]
Message-ID: <bug-54983-4-AFyzCrTo3F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54983-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-10-19 11:01:13 UTC ---
I think there might be an issue with some of the inline-asm in asm/io.h:
static inline __attribute__((always_inline))
__attribute__((no_instrument_function)) void __raw_writew(u16 val, volatile
void *addr)
{
 asm volatile("strh %1, %0"
       : "+Qo" (*(volatile u16 *)addr)
       : "r" (val));


Also what options are being passed to the gcc?


  reply	other threads:[~2012-10-19 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 10:39 [Bug c/54983] New: " hechtb at gmail dot com
2012-10-19 11:01 ` pinskia at gcc dot gnu.org [this message]
2012-10-19 11:55 ` [Bug c/54983] " hechtb at gmail dot com
2012-10-19 16:55 ` rearnsha at gcc dot gnu.org
2012-10-20 10:30 ` hechtb 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-54983-4-AFyzCrTo3F@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).