This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Instruction bundling on IA64 and the Intel Assembler
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 15 Dec 2003 14:05:04 -0800
- Subject: Re: Instruction bundling on IA64 and the Intel Assembler
- References: <10312152200.AA20379@vlsi1.ultra.nyu.edu>
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> Always print "{.whatever" in the bundle_selector output template;
> then, whenever bundling() goes to emit a bundle_selector, have it also
> look three insns ahead and emit an "}" insn. I think this will always
> be right, not interfere with labels and directives, and shouldn't
> require you to comprehend this problem function.
>
> It still requires *some* comprehension because it's not completely clear
> when those three insns are written out (consider nops).
NOPs have to be considered when determining bundle boundaries, so I think
that the naive three-insns-farther approach will be correct. (Must
not count things which are not INSN/JUMP_INSN/CALL_INSN of course.)
> However, that still doesn't address part of Geert's comment
... because I have nothing to add to that part.
zw