Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Implementing customized intrinsic"
2009 Jan 22
2
[LLVMdev] Implementing customized intrinsic
Thanks for your reply. Probably I did not explain clearly. Here is an
example:
call @check(%foo)
%1 = load %foo
Now I want to write optimization only focus on the function call
@check, and it might have some additional information which does not
need to appear at LLVM IR.
So it seems that the annotation intrinsic does not fit the scenario.
Haohui
On Jan 21, 2009, at 8:01 PM, Tanya M.
2009 Jan 22
0
[LLVMdev] Implementing customized intrinsic
Does the llvm annotation intrinsic not work for what you are trying to do?
http://llvm.org/docs/LangRef.html#int_var_annotation
http://llvm.org/docs/LangRef.html#int_annotation
-Tanya
On Wed, 21 Jan 2009, Haohui Mai wrote:
> Dear all,
>
> Currently I'm working on a project that add various checks into the
> LLVM bitcode. For example, I insert function calls before every
>
2009 Mar 06
3
[LLVMdev] Inserting annotations
Hello together,
how can i insert annotations in IR ?
I want actually write something like:
CallInst *call = CallInst::Create( ??? , aBasicBlock);
in my pass.
Regards
Raad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090305/cd1db761/attachment.html>
2008 Oct 02
0
[LLVMdev] Compliation broken
Hi all,
The current repository (revision 56968.) does not compile on my Linux
box (with GCC 3.4.6):
X86TargetAsmInfo.cpp:41: error: duplicate explicit instantiation of
`bool
llvm::X86TargetAsmInfo<BaseTAI>::ExpandInlineAsm(llvm::CallInst*)
const [with BaseTAI = llvm::TargetAsmInfo]'
X86TargetAsmInfo.cpp:43: error: duplicate explicit instantiation of
`bool
2006 Apr 13
0
[LLVMdev] Re: Creating Release 1.7 Branch at 1:00pm PDT
The various intrinsic assert/crashes should all be fixed on mainline CVS
(they are PR733, which I just fixed).
The only ones that I'm wary of are:
XPASS: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-20-
StaticRedeclare.c.tr
FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2005-12-04-
DeclarationLineNumbers.c:
In the former case, I would guess that the test isn't
2014 Jan 09
2
[LLVMdev] reference to non-static member function must be called
I'm using LLVM 3.3 Release. From the Class Reference Page. CallInst has a
member function :
static CallInst * Create (Value *Func, ArrayRef< Value * > Args, const
Twine &NameStr="", Instruction *InsertBefore=0)
This is what I want to use! the default name is "" and I also use that .
Thanks!
-----
Kind Regards!
-JinHuang
--
View this message in context:
2006 Apr 13
2
[LLVMdev] Re: Creating Release 1.7 Branch at 1:00pm PDT
I just updated again (both llvm and llvm-gcc). The only thing that
changed was:
P test/Regression/CFrontend/2005-12-04-DeclarationLineNumbers.c
The regression test below was done *with* your llvm-gcc changes to llvm-
expand.c. I don't know what the failures are all about, but I will try
it again. If its the same, I'll let you know.
Reid.
On Thu, 2006-04-13 at 16:20 -0500, Chris Lattner
2006 Apr 13
3
[LLVMdev] Re: Creating Release 1.7 Branch at 1:00pm PDT
Here's what's left on Linux (GCC 4.1.0), after all updates that went
into the branch:
Running /proj/llvm/build/../llvm/test/Regression/CFrontend/dg.exp ...
FAIL: /proj/llvm/build/../llvm/test/Regression/CFrontend/2004-02-12-
LargeAggregateCopy.c.tr:
gccas: /proj/llvm/build/../llvm/lib/VMCore/Function.cpp:266: unsigned
int llvm::Function::getIntrinsicID() const: Assertion `0 &&
2009 Mar 06
0
[LLVMdev] Inserting annotations
Hi,
As far as I know, Instruction class does not inherit "Annotable" Class. Only
Function inherits annotable according to the documentation of annotable
class.
What you are asking would require adding annotations at instruction level,
which does not seem to be possible. You can maintain external maps between
instructions and your annotations,
--Kapil
On Thu, Mar 5, 2009 at 7:17 PM,
2009 Apr 14
3
[LLVMdev] InstVisitor Example
On Apr 14, 2009, at 1:49 PM, Luke Dalessandro wrote:
>
> On Apr 14, 2009, at 12:48 PM, Brice Lin wrote:
>
>> I just read the LLVM Programmer's Manual, which mentions (but
>> specifically does not include any details of) the InstVisitor
>> template. Could someone please provide an example of how to use this
>> template to find (as an example) all CallSites for
2014 Jul 07
4
[LLVMdev] Splitting basic block results in unknown instruction type assertion
Hello,
I would like to see if this issue is a result of a misunderstanding on
my part before I file a bug. I am using LLVM 3.4, built from the
source tarballs. My system's uname is "Darwin tyler-air 12.5.0 Darwin
Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013;
root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64".
All I'm trying to do is add a runtime check after all call
2009 Apr 14
0
[LLVMdev] InstVisitor Example
On Apr 14, 2009, at 12:48 PM, Brice Lin wrote:
> I just read the LLVM Programmer's Manual, which mentions (but
> specifically does not include any details of) the InstVisitor
> template. Could someone please provide an example of how to use this
> template to find (as an example) all CallSites for the function
> strcpy?
If this is really what you want to do, then the easiest
2009 Apr 14
0
[LLVMdev] InstVisitor Example
Thanks for providing me with those examples. My rather inefficient
pass, which inherits from ModulePass, currently iterates through the
Module, Functions, and BasicBlocks multiple times (once to find
strcpy, another to find strcat, and so on for various other
functions). If I only care about the direct calls, would I benefit
more from switching to multiple use_iterators or the InstVisitor
2006 Apr 13
0
[LLVMdev] Re: Creating Release 1.7 Branch at 1:00pm PDT
Branches have been created. You are free to checkin to cvs head again.
I'll send mail once I have the prerelease tar balls up. Please continue to
review and revise the documentation. I can fold this into the release
later.
Thanks,
Tanya
On Thu, 13 Apr 2006, Tanya Lattner wrote:
>
> I will be creating the release branch at 1:00pm PDT. Please refrain from
> checking in from
2006 Apr 13
3
[LLVMdev] Creating Release 1.7 Branch at 1:00pm PDT
I will be creating the release branch at 1:00pm PDT. Please refrain from
checking in from 1:00-1:30pm. I will send email once I am done.
Thanks,
Tanya
2008 Oct 02
6
[LLVMdev] Making Sense of ISel DAG Output
On Thursday 02 October 2008 12:42, David Greene wrote:
> But let's say you _could_ write such a pattern (because I can). The input
> DAG looks like this:
>
> 0x391a220: <multiple use>
> 0x391c970: v2f64 = scalar_to_vector 0x391a220 srcLineNum= 10
> 0x391ac10: <multiple use>
> 0x391c8b0: v2f64 = scalar_to_vector
2009 Apr 14
2
[LLVMdev] InstVisitor Example
I just read the LLVM Programmer's Manual, which mentions (but
specifically does not include any details of) the InstVisitor
template. Could someone please provide an example of how to use this
template to find (as an example) all CallSites for the function
strcpy?
Thanks,
Brice Lin
2009 Jun 12
2
[LLVMdev] Proposal for pluggable intrinsics
Hi all,
Greetings. I'm a Ph.D. student in UIUC. Now I'm working on SAFECode, a
research compiler based on LLVM which insert necessary runtime checks
to guarantee memory-safety of programs. SAFECode needs to insert checks
into the programs (say, please check this load instruction for me).
Currently SAFECode inserts these checks as normal call instructions. It
would be great that LLVM can
2011 Jan 19
0
[LLVMdev] How to get the name and argument of a function
Thanks a lot!
I finally fix my problem.
My code is like this:
//CallInst* pCall pCall is a printf called in my situation
if( ConstantExpr * pCE = dyn_cast<ConstantExpr>( pCall->getArgOperand(0))){
if( GlobalVariable * pGV = dyn_cast<GlobalVariable>( pCE->getOperand(0))){
if( ConstantArray * pCA = dyn_cast<ConstantArray>(
2014 May 13
4
[LLVMdev] Problems in instrumentation
Hi everyone,
I have some trouble in instrumenting load instructions. I want to
instrument load instructions as follow: Firstly, I judge whether the loaded
pointer(*any type is possible*) is NULL. If so, I want to explicitly
allocate the corresponding address space of its type to the pointer.
For example, in source code level I want to translate the next statement
*p = 1;
into the next