From: Ian Lance Taylor <ian@cygnus.com>
To: robertl@sco.com
Cc: egcs-bugs@egcs.cygnus.com, gas2@cygnus.com
Subject: Re: dwarf-1 egcs outputs bad .s / GAS allows it.
Date: Sat, 27 Mar 1999 07:23:00 -0000 [thread overview]
Message-ID: <199903271523.HAA15972@rtl.cygnus.com> (raw)
In-Reply-To: <19990326213126.A3658@rjlhome.sco.com>
Date: Fri, 26 Mar 1999 21:31:26 -0600
From: Robert Lipe <robertl@sco.com>
HERE-> .2byte 0xfffffff0
Should bit_offset be masked to fit in 16 bits? Should it be .4byte?
Should this be an impossible combination anyway? Why does GAS allow this?
gas should issue a warning for this case. It doesn't because it needs
to accept
.2byte -10
and it is getting confused in the obvious way. It's a bug.
Ian
prev parent reply other threads:[~1999-03-27 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-26 19:32 Robert Lipe
1999-03-27 7:23 ` Ian Lance Taylor [this message]
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=199903271523.HAA15972@rtl.cygnus.com \
--to=ian@cygnus.com \
--cc=egcs-bugs@egcs.cygnus.com \
--cc=gas2@cygnus.com \
--cc=robertl@sco.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).