From: Ian Lance Taylor <ian@cygnus.com>
To: don@pixsci.com
Cc: gas2@cygnus.com
Subject: Re: New bug in gas980329
Date: Mon, 30 Mar 1998 08:59:00 -0000 [thread overview]
Message-ID: <199803301659.LAA24393@subrogation.cygnus.com> (raw)
In-Reply-To: <3521B963898BD111AA6A006008A84516079B40@SERVER>
From: Don Bowman <don@pixsci.com>
Date: Mon, 30 Mar 1998 11:21:35 -0500
With the gas980329 drop, configured as mips-gnu-elf (from cygwin32),
the following fragment causes an assertion failure.
Interestingly, if I remove the .stabn, then it assembles OK.
I would have assumed the .stabn didn't affect the delays,
but I guess they must. Maybe to keep all of a 'C' line without
delay slots from the nex line?
------this fragment (f.s)-----
lbu $2,0($3)
LABEL:
.stabn 68,0,4,LABEL
addu $6,$6,-1
-------------------------------
This works fine with my sources. I expect the problem is due to your
MIPS_STABS_ELF patch.
On the MIPS, a label is automatically attached to the following
statement. You can see this happening in s_cons and s_align in
config/tc-mips.c. Perhaps some of that code is getting executed
inappropriately, when there is some confusion about the section.
Perhaps you have switched to the .stab section without calling
mips_emit_delays.
Actually, you don't want to call mips_emit_delays in this case; you
just want to somehow prevent the section checks from firing while you
are in the .stab section.
Ian
next prev parent reply other threads:[~1998-03-30 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 8:21 Don Bowman
1998-03-30 8:59 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-03-29 19:33 Don Bowman
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=199803301659.LAA24393@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=don@pixsci.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).