Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Intr*Mem flags meaning"
2012 Nov 12
2
[LLVMdev] Incorrect values of GCC/LLC, GCC/LLC-BETA and LLC/LLC-BETA columns in the report.html
Hi,
I run LLVM test suite using the following command and get
report.nightly.html successfully.
% make report.html TEST=nightly
But GCC/LLC, GCC/LLC-BETA and LLC/LLC-BETA columns look strange. Here
is for example snippet of "clamscan" test result:
[[
Program MultiSource/Applications/ClamAV/clamscan
GCC 0.2360
LLC 0.2360
2012 Nov 14
0
[LLVMdev] Incorrect values of GCC/LLC, GCC/LLC-BETA and LLC/LLC-BETA columns in the report.html
On Mon, Nov 12, 2012 at 11:15 PM, Simon Atanasyan <satanasyan at mips.com> wrote:
> I run LLVM test suite using the following command and get
> report.nightly.html successfully.
>
> % make report.html TEST=nightly
>
> But GCC/LLC, GCC/LLC-BETA and LLC/LLC-BETA columns look strange. Here
> is for example snippet of "clamscan" test result:
> [[
> Program
2011 Oct 24
0
[LLVMdev] Extending Intrinsic Functions
Hi all,
A question about Intrinsic functions and their properties. I am trying
some extensions with Intrinsic functions. The intrinsic function takes a
pointer as argument and transforms the pointer into another one and
returns it. It does not read or write memory. The Intrinsic has
properties: IntrNoMem. Is there any other property I can specify for the
intrinsic function such as
2016 Mar 24
4
attribute of intrinsic function
Hi,
When I define an intrinsic function with memory write permission, my
assumption is that we can either attach [IntrReadWriteArgMem] or [] to the
intrinsic function. Based on the comment of the source code ,
"IntrReadWriteArgMem - This intrinsic reads and writes only from memory
that one of its arguments points to, but may access an unspecified amount."
"If no property is set,
2016 Mar 24
0
attribute of intrinsic function
On 03/24/2016 12:45 PM, Xiangyang Guo via llvm-dev wrote:
> Hi,
>
> When I define an intrinsic function with memory write permission, my
> assumption is that we can either attach [IntrReadWriteArgMem] or [] to
> the intrinsic function. Based on the comment of the source code ,
> "IntrReadWriteArgMem - This intrinsic reads and writes only from
> memory that one of its
2016 Mar 24
0
attribute of intrinsic function
> On Mar 24, 2016, at 12:45 PM, Xiangyang Guo via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi,
>
> When I define an intrinsic function with memory write permission, my assumption is that we can either attach [IntrReadWriteArgMem] or [] to the intrinsic function. Based on the comment of the source code , "IntrReadWriteArgMem - This intrinsic reads and writes
2016 Mar 25
1
attribute of intrinsic function
Thanks for your reply, Philip.
You are right, when I use LLVM-3.8, the 'argmemonly' shows up. Previously,
I use LLVM-3.7.
I think idempotent is what I want. Can you tell me how to add idempotent
attribute to the function? Thanks.
Regards,
Xiangyang
2016-03-24 14:30 GMT-07:00 Philip Reames <listmail at philipreames.com>:
>
>
> On 03/24/2016 12:45 PM, Xiangyang Guo via
2009 Mar 24
2
[LLVMdev] Reducing .td redundancy
On Tuesday 24 March 2009 10:43, Chris Lattner wrote:
> On Mar 23, 2009, at 5:56 PM, David Greene wrote:
> > Is it legal to do something like a !strconcat on a non-string
> > entity? That
> > is, is there some operation that will let me do this (replace
> > SOME_CONCAT with
> > an appropriate operator):
>
> I don't get it, can you try a simpler example on
2019 Jul 24
2
Intrinsics InstrReadMem memory properties
Hi Johannes,
Thanks for your reply. I now see more clearly how things work with these
properties. However, what would be an object whose address is potentially
known by a callee? I suppose the intrinsic arguments and global variable?
So IIUC, if not restricted by *only properties, an intrinsic could access
to:
- only its arguments if IntrArgMemOnly specified,
- its arguments and the global
2009 Mar 24
0
[LLVMdev] Reducing .td redundancy
On Mar 23, 2009, at 5:56 PM, David Greene wrote:
> Is it legal to do something like a !strconcat on a non-string
> entity? That
> is, is there some operation that will let me do this (replace
> SOME_CONCAT with
> an appropriate operator):
I don't get it, can you try a simpler example on me? :)
-Chris
>
>
> (WARNING! Hacked-up tablegen ahead!)
>
>
2014 Jul 18
2
[LLVMdev] how to define INTRINSIC_W_CHAIN
sure!
class TEST_INTINSIC_FM< string asmstr> : Intrinsic
<llvm_i32_ty], [llvm_i32_ty, llvm_ptr_ty],
[IntrReadWriteArgMem],
!strconcat(“llvm.test”, asmstr),”.float”)
>;
tks
On Jul 18, 2014, at 4:06 PM, Tom Stellard <tom at stellard.net> wrote:
> On Fri, Jul 18, 2014 at 03:19:47PM -0400, kewuzhang wrote:
>> en!
>>
>> my test is : %r1 =
2014 Jul 23
2
[LLVMdev] LowerINTRINSIC_W_CHAIN in X86
Yeah.
I agree that "Chain operand is needed if the intrinsic is reading / writing memory.”,
Just don’t know where and how to set it up.
like intrinsic “int_x86_xtest:
“
def int_x86_xtest : GCCBuiltin<"__builtin_ia32_xtest">,
Intrinsic<[llvm_i32_ty], [], []>;
“
"def X86xtest: SDNode<"X86ISD::XTEST", SDTypeProfile<1, 0,
2015 Sep 08
2
Strange types on x86 vcvtph2ps and vcvtps2ph intrinsics
Hi,
I was looking at the x86 vector intrinsics for converting half
precision floating point numbers and I'm a bit confused as to why
certain types were chosen. I've gone ahead and used their current
definition with success but I'd like to understand why the types used
with these intrinsics are done this way.
For reference see ``include/llvm/IR/IntrinsicsX86.td``. Here are the
2009 Mar 24
2
[LLVMdev] Reducing .td redundancy
Is it legal to do something like a !strconcat on a non-string entity? That
is, is there some operation that will let me do this (replace SOME_CONCAT with
an appropriate operator):
(WARNING! Hacked-up tablegen ahead!)
multiclass sse_fp_binop_bitwise_rm<bits<8> opc, string OpcodeStr,
SDNode OpNode> {
// Vector operation emulating scalar (fp)
2014 Jul 18
3
[LLVMdev] how to define INTRINSIC_W_CHAIN
Hi guys,
I am working on an intrinsic function, which will write to a pointer argument.
So I am lowering it and think I need to catch it in lowerINTRINSIC_W_CHAIN, but somehow it always fall into INTRINSIC_WO_CHAIN category.
I put [IntrReadwriteArgMem] into my Intrinsic class definition, it did not help.
tried put [SDNPHasChain] into intrinsic class definition, cause errors” Element type
2019 Jul 24
2
Intrinsics InstrReadMem memory properties
Ok, now I think I've found a bug:
Consider this C code:
void bar(int b) {
int a[10];
memset(a, b, 10);
}
which generates this IR code:
define dso_local void @bar(i32 %b) #0 {
entry:
%b.addr = alloca i32, align 4
%a = alloca [10 x i32], align 16
store i32 %b, i32* %b.addr, align 4
%arraydecay = getelementptr inbounds [10 x i32], [10 x i32]* %a, i64 0,
i64 0
%0 = bitcast i32*
2014 Jul 18
2
[LLVMdev] how to define INTRINSIC_W_CHAIN
Tks Tom,
That is my confusing part. How can I make it to "access memory” so it will HasChain?
Is there any flag set like in typeProfile, Node, instructions? myLoad, mayStore, SDNPHasChain?
-kevin
On Jul 18, 2014, at 4:26 PM, Tom Stellard <tom at stellard.net> wrote:
> On Fri, Jul 18, 2014 at 04:15:45PM -0400, kewuzhang wrote:
>> sure!
>>
>> class
2015 Jun 19
2
[LLVMdev] Attribute to mark that function only access memory through it's arguments
On 06/18/2015 09:15 PM, Nick Lewycky wrote:
>
> Currently in AliasAnalysis we can model ModRef behaviour for
> functions which
> only access memory through their pointer arguments. However we can't
> express this propery as a function attribute.
>
> For example, for intrinsics we can specify ReadWriteArgMem or
> ReadArgMem
> attributes in
2014 Jul 18
2
[LLVMdev] how to define INTRINSIC_W_CHAIN
en!
my test is : %r1 = call<float> @test.adddiv( <float> %r0, <float>* %p0).
since
>> but somehow it always fall into INTRINSIC_WO_CHAIN category.
(caught it in lowering..)
I think it doesn’t have chain in initial DAG.
unfortunately the intrinsic “test.adddiv” is defined by me for now. not sure how to make it has a chain.
kevin
On Jul 18, 2014, at 3:06 PM,
2018 Feb 01
1
Intrinsic pattern matching
Hello,
I have a problem with pattern matching on intrinsics.
I have following code in IntrinsicsX86.td:
```
let TargetPrefix = "x86" in { // All intrinsics start with "llvm.x86.".
def int_x86_mpx_bndmk:
Intrinsic<[llvm_x86bnd_ty], [llvm_ptr_ty, llvm_i64_ty], []>;
}
```
And following instruction that is generated when @llvm.x86.mpx.bndmk is
used in code: