search for: methodid

I'm trying to find a clever way to re-map data from a database query into a data.frame. Querying a database often returns a table (data.frame) like this: GeneID MethodID Value 6 1 123 6 2 456 6 3 987 7 1 234 7 3 432 8 2 190 8 3 34 8 1 864 Note that GeneID=7 doesn't have a value for MethodID=2. Note that GeneID=8 doesn't have the MethodID in any particular order and, in fact, there doesn't need to be an or...

...} } - virConnectClose(connection); + virConnectClose(connection); host->beeping = false; } @@ -228,16 +228,16 @@ void HostWrapper::shutdown() system("shutdown -h now"); } -Manageable::status_t -HostWrapper::ManagementMethod(uint32_t methodId, Args& args, string& text) +Manageable::status_t +HostWrapper::ManagementMethod(uint32_t methodId, Args& args, string& text) { switch(methodId) { case _qmf::Host::METHOD_SHUTDOWN: - shutdown(); - return Manageable::STATUS_OK; + shutdown(); +...

Hi Nicolas, >> This might help. See how "stack protectors" is implemented here: >> >> lib/CodeGen/StackProtector.cpp >> >> It places a special value at a specific place on the stack. You can >> use the same trick to put your own information on a set stack >> position. There's more to the code than just that .cpp file. It's >>

Hi Bill, Bill Wendling wrote: > > This might help. See how "stack protectors" is implemented here: > > lib/CodeGen/StackProtector.cpp > > It places a special value at a specific place on the stack. You can > use the same trick to put your own information on a set stack > position. There's more to the code than just that .cpp file. It's done >

...se the Hal Context + put_hal_ctx(hal_ctx); } -void HostWrapper::reboot() +void +HostAgent::update(void) { - system("shutdown -r now"); -} - -void HostWrapper::shutdown() -{ - system("shutdown -h now"); -} - -Manageable::status_t -HostWrapper::ManagementMethod(uint32_t methodId, Args& args, string& text) -{ - switch(methodId) { - case _qmf::Host::METHOD_SHUTDOWN: - shutdown(); - return Manageable::STATUS_OK; - case _qmf::Host::METHOD_REBOOT: - reboot(); - return Manageable::STATUS_OK; - } - return...

...r(), IFNAMSIZ - 1); - ifr.ifr_data = (caddr_t)&edata; - - sock = socket(AF_INET, SOCK_DGRAM, 0); - ret = ioctl(sock, SIOCETHTOOL, &ifr); - close(sock); - - if (ret != 0) - ret = errno; - - return ret; -} - -Manageable::status_t -NICWrapper::ManagementMethod(uint32_t methodId, Args& args, string& text) -{ - switch (methodId) { - case _qmf::NIC::METHOD_IDENTIFY_NIC: - _qmf::ArgsNICIdentify_nic& ioArgs = (_qmf::ArgsNICIdentify_nic&) args; - int seconds = ioArgs.i_seconds; - ioArgs.o_ret = identifyNIC(seconds); -...

...than a simple push and pop. > Also, out of curiosity: are you working on something like Java > security contexts? Or perhaps something like ProPolice canary values? > > I'm working on VMKit, which implements a JVM on top of LLVM. And an easy way to walk the stack is to have a methodID stored in each stack frame to locate which method the frame belongs to. Nicolas

In looking at the code I realized that the last of the HAL depenencies were removed with this patch. So, I'm pushing an updated patch that contains none of the HAL code in it.

> I'd like to generate this layout: > > 12(%ebp) - second function parameter > 8(%ebp) - first function parameter > 4(%ebp) - old %EIP (the function's "return address") > 0(%ebp) - old %EBP (previous function's base pointer) > -4(%ebp) - My language specific information > -8(%ebp) - first local variable > -12(%ebp) -

Hi everyone, As a front-end developer, I'd like to add a language-specific information at a fixed location of each stack frame. The reason is that I want to retrieve this information when dynamically walking the stack. For example, X86 has the following stack layout for a function with two arguments and two locals: 12(%ebp) - second function parameter 8(%ebp) - first function

...flags = flags__; - } - -public: - - // Factory like method - static void fillCPUInfo(vector<CPUWrapper*> &cpus, ManagementAgent *agent); - - // QMF Methods - ManagementObject* GetManagementObject(void) const { return mgmt_object; } - - status_t ManagementMethod(uint32_t methodId, Args& args, string& text) { - return STATUS_NOT_IMPLEMENTED; - } - - // Field Accessors - int getCpunum(void) { return cpunum; } - int getCorenum(void) { return corenum; } - int getNumcores(void) { return numcores; } - - int getModel(void) { return model; } - in...

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...68865 me_fullsearch.ll 5 205532 0 0.02 205511 0 0.02 205511 memalloc.ll 47 144392 0 0.02 144371 * * * member-function-pointers.ll 6 7652 0 0.01 7641 0 0.01 7641 MemBlocks.ll 16 46800 0 0.01 46768 0 0.01 46768 memory.ll 12 44937 0 0.01 44907 0 0.01 44907 methcall.ll 9 15754 0 0.01 15735 0 0.01 15735 MethodId.ll 1 6496 0 0.01 6464 0 0.01 6464 MethodProps.ll 3 36369 0 0.01 36337 0 0.01 36337 me_umhex.ll 14 589759 0 0.05 589738 0 0.05 589738 me_umhexsmp.ll 12 428141 0 0.04 428120 0 0.04 428120 mgrep.ll 7 78013 0 0.02 77987 0 0.02 77987 miller.ll 1 19639 0 0.01 19622 0 0.01 19622 mincov.ll 5 84617 0 0.02 8...