From: Pavel Roskin <pavel_roskin AT geocities.com>
To: binutils AT sourceware.cygnus.com
Subject: assertion failure in coff-i386.c on .code16
Date: Fri, 17 Sep 1999 01:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9909171206550.30517-100000@intra.typhoon.spb.ru> (raw)
Hello!
I've compiled binutils-990916 snapshot on Cygwin B20.1 (standard
installation + egcs-1.1.1)
While configuring GNU GRUB I have noticed that "as" cannot compile the
following file:
.code16
l1: addr32
movb %al, l1
D:\home\proski\src\bfd>as test.s
test.s: Assembler messages:
test.s:2: Warning: stand-alone `addr32' prefix
as: bfd assertion fail coff-i386.c:498
test.s:3: Error: Cannot represent relocation type BFD_RELOC_16
Actually, there is an error in the test file. It should be
.code16
l1: addr32 movb %al, l1
and this can be compiled.
In any case, the assertion failure must indicate a problem. You think it
cannot happen, but it can.
By the way, please consider changing the bug reporting address from
bug-gnu-utils@gnu.org to binutils@sourceware.cygnus.com everywhere in the
sources.
Pavel Roskin
next reply other threads:[~1999-09-17 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 1:21 Pavel Roskin [this message]
1999-09-17 3:29 ` Alan Modra
1999-09-17 6:23 ` Pavel Roskin
1999-09-17 18:10 ` Alan Modra
1999-09-17 7:03 ` 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.LNX.4.10.9909171206550.30517-100000@intra.typhoon.spb.ru \
--to=binutils@sourceware.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).