similar to: Replacing operands in a call instruction

Hello, I am trying to reset the operands of instructions. What I am doing is, I am finding all Uses of a specific operand in an Instruction and resetting it with a new value using "setOperands(int, Value*)". I am doing as: for (auto vmitr=vm.begin(), vsitr=vs.begin(); vmitr!=vm.end() && vsitr!=vs.end(); vmitr++, vsitr++){ // I have two *Value ( operands) for ( auto myitr

Does it mean we can not dereference the Value variables? Value *val = some operand of an instruction; Value *val2= some operand of another instruction; I am trying to rewire the operand values of an instruction using: *val = *val2; It seems that this is not allowed. Thanks, -- Abid M. Malik ****************************************************** "I have learned silence from the

Hello, I am loop over the arguments of a call instruction : ----> for (Value *arg: c->args()){ errs() << *arg << "\n"; arg->print(llvm::errs(), false); errs()<<"\n"; } -----> How can I convert the arg for binary comparison(== etc.)? If I am correct, it is not a string. If the argument is "i32 1",

Dear All; Is there any work that discusses ​LLVM framework's short comings regarding auto vectorization and polyhedral optimizations? Regards, > -- Abid M. Malik ****************************************************** "I have learned silence from the talkative, toleration from the intolerant, and kindness from the unkind"---Gibran "Success is not for the chosen few, but

Hi: Does Clang support CUDA? I am looking for a front end for my compiler that can take CUDA programming framework. Thanks, -- *Abid ****************************************************** "I have learned silence from the talkative, toleration from the intolerant, and kindness from the unkind"---Gibran "Success is not for the chosen few, but for the few who choose" --- John

Hello, What intrinsics "@llvm.lifetime.start/@llvm.lifetime.end" really do? As per my knowledge, they define the live ranges of variables. In the following code section, they seem redundant. However, when I remove them, the behavior of the code becomes non-deterministic. The live ranges of the variables defined by them are never used in the code. Thanks, --------------- %37 = bitcast

Hi, Does anyone know how to implement the feature in asterisk calling card when a user has dialed the access number and during the IVR or any time during the call, he can press ## or ** to end the current call and dial a new destination number? Please help and give me a step by step help. Thanks. Rgrds-------------Abid -------------- next part -------------- An HTML attachment was

Hi All, I am new to this community and just subscribed. We have Asterisk running in production but I could not find out in documentation as well as web that how many maximum number of registrations an Asterisk Server can support. We have it on a 1.4 GHz Processor, 2 GB RAM and 40 GB HDD IBM Server. Please suggest urgently. Thanks. Best Regards, ------------------------------------- Abid

Going to keep this RFC short and to the point: TerminatorInst doesn't pull its weight in the type system. There is essentially a single relevant API -- iterating successors. There is no other interesting aspect shared -- the interface itself just dispatches to specific instructions to be implemented. On the flip side, CallInst and InvokeInst have *massive* amounts of code shared and struggle

Hello llvm devs, Melpa[1] is pretty much the most common package manager for emacs and very recently the llvm-mode got removed from it[2] due to performance issues. This issue is not unique to llvm-mode, but affects a bunch of projects with very large git repositories[3]. Will it be possible to split this into a new separate git repo? This should make it easier for the emacs community to work

I'm trying to set up Johannes's DSpam plugin for dovecot. I've compiled rc2 and the plugin, and have things installed OK. I have a X-DSPAM-Signature in my message that is delivered to Inbox. Whenever I try to move this to my spam folder (I changed source to say 'Spam' instead of 'SPAM'), my client (Thunderbird) pops up 'The current command did not succeed. The

On Thu, May 17, 2018 at 10:32 AM Xinliang David Li <xinliangli at gmail.com> wrote: > > > On Thu, May 17, 2018 at 2:03 AM, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Going to keep this RFC short and to the point: >> >> TerminatorInst doesn't pull its weight in the type system. There is >> essentially a single

On 05/17/2018 04:03 AM, Chandler Carruth via llvm-dev wrote: > Going to keep this RFC short and to the point: > > TerminatorInst doesn't pull its weight in the type system. There is > essentially a single relevant API -- iterating successors. There is no > other interesting aspect shared -- the interface itself just > dispatches to specific instructions to be implemented.

On Thu, May 17, 2018 at 1:24 PM, Chandler Carruth <chandlerc at gmail.com> wrote: > On Thu, May 17, 2018 at 10:32 AM Xinliang David Li <xinliangli at gmail.com> > wrote: > >> >> >> On Thu, May 17, 2018 at 2:03 AM, Chandler Carruth via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> Going to keep this RFC short and to the

On Thu, May 17, 2018 at 2:03 AM, Chandler Carruth via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Going to keep this RFC short and to the point: > > TerminatorInst doesn't pull its weight in the type system. There is > essentially a single relevant API -- iterating successors. There is no > other interesting aspect shared -- the interface itself just dispatches to

On Fri, May 18, 2018 at 10:26 PM Chris Lattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > > On May 17, 2018, at 2:03 AM, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Going to keep this RFC short and to the point: > > > > TerminatorInst doesn't pull its weight in the type system. There is >

> On May 17, 2018, at 2:03 AM, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Going to keep this RFC short and to the point: > > TerminatorInst doesn't pull its weight in the type system. There is essentially a single relevant API -- iterating successors. There is no other interesting aspect shared -- the interface itself just dispatches to

On 10 May 2018 at 06:07, Jaseem Abid via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Melpa[1] is pretty much the most common package manager for emacs and very > recently the llvm-mode got removed from it[2] due to performance issues. Wouldn't svn be better here? It ought to allow you to checkout just the utils/emacs directory (or not even that with "svn cat").

[AMD Official Use Only - Internal Distribution Only] Hi , There seems to be some issue with attributor, exactly in File Attributor.cpp, Function Attributor::rewriteFunctionSignatures(), Line No: 1600 (approrimate). The llvm source code at above address is as follows: // Eliminate the instructions *after* we visited all of them. for (auto &CallSitePair : CallSitePairs) {

+1, sounds like a great idea And if you're volunteering to do the work, even better! :) Philip p.s. Any reason we can't preserve a TerminatorInst type with an isa function which just returns true for all our terminators but without having terminators actually inherit from it?  If so, we preserve the bit of a "type safety" for a variable which is expected to always point to