similar to: [LLVMdev] [Patch] Module Flags Patch

Hi! This is a patch for module flags that I talked about here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-January/046857.html This patch creates an interface in the Module class to get and create module flags for a Module. The bulk of the patch deals with code in the Linker to merge module flags from two (or more) Modules when those Modules are linked together. This patch doesn't

All, Is there one liner way to obtain the max per observation for two vectors? I looked at apply and lapply but it seems that groundwork would have to be done before applying either of those. The code below does it but seems like overkill. Thanks! Dave x = rnorm(10) y = rnorm(10) ind = which(x < y) z = x z[ind] <- y[ind] ## z now contains the max's

Can anyone recommend an enterprise-class monitoring system for both Linux and Windows servers? Here are my requirements: SNMP trap collection, ability to import custom MIBs isup/isdown monitoring of ports and daemons Server health monitors (CPU, Disk, Memory, etc) SLA reporting with nice graphs Pager/Email/SMS alerts with groups, filters and escalations Built-in MTBF and MTTR reporting Robust

On Tue, May 28, 2019 at 10:23:13AM -0500, Eric Blake wrote: > But having some sort of callback that gets invoked > on each chunk would allow the client to add in such checking; we could > even provide a utility function in the library to serve as such a > callback if our checking is sufficient for the client's purposes. > Something like: > > nbd_pread_callback(nbd, buf,

Thanks for the detailed response. On Apr 23, 2007, at 4:22 PM, Chris Lattner wrote: > Right. Evan is currently focusing on getting the late stages of > the code > generator (e.g. livevars) to be able to understand arbitrary machine > instrs in the face of physreg subregs. This lays the groundwork for > handling vreg subregs, but won't solve it directly. Is the work Evan

Hi all, I wanted to let you know that I feel I need to step down as leader of the Virtualisation SIG. When I originally was approached by KB to do this, it was always clear that this would be a temporary thing until the SIG got going. At the time, only Xen and CentOS folks were involved with the SIG. Since then, we added oVirt and Docker maintainers, have a total of 5 maintainers and built good

Matt asked me this morning if we could generate guestfish scripts automatically from running programs like virt-v2v. Good idea. This patch however doesn't do this, but it lays the groundwork for it: In order for us to generate code for any functions which don't go through the daemon, we need to add an indirection to those calls via some generated code. This will allow us to add

Hi This is a bit of an exploratory question for groundwork before I start playing with asterisk 12. I've spotted the very useful looking file contrib/realtime/mysql/mysql_config.sql in the source. Are the table names starting ps_ all to do with PJSIP? Direct MySQL connection has been deprecated for quite a while, will I need to use ODBC for PJSIP or will it be supported by the old

Greetings, I have created several scripts which needs to be packaged. I have done my groundwork on rpmbuild Let us say I have 4 directories with scripts in them dir1, dir2, dir3 and dir4 I want to create different packages which will contain the compiled code (err.. shc) pack1: dir1,dir2 pack2: dir1,dir3 pack3: dir1,dir3 I want the resulting rpm packages will be residing elsewhere (perhaps

Hi Bill, For the GNU runtimes, this metadata is stored in the module structure in each compilation unit, and uses a different set of flags. Do you have any plans for this to be generic, or is it intended just for Darwin? David On 19 Jan 2012, at 23:33, Bill Wendling wrote: > Hi Sandeep, > > ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses

All, The attached patch adds two extra arguments to TargetLowering::LowerCall: RetTy and Args. These arguments are used in TargetLowering::LowerCallTo() to construct the Ins and OutVals parameters, but are not available to the target via LowerCall(). Some targets require this additional information, and the LowerCallTo() method is not virtual in TargetLowering. Instead of making that method

Hi Bill, > This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have. what does this give you that you can't get with the existing scheme of using global variables in a special section? Ciao, Duncan. > > Thanks! > -bw > > Module Flags Metadata > > Information about the module

On Apr 23, 2007, at 4:07 PM, Christopher Lamb wrote: > Thanks for the detailed response. > > On Apr 23, 2007, at 4:22 PM, Chris Lattner wrote: > >> Right. Evan is currently focusing on getting the late stages of >> the code >> generator (e.g. livevars) to be able to understand arbitrary machine >> instrs in the face of physreg subregs. This lays the

On Mon, 23 Apr 2007, Christopher Lamb wrote: >>> The issue I'm having is that there is no extract/insert >>> instruction in the ISA, it's simply based on using subregister >>> operands in subsequent/preliminary instructions. At the pointer of >>> custom lowering register allocation has not yet been done, so I >>> don't have a way to

Hi Sandeep, ObjC is the first place that I will use it, of course (we need it to fix LTO). Other uses will come along later. (I don't know enough about the float ABI issues to say whether they should be done via module flags or not.) The OpenCL people have a need for named metadata for their stuff. I would hope that module flags would be a good fit for that, but that remains to be seen. But

Could you expand on likely uses other than ObjC? For example, should float ABI (soft/softfp/hard) be conveyed via this mechanism? deep On Wed, Jan 18, 2012 at 9:36 PM, Bill Wendling <wendling at apple.com> wrote: > Hello, > > This is a proposal for implementing "module flags". Please take a look at this and give any feedback you may have. > > Thanks! > -bw >

On Wed, Jan 18, 2012 at 1:36 PM, Bill Wendling <wendling at apple.com> wrote: > Hello, > > This is a proposal for implementing "module flags". Please take a look at > this and give any feedback you may have. > > Thanks! > -bw > > Module Flags Metadata > I have only one real comment -- this violates the contract and spirit of

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

TargetLowering::LowerCall is already a mess, I would really prefer not to extend it any further. It's especially difficult to justify extending it without a use in the open source tree. We really should think hard about how to improve the API in two ways. Perhaps we should wrap the arguments in some struct rather than as individual ones. We should also make it easier to extend it in the

On Jan 19, 2012, at 4:20 PM, David Chisnall wrote: > Hi Bill, > > For the GNU runtimes, this metadata is stored in the module structure in each compilation unit, and uses a different set of flags. Do you have any plans for this to be generic, or is it intended just for Darwin? > Hi David, This should be generic as is. :) -bw