Displaying 3 results from an estimated 3 matches for "__2e_str".
Did you mean:
__2e_str1
2009 Jun 16
0
[LLVMdev] x86 Intel Syntax and MASM 9.x
On Mon, Jun 15, 2009 at 11:21 PM, Gaster,
Benedict<Benedict.Gaster at amd.com> wrote:
> I can get this two work with additional changes to X86InstrInfocpp but
> the problem I have with this approach is that it introduces a lot of
> duplication, when all I really want to do is parameterize the final
> field in the string "shl{b}\t{%cl, $dst|$dst, %CL}". I was wondering
2009 Jun 16
2
[LLVMdev] x86 Intel Syntax and MASM 9.x
Hi Eli,
Thanks for the response I have one question inline.
Regards,
Ben
[...]
> The main problem that I have hit is regarding the use of CL register
in the
> shift instructions. The problem is that ATT syntax states that it
should be
> referenced as "%cl" while Intel says just "cl" but these references
occur in
> X86InstInfo.td and this means that it is shared
2009 Jun 16
5
[LLVMdev] x86 Intel Syntax and MASM 9.x
...LLVM is sometimes generating 32
alignment, for example, consider the following code:
float bar(float fy, float fx)
{
static const double foo[ 241] = {
6.24188099959573430842e-02,
6.63088949198234745008e-02,
}
}
Is generating the data segment:
_data segment PARA 'DATA'
__2E_str: ; .str
db 'out',0
__2E_str1: ; .str1
db 'in',0
public ___some_other_sruct_data
ALIGN 4
___some_other_sruct_data: ;
dd 7 ; 0x7
dd...