Displaying 20 results from an estimated 392 matches for "s128".
Did you mean:
128
2013 Mar 15
6
[LLVMdev] Simple question
...to assign a constant integer value to
the variable in llvm ir.
The following returns 12, and %var2 = 12.
; ModuleID = 't.c'
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-pc-linux-gnu"
define i32 @test() nounwind readnone {
%var1 = xor i32 0, 0
%var2 = add i32 %var1, 12
ret i32 %var2
}
Why can't I do?:
; ModuleID = 't.c'
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:...
2018 Jan 04
0
AllocateTarget for ELF objects on Darwin
...Interface, I switched the format of the in-memory object files to ELF. I
thought this target triple should do:
Triple TT;
TT.setTriple(sys::getProcessTriple());
TT.setObjectFormat(llvm::Triple::ELF);
But Clang exits with an error:
backend data layout 'e-m:e-i64:64-f80:128-n8:16:32:64-S128'
does not match expectedtarget description
'e-m:o-i64:64-f80:128-n8:16:32:64-S128'
1 error generated.
The target selection is a little tricky here and I wonder if it's on
purpose or not. One solution is to add another line:
TT.setOS(llvm::Triple::UnknownOS);
This line rem...
2015 Feb 18
3
[LLVMdev] Calling into non-linked function via a pointer
...edef int fn(int);
>
> int test(fn f, int val){
> return f(val);
> }
>
> -----------
>
> Compiled with: clang callfuncptr.c -O -S -emit-llvm -o callfuncptr.ll
>
> ; ModuleID = 'callfuncptr.c'
>
> target datalayout = "e-m:o-i64:64-f80:128-n8:16:32:64-S128"
>
> target triple = "x86_64-apple-macosx10.10.0"
>
>
> ; Function Attrs: nounwind ssp uwtable
>
> define i32 @test(i32 (i32)* nocapture %f, i32 %val) #0 {
>
> %1 = tail call i32 %f(i32 %val) #1
>
> ret i32 %1
>
> }
>
> -------------
&...
2013 Mar 15
0
[LLVMdev] Simple question
...alue to
> the variable in llvm ir.
>
> The following returns 12, and %var2 = 12.
> ; ModuleID = 't.c'
> target datalayout =
> "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
> target triple = "x86_64-pc-linux-gnu"
>
> define i32 @test() nounwind readnone {
> %var1 = xor i32 0, 0
> %var2 = add i32 %var1, 12
> ret i32 %var2
> }
>
> Why can't I do?:
> ; ModuleID = 't.c'
> target datalayout =
> "e-p:...
2013 Mar 15
0
[LLVMdev] Simple question
...value to
> the variable in llvm ir.
>
> The following returns 12, and %var2 = 12.
> ; ModuleID = 't.c'
> target datalayout =
> "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
> target triple = "x86_64-pc-linux-gnu"
>
> define i32 @test() nounwind readnone {
> %var1 = xor i32 0, 0
> %var2 = add i32 %var1, 12
> ret i32 %var2
> }
>
> Why can't I do?:
> ; ModuleID = 't.c'
> target datalayout =
> "e-p...
2017 Oct 25
3
LLVM v6.0 Internalize and GlobalDCE PASS can not work together?
...edhat-linux
Thread model: posix
InstalledDir: /opt/llvm-svn/bin
$ /opt/llvm-svn/bin/clang -Xclang -disable-O0-optnone -S -emit-llvm
hello.c -o hello2.ll
$ cat hello2.ll
; ModuleID = 'hello.c'
source_filename = "hello.c"
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
@.str = private unnamed_addr constant [4 x i8] c"%d\0A\00", align 1
; Function Attrs: noinline nounwind uwtable
define void @foo() #0 {
entry:
ret void
}
; Function Attrs: noinline nounwind uwtable
define i32 @main(i32 %argc...
2013 Mar 16
3
[LLVMdev] Simple question
...e in llvm ir.
> >
> > The following returns 12, and %var2 = 12.
> > ; ModuleID = 't.c'
> > target datalayout =
> >
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
> > target triple = "x86_64-pc-linux-gnu"
> >
> > define i32 @test() nounwind readnone {
> > %var1 = xor i32 0, 0
> > %var2 = add i32 %var1, 12
> > ret i32 %var2
> > }
> >
> > Why can't I do?:
> > ; ModuleID = ...
2015 Feb 18
3
[LLVMdev] Calling into non-linked function via a pointer
I'm having a problem of being unable to call into an arbitrary function
that is loaded into memory whose pointer address is known to me but was not
linked into LLVM.
I have added the function and called LLVMAddGlobalMapping with the pointer,
and the program segfaults.
I was wondering if it is a supported scenario that LLVM can generate a call
into an arbitrary function that is not linked.
2017 Oct 26
2
LLVM v6.0 Internalize and GlobalDCE PASS can not work together?
...t;
>> $ /opt/llvm-svn/bin/clang -Xclang -disable-O0-optnone -S -emit-llvm
>> hello.c -o hello2.ll
>>
>> $ cat hello2.ll
>> ; ModuleID = 'hello.c'
>> source_filename = "hello.c"
>> target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
>> target triple = "x86_64-unknown-linux-gnu"
>>
>> @.str = private unnamed_addr constant [4 x i8] c"%d\0A\00", align 1
>>
>> ; Function Attrs: noinline nounwind uwtable
>> define void @foo() #0 {
>> entry:
>> ret void
>...
2018 Jul 28
2
ThinLTO Bug ?
...vm/build-debug/bin/opt -module-summary -o a.o a.ll
~/llvm/build-debug/bin/opt -module-summary -o b.o b.ll
~/llvm/build-debug/bin/llvm-lto2 run -o c a.o b.o -r a.o,c,px -r
b.o,a,px -r b.o,b,px -r a.o,gv -r b.o,gv
[~/thinltobug]$ cat a.ll
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
%struct.TA = type {}
@gv = dso_local global %struct.TA * zeroinitializer
define i32 @c() !dbg !6 {
bitcast %struct.TA ** @gv to i8*
unreachable
}
!llvm.module.flags = !{!0, !1}
!llvm.dbg.cu = !{!2}
!0 = !{i32 2, !"D...
2018 Jul 30
2
ThinLTO Bug ?
...t -module-summary -o b.o b.ll
> > ~/llvm/build-debug/bin/llvm-lto2 run -o c a.o b.o -r a.o,c,px -r
> > b.o,a,px -r b.o,b,px -r a.o,gv -r b.o,gv
> >
> >
> >
> > [~/thinltobug]$ cat a.ll
> >
> > target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
> >
> > target triple = "x86_64-unknown-linux-gnu"
> >
> > %struct.TA = type {}
> >
> >
> >
> > @gv = dso_local global %struct.TA * zeroinitializer
> >
> > define i32 @c() !dbg !6 {
> >
> > bitcast %struct.TA...
2017 Jun 02
10
[RFC][ThinLTO] llvm-dis ThinLTO summary dump format
Hey all,
Below is the proposed format for the dump of the ThinLTO module summary in
the llvm-dis utility:
> ../build/bin/llvm-dis t.o && cat t.o.ll
; ModuleID = '2.o'
source_filename = "2.ll"
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
@X = constant i32 42, section "foo", align 4
@a = weak alias i32, i32* @X
define void @afun() {
%1 = load i32, i32* @a
ret void
}
define void @testtest() {
tail call void @boop()
ret void
}
declare void @boop()
; Mod...
2016 Nov 09
10
Is the correct behavior of getelementptr i192* for opt + llc -march=aarch64?
Hi all,
opt and opt + llc generate the difference aarch64 asm code for the following LLVM code.
Is it intended behavior?
I expected (A) because I cast %p from i192* to i64*.
The information is dropped by opt and 8-byte padding is inserted or I write a bad code?
% cat a.ll
define void @store0_to_p4(i192* %p)
{
%p1 = bitcast i192* %p to i64*
%p2 = getelementptr i64, i64* %p1, i64 3
%p3 =
2016 Apr 05
3
What should IRObjectFile expose?
Hi Rafael,
There's a source file in Chromium that does something like this:
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
module asm ".text"
module asm "foo: ret"
declare void @foo()
define void @_start() {
call void @foo()
ret void
}
Currently the llvm-nm output for that looks like this:
---------------- T _start...
2016 Feb 19
3
target triple in 3.8
...LibraryInfoWrapperPass(llvm::TargetLibraryInfoImpl(targetMachine->getTargetTriple()))
);
still,
LV: The Widest register is: 32 bits.
so, unfortunately no change.
If I dump the Module, it starts with:
; ModuleID = 'module'
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
Does this datalayout look good for x86-64 AVX ?
Frank
On 02/19/2016 03:14 PM, Mehdi Amini wrote:
> Do you have the TTI in your pass manager?
>
> Something like:
>
> // Add the TTI (required to inform the vectorizer about register size for
> // instance)
>...
2020 May 27
4
default behavior or
...cat a.c
float foo(float a, float b)
{
return a+b;
}
$clang a.c -O2 -S -emit-llvm
emit ir like:
$cat a.ll
---------------------------------------
; ModuleID = 'a.c'
source_filename = "a.c"
target datalayout =
"e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
; Function Attrs: norecurse nounwind readnone uwtable
define dso_local float @foo(float %a, float %b) local_unnamed_addr #0 {
entry:
%add = fadd float %a, %b
ret float %add
}
attributes #0 = { norecurse nounwind readnone uwtable
"...
2012 Feb 02
0
[LLVMdev] Why extra 4 bytes on stack ???
...implest "int main() { return 0; }" program
allocates those four bytes:
; ModuleID = '/tmp/webcompile/_29079_0.bc'
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define i32 @main() nounwind uwtable {
%1 = alloca i32, align 4
store i32 0, i32* %1
ret i32 0
}
2014 Sep 18
2
[LLVMdev] [Vectorization] Mis match in code generated
...ere we calculate scalar loop
cost as 4 and vector loop cost as 2.
Since vector loop cost is less and above reduction is legal to vectorize,
loop vectorizer produces vectorized code :
*IR without vectorization:*
*target datalayout = "e-m:e-p:32:32-f64:32:64-f80:32-n8:16:32-S128"target
triple = "x86_64-pc-linux-gnu"; Function Attrs: nounwind readonlydefine i32
@foo(i32* nocapture readonly %a, i32 %n) #0 {entry: br label
%for.bodyfor.body: ; preds =
%for.body, %entry %i.05 = phi i32 [ 0, %entry ], [ %inc, %for.body ]...
2016 Sep 14
4
setDataLayout segfault
...->createDataLayout().getStringRepresentation() ); // this
segfaults
Mod.get()->setDataLayout( targetMachine->createDataLayout() ); // as
well as this
}
Backtrace:
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
e-m:e-i64:64-f80:128-n8:16:32:64-S128
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5f65832 in llvm::SmallVectorTemplateCommon<unsigned char,
void>::end (this=0x148) at
/home/fwinter/svn/llvm-3.9/include/llvm/ADT/SmallVector.h:117
117 iterator end() { return (iterator)this->EndX; }
(gdb) bt
#0 0x0000...
2013 Jun 17
2
[LLVMdev] Failure handling half type
Hi,
if I write the following simple program:
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define void @foo () {
%1 = alloca half
store half 0xH42CC, half* %1 ; 0xH42CC = 3.4
%2 = load half* %1
ret void
}
llc goes in SIGABRT. In the reference manual says that it's correct syntax.
It's a bug?
Thanks....