From: Joel Sherrill <joel@merlin.gcs.redstone.army.mil>
To: gas2@cygnus.com
Subject: possible bug in bfd/sunos.c
Date: Tue, 28 May 1996 08:56:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.91.960528101146.13030G-100000@merlin> (raw)
Version binutils-2.6.
I am configured for sparc-rtems which is essentially the same as
sparc-aout with different CPP_PREDEFINES. I use the following assembly
file (cut down to the point of uselessness :) ):
.text
sethi %hi(stack_space + 16 * 1024), %g1
call _main
.comm stack_space, 16 * 1024
I then run this script on it:
sparc-rtems-as -o test.o test.s
sparc-rtems-ld test.o
and get the following message:
bfd assertion fail ../../src/bfd/sunos.c:1839
If I delete any line in the file other than the .text, the problem goes
away. Is this something I am doing which is stupid? Is this a real
problem? I looked at the source for this problem but (in my usual luck)
requires real expertise to even read.
I noticed that the assert in question has changed in the latest binutils
snapshot. Is this the bug? If so is there a simple patch for this
specific problem?
Any assistance is appreciated.
--joel
next reply other threads:[~1996-05-28 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-28 8:56 Joel Sherrill [this message]
1996-05-28 9:07 ` Ian Lance Taylor
1996-05-28 12:14 ` Joel Sherrill
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.SV4.3.91.960528101146.13030G-100000@merlin \
--to=joel@merlin.gcs.redstone.army.mil \
--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).