public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Don Bowman <don@pixsci.com>
To: "'gas2@cygnus.com'" <gas2@cygnus.com>
Subject: New bug in gas980329
Date: Mon, 30 Mar 1998 08:21:00 -0000	[thread overview]
Message-ID: <3521B963898BD111AA6A006008A84516079B40@SERVER> (raw)

--apologies for the earlier MIME/HTML. I'm having a fight with out
--corporate standard, MS Exchange. This message is just resent in
--plain text.

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
-------------------------------

$ as -v -o f.o f.s
GNU assembler version 980329 (mips-gnu-elf), using BFD version 980329
f.s: Assembler messages:
f.s:3: Internal error!
Assertion failure in mips_emit_delays at ../../gas-980329/gas/config/tc-mips.c line 2280.
Please report this bug.


          for (l = insn_labels; l != NULL; l = l->next)
            {
              assert (S_GET_SEGMENT (l->label) == now_seg); <<<<<<<< This is line 2280
              l->label->sy_frag = frag_now;
              S_SET_VALUE (l->label, (valueT) frag_now_fix ());
              /* mips16 text labels are stored as odd.  */
              if (mips_opts.mips16)
                ++l->label->sy_value.X_add_number;
            }

             reply	other threads:[~1998-03-30  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-30  8:21 Don Bowman [this message]
1998-03-30  8:59 ` Ian Lance Taylor
  -- 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=3521B963898BD111AA6A006008A84516079B40@SERVER \
    --to=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).