public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: cgd@sibyte.com (Chris G. Demetriou) To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: target/2467: MIPS cross-assembler reports error for constant PC-relative branches Date: Tue, 03 Apr 2001 17:16:00 -0000 [thread overview] Message-ID: <20010404001601.26267.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR target/2467; it has been noted by GNATS. From: cgd@sibyte.com (Chris G. Demetriou) To: vvortex1@home.com Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: target/2467: MIPS cross-assembler reports error for constant PC-relative branches Date: 03 Apr 2001 17:13:35 -0700 vvortex1@home.com writes: > When given a PC-relative branch instruction with a numeric immediate, such as "bne $0, $0, 16", the MIPS cross-assembler correctly parses the expression but fails to generate object code. It reports "Can not represent BFD_RELOC_16_PCREL_S2 relocation in this object file format". Strictly speaking, no relocation information is necessary because the value of the immediate field is already known. This error is generated in all known emulation modes. > >How-To-Repeat: > Contents of broken.s: > bne $0, $0, 8 > nop > nop > nop > nop > ------ > > To reproduce, run: > % mips64orion-rtems-as broken.s > None of the configuration options seem to have any effect on this glitch. > >Fix: > Beats me ;-) The assembler should simply store the supplied numeric operand shifted right two places. (1) why have you reported this as a GCC bug? (2) in general, I suspect that what's happening here is that it's taking '8' as the address '8', and trying to convert that to a branch using a PC-relative relocation. I would guess that what you mean here is ".+8" or similar. I find that, indeed, with current-ish assemblers: bne $0, $0, .+8 assembles into: 0: 14000001 bnez $zero,0x8 4: 00000000 nop which is, i believe, what you want. cgd
next reply other threads:[~2001-04-03 17:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-04-03 17:16 Chris G. Demetriou [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-11 20:55 ljrittle 2001-04-02 23:36 vvortex1
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=20010404001601.26267.qmail@sourceware.cygnus.com \ --to=cgd@sibyte.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).