public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@nynexst.com
Cc: gas2@cygnus.com
Subject: Re: My registers spilleth over... (fwd)
Date: Tue, 15 Aug 1995 14:30:00 -0000	[thread overview]
Message-ID: <199508152130.RAA09556@sanguine.cygnus.com> (raw)
In-Reply-To: <9508152031.AA08641@nynexst.com>

   From: hjl@nynexst.com (H.J. Lu)
   Date: Tue, 15 Aug 95 16:30:38 EDT

   Forwarded message:
   From: Jim Paradis <paradis@amt.tay1.dec.com>
   Date: Thu, 3 Aug 1995 21:20:07 -0500 (EDT)

   (linux-gcc people can tune in now):  The first bug I found was when my
   freshly-built gas tried to build a "dummy" Alpha object file (basically, a
   six-line bit of assembly code that's nothing more than a single routine
   consiisting of a single "ret" instruction).  gas fell over dead when it
   tried to build it: got "Assertion failed in write.c".  Much tracking down
   finally got me to the following line of code:

	   fragp->fr_offset += newsize - size;

   All of the variables above are 64-bit "long long"'s.  newsize=16, size=12;
   therefore fragp->fr_offset should have been incremented by 12.  Instead it
   was incremented by 24.  I figure this is a bug in the handling of
   "long long"s by the i486 code generator; if I break the above apart into
   two statements:

	   fragp->fr_offset = fragp->fr_offset + newsize;
	   fragp->fr_offset = fragp->fr_offset - size;

   then everything works fine.

Note that this is a compiler bug.  Nothing needs to be changed in gas.

Ian


  reply	other threads:[~1995-08-15 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-15 13:34 H.J. Lu
1995-08-15 14:30 ` Ian Lance Taylor [this message]
1995-08-16  6:10 ` Michael Meissner

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=199508152130.RAA09556@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@nynexst.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).