From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: gas is overly conservative with itc instruction
Date: Fri, 03 Mar 2006 01:13:45 +0000 [thread overview]
Message-ID: <1141348425.2906.14.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <B05667366EE6204181EABE9C1B1C0EB506C07A07@scsmsx401.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Wed, 2006-03-01 at 10:59, Chen, Kenneth W wrote:
> The stop after first mmi bundle is unnecessary. HJ, is it possible
> to get that relaxed a bit?
Yes. The double stop bit here is a bug. It is better to fix the kernel
assembly source, but the assembler should be fixed also. I wrote and
checked in a patch to fix it.
I tested this with a kernel build, and the only difference with the
patch is that the one extra stop bit you complained about is gone.
There were no other changes to the kernel binary.
[-- Attachment #2: patch.last.stop --]
[-- Type: text/plain, Size: 922 bytes --]
2006-03-02 James E Wilson <wilson@specifix.com>
* config/tc-ia64.c (emit_one_bundle): For IA64_OPCODE_LAST, if we
change the template, then clear md.slot[curr].end_of_insn_group.
Index: tc-ia64.c
===================================================================
RCS file: /cvs/src/src/gas/config/tc-ia64.c,v
retrieving revision 1.186
diff -p -p -r1.186 tc-ia64.c
*** tc-ia64.c 23 Feb 2006 21:36:17 -0000 1.186
--- tc-ia64.c 2 Mar 2006 22:32:53 -0000
*************** emit_one_bundle ()
*** 6855,6860 ****
--- 6855,6864 ----
changing NOPs in front of this slot. */
for (j = i; j < 3; ++j)
insn[j] = nop[ia64_templ_desc[required_template].exec_unit[j]];
+
+ /* We just picked a template that includes the stop bit in the
+ middle, so we don't need another one emitted later. */
+ md.slot[curr].end_of_insn_group = 0;
}
template = required_template;
}
prev parent reply other threads:[~2006-03-03 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 18:59 gas is overly conservative with itc instruction Chen, Kenneth W
2006-03-01 19:28 ` John S. Worley
2006-03-01 20:09 ` Chen, Kenneth W
2006-03-03 1:13 ` James E Wilson [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=1141348425.2906.14.camel@aretha.corp.specifix.com \
--to=wilson@tuliptree.org \
--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