From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: gas-971208 mips64orion-rtems internal error
Date: Sat, 20 Dec 1997 11:00:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971220124850.2016I-100000@vespucci.advicom.net> (raw)
The public domain floating point test paranoia when compiled by egcs 1.0
generates code which causes an internal error in gas. I have cut the code
down to the following:
.file 1 "p1.c"
# -G value = 8, Cpu = 4650, ISA = 3
# GNU C version egcs-2.90.21 971202 (egcs-1.00 release)
(mips64orion-rtems) compiled by GNU C version 2.7.2.
# options passed: -mcpu=4650
# options enabled: -fpeephole -ffunction-cse -fkeep-static-consts
# -fpcc-struct-return -fcommon -fverbose-asm -fgnu-linker
-fargument-alias
# -mgas -mfp64 -mgp64 -meb -mcpu=4650
gcc2_compiled.:
__gnu_compiled_c:
.globl One
.align 3
One:
.word 0x3ff00000 # 1
.word 0x00000000
.globl paranoia
.ent paranoia
paranoia:
.frame $fp,72,$31 # vars= 8, regs= 3/1, args= 32,
extra= 0
.mask 0xc0010000,-16
.fmask 0x00100000,-8
s.d $f0,One
which when assembled as follows:
mips64orion-rtems-as -mcpu=4650 -v p1.s
generates this error message:
p1.s: Assembler messages:
p1.s:23: Internal error!
Assertion failure in macro_build at ../../src/gas/config/tc-mips.c line
2365.
Please report this bug.
This file assembles with a warning about the missing ".end or .bend" with
binutils 2.8.1.
Thanks.
--joel
Joel Sherrill Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (205) 722-9985
next reply other threads:[~1997-12-20 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-20 11:00 Joel Sherrill [this message]
1997-12-22 9:19 ` Ian Lance Taylor
1997-12-22 9:27 ` Joel Sherrill
1997-12-22 9:30 ` Ian Lance Taylor
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=Pine.BSF.3.96.971220124850.2016I-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
/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).