public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "inaoka dot kazuhiro at renesas dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/28508] Assembler Error: operand out of ragne (145 not between -128 and 127) form m32r-target
Date: Thu, 27 Jul 2006 01:48:00 -0000	[thread overview]
Message-ID: <20060727014843.5409.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28508-5993@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from inaoka dot kazuhiro at renesas dot com  2006-07-27 01:48 -------
Created an attachment (id=11953)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11953&action=view)
test case

bc.s and bnc.s have the range (form -512 to 508) of PC-relative.

If all 2byte instruction have alignment code (pnop)of debug information,
we must use 254/508.
But it's rare case.

FAIL Sample>
m32r-linux-gnu-gcc -S -g -O2 -o line_test.s.ng line_test.c
/tmp/ccHkZoqt.s: Assembler messages:
/tmp/ccHkZoqt.s:22: Error: operand out of range (198 not between -128 and 127)

PASS Sample> without -g option
m32r-linux-gnu-gcc -S -O2 -o line_test.s line_test.c


-- 


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


  reply	other threads:[~2006-07-27  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  1:39 [Bug c/28508] New: " inaoka dot kazuhiro at renesas dot com
2006-07-27  1:48 ` inaoka dot kazuhiro at renesas dot com [this message]
2006-07-27  1:52 ` [Bug c/28508] " inaoka dot kazuhiro at renesas dot com
2006-07-27 10:20 ` [Bug target/28508] " nickc at redhat dot com
2006-07-27 12:22 ` [Bug target/28508] Assembler Error: operand out of range " nickc at gcc dot gnu dot org
2006-07-29  5:22 ` pinskia at gcc dot gnu dot org
2006-08-03  7:59 ` inaoka dot kazuhiro at renesas dot com
2007-04-28 10:11 ` tbm at cyrius dot com
2008-01-23 14:21 ` debian-gcc at lists dot debian 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=20060727014843.5409.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).