similar to: [LLVMdev] Non-deterministic behavior when using LoopInfo pass in LLVM

Nick, Is there a clean way to tell the difference between dst and src operands in operations without assignment "=" (ie, store)? On Mon, Oct 24, 2011 at 9:52 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > Nick, > > I forgot to thank you, thanks! > > > On Sat, Oct 22, 2011 at 2:25 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > >> Ryan

Ryan Taylor wrote: > Nick, > > Unfortunately this doesn't answer my question I don't think. It > seems that -instnamer, as you mention, names the instructions but still > does not name the local variables. What other local variables are you referring to? When AsmWriter prints "%y = add i32 %x, 1", the name of that add instruction is "y" and

Nick, Unfortunately this doesn't answer my question I don't think. It seems that -instnamer, as you mention, names the instructions but still does not name the local variables. So there really is no way to do this shy of creating (or basically copying) the API from AsmWriter (seems very dedundant to me)? This seems like a large failing? On Fri, Oct 21, 2011 at 7:03 PM, Nick

On Nov 13, 2009, at 7:27 AM, Jay Foad wrote: > Hi, > > I've been upgrading some custom LLVM passes to work with LLVM 2.6 > instead of LLVM 2.5. I've noticed that in 2.6, some functions seem to > have several local values with no name (where getName() returns an > empty string). I never saw this in 2.5. Is this a known change in > behaviour? Is there some handy way to

Ryan Taylor wrote: > It looks like the AsmWriter is generating the local variables (SlotNum)s > on the fly in that file (AsmWriter.cpp), so is there any way at all to > get this information from the operation itself, via Instruction, Value > or Type? Nope! As you noticed, they're created on the fly... ...when the Value or Type is anonymous. If you want them to be persistent,

Hi Bill, With the latest llvm version I'm getting the following error: opt -instnamer < core-device.c.bc > core-device.o.bc Attribute 'nobuiltin' only applies to functions! void (%struct.fw_csr_iterator*, i32*)* @fw_csr_iterator_init Broken module found, compilation aborted! 0 opt 0x0000000001914bf1 llvm::sys::PrintStackTrace(_IO_FILE*) + 38 1 opt

On 2/25/11 1:50 PM, Kodakara, Sreekumar V wrote: > I have developed a pass to instrument LLVM bit code files with calls to a custom instrumentation library. For one of the instrumentation calls, I need to pass the name of the temporary variable used in LLVM bit code. > > For example, if I see LLVM assembly code as shown below, > > %13 = icmp eq i64 %11, 0, !dbg !14 > > After

Hi, > Can anyone tell how to get the result name or instruction name of all > instruction? For example if the instruction is "x=add y,z", here i need "x". > Using getName(), i am getting some instructions result name, but llvm > produces some instruction like "%0=add i32 tmp, 1", here getName() shows > empty string as result name. > So please help.

Ryan Taylor wrote: > Nick, > > Ah, forgot the -o, thanks, silly mistake. > > So how would you extract "add" from the instruction "%A"? I->getOpcodeName(). > Yes, this is sort of what I am trying to do. The instnamer works fine > for the local variables and I already had the constants sorted out. Great! Nick > > On Sat, Oct 22, 2011 at

Ryan Taylor wrote: > Nick, > > Also, I forgot to mention I had no luck with instnamer, it still left > the local variables as "%slotNum", it didn't name them, unless I used > -instnamer wrong: > > opt -instnamer <file.bc> file2.bc Almost, use -o to specify output: opt -instnamer file.bc -o file2.bc > Those are the ones I am refering to. The

[please remember to cc llvmdev] On 24 October 2011 13:20, Ryan Taylor <ryta1203 at gmail.com> wrote: > Nick, > > Thanks, this is not really viable as I'd have to check every single > instruction like this, seems like there is a lot of overhead associated with > this solution. I don't know what problem you're solving? Nick On Mon, Oct 24, 2011 at 11:48 AM,

On 24 October 2011 15:50, Ryan Taylor <ryta1203 at gmail.com> wrote: > Nick, > > Oh, sorry. So there are lots of "void" operations, I basically just want > to print out the operation name, it's dest operands and source operands, What's a dest operand? The term "operand" in LLVM always refers to the inputs (ie., an add has two operands). >

How does the verifier deal with this? I'm noticing that if I load a clang compiled function (with -emit-llvm) and run the verifier, there is no problem. If I start mucking with the function body (adding an instruction), the verifier is unhappy saying the instructions that would have been in the commented out block aren't part of a basic block. Does the clang compiled function have some

In LLVM 1.5, the function isLoopHeader fails to check for a null pointer after calling getLoopFor. Dunno if this is fixed in CVS, but attaching a patch anyway ... Sameer. -- Research Scholar, KReSIT, IIT Bombay http://www.it.iitb.ac.in/~sameerds/ -------------- next part -------------- --- LoopInfo.h 2005-06-29 17:42:43.000000000 +0530 +++ llvm/include/llvm/Analysis/LoopInfo.h 2005-06-29

Dear llvmers, I decided to write my own scripts to compile the SPEC programs, and they work fine, except with 403.gcc. Basically, I take the file 403.gcc.linked.rbc from the ...\Output folder that the LLVM test suite produces. Then I use this linked.rbc file to generate an executable file via the following commands: llc 403.gcc.linked.rbc -o 403.gcc.linked.s clang 403.gcc.linked.s -o

Hello, I have a question regrading the analysis pass that generates loop info from an .ll code. My previous understanding was there will be just one loop header(in the loop info) for a particular loop. But, when i use isLoopHeader() member function from the loop info class I get 'true' return value for two different basic blocks. Note both basic blocks are loop conditional block(break

Solaris-x86-10u8 Dovecot-1.2.7 Large mail setup, with quite a few MX servers working well. Generally everything is super. But every now and then, we get "bouts of bad weather" - which only lasts a short time, and curiously nearly always occur when mail is sent to customer mailing lists. I suspect mostly because of that 1 message has multiple recipients within the same domain.

Dear puppetteers, I am having a philosophical question about parametrized classes. When building modules, one wants to be as flexible as possible, to try to target as many puppet flavors as possible. This is our target: - Foreman users, using foreman as an ENC with smart variables (or potentially any other ENC, but I would say this is the most widespread one). - Pure Puppet''s site.pp

All- I''m using puppet 2.7.14. I''ve reviewed http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html but it doesn''t seem to cover what I''m attempting. Consider a module layout like this: $ tree mymodule mymodule |-- Modulefile |-- README |-- manifests | |-- init.pp | |-- special_type | | `-- prereqs.pp | `-- special_type.pp

Hello LLVMers, I'm putting together some (extensive) experiments with using a genetic algorithm to construct sets of optimization passes that are as close as optimal in a number of ways, e.g. compilation time, execution time, code size, ... I've figured out which LLVM tools I should use for this (llvm-gcc to obtain bitcode, opt to optimize, llc to obtain assembly, ...), and I'm now