similar to: [LLVMdev] Integer ID for LLVM::Instruction*?

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Integer ID for LLVM::Instruction*?"

2015 May 07
2
[LLVMdev] Integer ID for LLVM::Instruction*?
David, As you suggested, I try to compile the following test code: *include "llvm/IR/Instruction.h"#include "stdint.h"extern void callback(intptr_t);void foo(){ llvm::Instruction* i; intptr_t zzzz=static_cast<intptr_t>(i); callback(zzzz);}* but got this compilation error: * 'intptr_t' (aka 'long') is not allowed intptr_t
2015 Jul 24
2
[LLVMdev] Transforming SwitchInst to BranchInst
Hi, Are there some built-in LLVM transformation pass, or written library code that transforms LLVM::SwitchInst into if-condition statements (LLVM:: BranchInst)? The purpose of the transformation is that we have a legacy program analyzer that includes an LLVM pass manipulating if-condition statements. Statements of LLVM::SwithchInst should have been handled in the same manner but was not done.
2015 Apr 19
2
[LLVMdev] LLVM IR for inline functions
Hi, I have a naive question on how to generate LLVM IR for inline functions. I have compiled this C code: *inline void func1()* * {* * int x=3;* * }* * void func2()* * {* * func1();* * int y = 4;* * }* into LLVM IR, using clang -emit-llvm -S -c <filename> But the generated LLVM IR file does *not* have func1() expanded (see below for the relevant parts). *; Function Attrs: nounwind
2015 Jun 07
2
[LLVMdev] Loop Unfolding in LLVM
Hello, I am looking for a loop unfolding procedure implemented in LLVM that helps to transform a while-loop to n-layer If-statements. The transformation should be on IR, although the example below is illustrated on the source level. original loop: * WHILE (condition) DO action ENDWHILE* Expected unfolded loop (2-layer): * IF (condition) THEN* * action* * IF
2016 Aug 13
2
A "hello world" coverage sanitizer
Thank you, kcc. I am unsure if I misunderstand your reply. It seems that trace-bb, rather than trace-pc, fits better for my problem, given that my instrumentation is to put before each conditional statement. Do I misunderstand something here? " Tracing basic blocks <http://clang.llvm.org/docs/SanitizerCoverage.html#id11> With -fsanitize-coverage=trace-bb the compiler will insert
2015 Apr 09
3
[LLVMdev] BasicBlock.h in the binary and in the source differ
Hi, I am using LLVM to develop a tool, using Mac OS 10.9. I have download llvm source and binary from http://llvm.org/releases/download.html I just find the BasicBlock.h file of the binary package clang+llvm-3.6.0-x86_64-apple-darwin/include/llvm/IR/BasicBlock.h is slightly different from that of the source llvm/include/llvm/IR/BasicBlock.h In particular, llvm:: getModule(..)
2018 Apr 05
1
llvm::PointerIntPair -- is this by design or a bug?
I do agree that sign-extension is the right thing to do. Unlike bit-fields, llvm::PointerIntPair has asserts checking that the int value is within range. So if you assign an out of range value, it should fail with an assertion: llvm::PointerIntPair<SomeType*, 3, int> pip; pip.setInt(7); // can be made to fail as the valid range // of signed 3-bit values is [-4:3] The above
2015 Apr 09
2
[LLVMdev] BasicBlock.h in the binary and in the source differ
The source is cloned from https://github.com/llvm-mirror/llvm Thanks. Zhoulai On Thu, Apr 9, 2015 at 9:15 AM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > On 4/9/15 9:58 AM, Zhoulai wrote: > >> Hi, I am using LLVM to develop a tool, using Mac OS 10.9. I have >> download llvm source and binary from >> >>
2016 Aug 12
2
A "hello world" coverage sanitizer
Hi, all I want to instrument a program automatically so that it prints "hello" before each conditional statement. For example, consider the function P below. int P(int x) { if (x<3) if (x>0) return 1; return 0; } Let P_instrum be the instrumented version of P. It is expected that: -- P_instrum(1) prints two "hello"s --
2009 Apr 08
1
[LLVMdev] new warnings
On Tue, Apr 7, 2009 at 8:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Mike Stump wrote: >> On Apr 7, 2009, at 6:02 PM, Tanya M. Lattner wrote: >>> Can you please just respond to the specific patch on llvm-commits >>> instead >>> of emailing llvm-dev? >> >> Don't happen to know which checkin caused it... > > Given that there's
2009 Aug 11
1
reading heterogeneous CSV
Greetings, all. I've got a datafile I've been working with that has an ideosyncratic, heterogeneous format. It's grossly like: [...] DISKREAD,metadata about disks MEM,metadata about memory ZZZZ,observation-identifier,time,date DISKREAD,observation-identifier,data about disks MEM,observation-identifier,data about memory [ and repeat for each observation ] What I've done in
2005 Jul 27
3
[LLVMdev] How to define complicated instruction in TableGen (Direct3D shader instruction)
Each register is a 4-component (namely, r, g, b, a) vector register. They are actually defined as llvm packed [4xfloat]. The instruction: add_sat r0.a, r1_bias.xxyy, r3_x2.zzzz Explaination: '.a' is a writemask. only the specified component will be update '.xxyy' and '.zzzz' are swizzle masks, specify the component permutation, simliar to the Intel SSE permutation
2005 Jul 29
0
[LLVMdev] How to define complicated instruction in TableGen (Direct3D shader instruction)
Actually the problems that Tzu-Chien Chiu are encountering are similar to what should be done for generating SSE code in the X86 backend and also other SIMD instruction sets. I think LLVM neeeds to add instructions for permuting components, extracting and injecting elements in packed types. If the architecture has instructions which can do permutations for each instruction (for example
2013 Aug 31
23
ERROR: Log level INFO requires LOG Target in your kernel and iptables
Hi, I have 2 Debian testing boxes running a very similar setup (both running the latest aptosid kernel); on one of them, since the iptables/libxtables10 packages have been upgraded from 1.4.19.1-1 to 1.4.20-2, shorewall-init can''t start shorewall anymore and for this reason ifupdown also fails triggering firewall up. Shorewall can be successfully started later on, and ifupdown starts
2003 Feb 08
3
Bug moving file over link?
Can someone explain to me what is happening here: ~ $ touch foo ~ $ ln foo bar ~ $ ls foo bar bar foo ~ $ mv foo bar ~ $ ls foo bar bar foo I try to move a file over a hard linked copy of itself and the move fails, but there is no error. Is this the intended behavior? -- Ben Escoto
2015 May 02
5
[LLVMdev] Modifying LoopUnrollingPass
Hi Zhoulai, I am trying to modify "LoopUnrollPass" in llvm which produces multiple copies of loop equal to the loop unroll factor.Currently, using multicore architecture, say 3 for example and the execution goes like: for 3 cores if there are 9 iterations of loop core instruction 1 0,3,6 2 1,4,7 3 2,5,8 But I want to to
2007 Feb 23
11
Problems getting mongrel service working
Hello list! I have mongrel service 0.1.0 working on my current production machine. Upgrading to a new server and also moving to mongrel service 0.3.1 has not worked yet. I am hoping someone will have an idea as to why. I have mongrel installed properly (I think): C:\rails\igacc>gem list --local *** LOCAL GEMS *** ... mongrel (1.0.1) A small fast HTTP library and server that runs
2007 Jul 16
1
Dict-server mysql module error
hi all when i setup plugin quota by quota = dict: mysql:/etc/quota-dict.conf i get the folowing error: deliver(zzzz at zzzz.zz): Unknown dict module: mysql deliver(zzzz at zzz.zz): dict quota: dict_init() failed quota-dict.conf: connect = host=localhost dbname=zzzz user=zzzz password=zzzz table = mailbox select_field = quota where_field = maildir username_field = username dovecot.conf: #
2005 Nov 08
3
Agent Call Recording
When recording inbound agent calls, if the queues use agent members (Agent/6000), we can get the calls recorded as agent-xxxx.yyyy.zzzz.gsm where xxxx is the agent number. However, if the queues use phone members (SIP/6000), the recorded filename is simply yyyy.zzzz.gsm. Is there any way of making the recorded file either agent-xxxx or even sip-xxxx where xxxx is the extension number. I had
1998 Jan 13
1
R-beta: 0.61.1 "if else" parse bug?
I was playing with porting "Hmisc" S-Lib. I am getting parse errors for: if (xxx) yyyy;else zzzz I have to break this into: if(xxx) yyyy else zzzz Is this a known feature? TIA Osman -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or