Displaying 9 results from an estimated 9 matches for "0xl00000000000000003fff000000000000".
2018 May 22
2
Rewriting calls to varargs functions
...multiple values, or insert a padding value. For
example, for the target mips64-unknown-linux-gnu, a call like
printf("asdf%Lf", 1.0L); gets lowered to the following:
%call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x i8],
[5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
0xL00000000000000003FFF000000000000) #2"
I would to hear more suggestions whether it is safe or not. Seems like
for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
Any folks from Clang/LLVM to bring more information about "varargs vs ABI
vs LLVM vs Clang"?
And whether we can rewrite calls to varargs fun...
2018 May 22
4
Rewriting calls to varargs functions
...padding value. For
> example, for the target mips64-unknown-linux-gnu, a call like
> printf("asdf%Lf", 1.0L); gets lowered to the following:
>
> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x i8],
> [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
> 0xL00000000000000003FFF000000000000) #2"
>
>
> I would to hear more suggestions whether it is safe or not. Seems like
> for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>
> Any folks from Clang/LLVM to bring more information about "varargs vs ABI
> vs LLVM vs Clang"?
> And whethe...
2018 May 22
0
Rewriting calls to varargs functions
...padding value. For example, for the target
> mips64-unknown-linux-gnu, a call like printf("asdf%Lf", 1.0L); gets
> lowered to the following:
>
> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x
> i8], [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
> 0xL00000000000000003FFF000000000000) #2"
>
>
> I would to hear more suggestions whether it is safe or not. Seems like
> for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>
> Any folks from Clang/LLVM to bring more information about "varargs vs
> ABI vs LLVM vs Clang"?
> And wheth...
2018 May 22
4
Rewriting calls to varargs functions
...gt; example, for the target mips64-unknown-linux-gnu, a call like
>> printf("asdf%Lf", 1.0L); gets lowered to the following:
>>
>> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x i8],
>> [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
>> 0xL00000000000000003FFF000000000000) #2"
>>
>>
>> I would to hear more suggestions whether it is safe or not. Seems like
>> for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>>
>> Any folks from Clang/LLVM to bring more information about "varargs vs ABI
>> vs LLVM vs...
2018 May 22
0
Rewriting calls to varargs functions
...the target mips64-unknown-linux-gnu, a call like
>> printf("asdf%Lf", 1.0L); gets lowered to the following:
>>
>> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds
>> ([5 x i8], [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
>> 0xL00000000000000003FFF000000000000) #2"
>>
>>
>> I would to hear more suggestions whether it is safe or not. Seems
>> like for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>>
>> Any folks from Clang/LLVM to bring more information about
>> "varargs vs...
2018 May 22
0
Rewriting calls to varargs functions
..., a call
>>> like printf("asdf%Lf", 1.0L); gets lowered to the following:
>>>
>>> %call = call i32 (i8*, ...) @printf(i8* getelementptr
>>> inbounds ([5 x i8], [5 x i8]* @.str, i32 0, i32 0), i64
>>> undef, fp128 0xL00000000000000003FFF000000000000) #2"
>>>
>>>
>>> I would to hear more suggestions whether it is safe or not.
>>> Seems like for mips Clang produces some weird IR, but e.g.
>>> x86 IR seems ok.
>>>
>>> Any folks from Clang/LLVM to b...
2018 May 22
0
Rewriting calls to varargs functions
...target mips64-unknown-linux-gnu, a call like
>>> printf("asdf%Lf", 1.0L); gets lowered to the following:
>>>
>>> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x
>>> i8], [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
>>> 0xL00000000000000003FFF000000000000) #2"
>>>
>>>
>>> I would to hear more suggestions whether it is safe or not. Seems like
>>> for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>>>
>>> Any folks from Clang/LLVM to bring more information about "varargs vs...
2018 May 23
1
Rewriting calls to varargs functions
...wn-linux-gnu, a call
>>>> like printf("asdf%Lf", 1.0L); gets lowered to the following:
>>>>
>>>> %call = call i32 (i8*, ...) @printf(i8* getelementptr inbounds ([5 x
>>>> i8], [5 x i8]* @.str, i32 0, i32 0), i64 undef, fp128
>>>> 0xL00000000000000003FFF000000000000) #2"
>>>>
>>>>
>>>> I would to hear more suggestions whether it is safe or not. Seems like
>>>> for mips Clang produces some weird IR, but e.g. x86 IR seems ok.
>>>>
>>>> Any folks from Clang/LLVM to bring more information...
2017 Oct 03
2
invalid code generated on Windows x86_64 using skylake-specific features
I figured it out. I was using this implementation of __chkstk from
compiler-rt:
DEFINE_COMPILERRT_FUNCTION(___chkstk)
push %rcx
cmp $0x1000,%rax
lea 16(%rsp),%rcx // rsp before calling this routine -> rcx
jb 1f
2:
sub $0x1000,%rcx
test %rcx,(%rcx)
sub $0x1000,%rax
cmp $0x1000,%rax
ja 2b
1: