From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gas dependency checker bug [forwarded message from Xavier Leroy]
Date: Wed, 16 Aug 2000 03:22:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205333@msgid-missing> (raw)
1- "addl" vs. "adds"
... no DV reported for addl
This is a bug in gas. addl takes a special operand type gr0-gr3 (in gas
IA64_OPND_R3_2) and this operand type was accidentally left out of the
dv checking code. addl is the only instruction using this operand type,
so it is the only instruction effected by this problem. This is easy to fix.
2- Loads and stores with postincrement.
This is another oversight. The code checking for operands modified by an
instruction doesn't include memory operands with postincrement addressing
modes. This one is a little harder to fix, because the opcodes files need to
be modified to indicate which instructions are postincrement, and then gas
needs to use the new info, so I ended up with a pretty big patch.
While I was at it, I also fixed a few gas testsuite failures, added new
gas testsuite cases for these two bugs, and fixed some warnings from the
ia64-gen program. The result is a 64K patch if I delete the diffs for
gas/testsuite/gas/ia64/opc-f.d and opcodes/ia64-asmtab.c both of which are
generated files. With those files it is a 687K patch.
I am doing a little more cleanup and testing of these patches, and I expect
to check them into the FSF binutils source tree tomorrow.
Jim
next reply other threads:[~2000-08-16 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-16 3:22 Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-06 17:57 [Linux-ia64] gas dependency checker bug [forwarded message from Xavier Leroy] David Mosberger
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=marc-linux-ia64-105590678205333@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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