search for: instrucation

The intrinsic instructions always have an number in the end, what's meaning of it? For example, %2 = call <2 x double> @llvm.x86.sse2.sqrt.pd(<2 x double> %1) #2 What does this #2 mean? Can I ignore it when I create the instruction? Thanks. Best, Zhi -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello everyone, I was able to get all the execution paths between 2 points (basic blocks) in my program (with the condition to traverse a loop only once). I mapped all the basic blocks to integers and created a correspondent directed graph. I was able to get all the paths (a path is represented by an integer identifier). For my target program I have 72 paths, but the program hangs unexpectedly

As an update, it is a memory problem which I don't know how to fix. I tried to skip the problematic piece of code when in the case when the loop hangs. So I did something like : if( instr ) { LLVMContext& C = instr->getContext(); Value* values[cnt]; errs()<<"\ngy: \n"; if(!(desters==7)){ // this

Hi, I don't know much about this issue, but this malloc error won't be solved by a change to delete[] or free. In fact, if you use the incorrect one for simple types, you may not notice it. The error you have seems to me like a memory corruption because you went out of bound and corrupted the memory somewhere, Valgrind may help you figure out what is going on. Cheers, Matthieu

In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Recent (testing) Clonezilla versions include changes related to >booting problems, so there are valid reasons to try the very latest >version available. At the time I am writing this email, Clonezilla >Live 2.2.1-22 is the latest available (at this moment, under

In message <BLU0-SMTP557B92590B4CC34F8318088BB30 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >Since in all cases you get to see at least the Syslinux copyright >message, the problem doesn't seem to be related to whether your BIOS >can identify the USB disk and boot from it. I can only agree. >Some GA motherboards might identify some USB drives as

This patch series implements SMP boot for arch/arm, as far as getting all CPUs up and running the idle loop. Changes from v1: - moved barriers out of loop in udelay() - dropped broken GIC change in favour of explanatory comment - made the increment of ready_cpus atomic (I couldn''t move the increment to before signalling the next CPU because the PT switch has to happen between