search for: precludes

Do you use the LLVM_INCLUDE_TESTS setting? If so, what for? It is documented to preclude the inclusion *unittests* in the build. What it actually does in preclude *all* LLVM testing (unit and regression), but only unittests for Clang. The Clang regression tests continue to be built and run. My preference is simply to remove it if none have an important use case. If they do, I would like to

On Fri, 26 Apr 2019 20:32:38 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Nothing precludes to accepting VIRTIO_F_RING_PACKED any more. "precludes us from accepting" > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/drivers/s...

Hi, I built llvm-gcc and tried to use it as drop-in replacement of gcc. I attempted to build busybox with it. It choked on -std=gnu99. Reduced testcase: struct stat {}; struct stat64 {}; int fxstat(int n, int fd, struct stat *sb); int fxstat64(int n, int fd, struct stat64 *sb); extern int fstat(int fd, struct stat *buf) asm("fstat64"); extern inline int fstat(int fd, struct stat *sb)

Hi, We use CMake but don't use that setting. Cheers, James On 29 June 2012 12:40, Chandler Carruth <chandlerc at google.com> wrote: > Do you use the LLVM_INCLUDE_TESTS setting? If so, what for? > > > It is documented to preclude the inclusion *unittests* in the build. > > What it actually does in preclude *all* LLVM testing (unit and regression), > but only

>> >> So, my two questions are: >> - How do I map the domain\administrator account to a UID other than 0. > > You don't really want to change this, it maps 'Administrator' to the > Unix 'root' user and this allows the changing of ACLs etc. > Just because the Administrator user is a non-root user does not preclude it from changing ACLs. It may

On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > Michael pointed out that the virtio-vsock draft specification does not > > address live migration and in fact currently precludes migration. > > > > Migration is fundamental so the device specification at least mustn't > > preclude it. Having brainstormed migration with Matthew Benjamin and > > Michael Tsirkin, I am now summarizing the approach that I want to > > include in the next draft s...

On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > Michael pointed out that the virtio-vsock draft specification does not > > address live migration and in fact currently precludes migration. > > > > Migration is fundamental so the device specification at least mustn't > > preclude it. Having brainstormed migration with Matthew Benjamin and > > Michael Tsirkin, I am now summarizing the approach that I want to > > include in the next draft s...

Michael pointed out that the virtio-vsock draft specification does not address live migration and in fact currently precludes migration. Migration is fundamental so the device specification at least mustn't preclude it. Having brainstormed migration with Matthew Benjamin and Michael Tsirkin, I am now summarizing the approach that I want to include in the next draft specification. Feedback and comments welcome! In...

Michael pointed out that the virtio-vsock draft specification does not address live migration and in fact currently precludes migration. Migration is fundamental so the device specification at least mustn't preclude it. Having brainstormed migration with Matthew Benjamin and Michael Tsirkin, I am now summarizing the approach that I want to include in the next draft specification. Feedback and comments welcome! In...

...mmend gcc 4.5 as the baseline: that's when you can start using lambdas > and atomics (and a few other unicode goodies, but MSVC has yet to support > those anyways, so the point is fully moot). Anything older than gcc 4.4 > loses you most of the C++11 features. MSVC 2010 as the baseline precludes > you primarily from the following features: > * raw, user, unicode string literals > * enum class [that's 2012] > * alignment support > * extra constructor features > * explicit conversion operators > * range-based for > * intializer lists > * constexpr variadic tem...

Hello, I recently upgraded our file server from RedHat6.2 to RedHat7.2. This upgraded our (working) Samba 2.0.x to 2.2.1a-4. Now, the windows98 machines on the network can print without problems. The 2K/NT4 machines cannot print, but they experience no problems with file sharing operations (writeable /home/$USER). The 2K/NT4 machines had been printing fine prior to the upgrade. I won't

Hello, I want to create and save objects in a loop, but this is precluded by the following obstacle: this part of the script fails to work: assign(x=paste("a", 1, sep=""), value=1); save(paste("a", 1, sep=""), file=paste(paste("a", 1, sep=""), ".RData", sep="")) Do you know any workaround? I am already out of ideas.

...ike a bug in Visual Studio, but we could not find a resolution other than changing LLVM as noted below). 2) We chose to use delay loading for symbols imported by Polly from clang. This allows the Polly dll to be loaded into any executable that provides the required symbols. However delay loading precludes the importing of data[1]. We would like to resolve these issues by replacing public access of the ID with a getter: class AliasAnalysis { private: static char ID; // Class identification, replacement for typeinfo public: static const void *getClassPassID(); };...

I'm relatively new to LLVM so apologies in advance if this is a dumb question. I've been experimenting with re-targeting LLVM onto a 16-bit micro which has pre and post increment and decrement addressing modes. I've been using llvm-gcc to generate llvm bitcode and llvm 2.7 to go from here to my target assembly code. I've got the Combine pass to deal with

Currently these leave in lib/Transforms/ObjCARC even though they are analysis passes. This seems confusing and odd. In particular, Analysis/Passes.h talks about ObjCARCAliasAnalysis. =/ I'd like to just move the analysis headers to live under include/llvm/Analysis and the source under lib/Analysis. This will preclude omitting the ObjC ARC analysis passes from your build of LLVM if you

I am not currently subscribed so please email me below. First, my only experience with rsync has been older versions (e.g. 1.7.x) which did not allow daemon mode, so please bear with me. My problem is that I would like to mirror large quantities of data on a remote machine to a local one, but I don't care about encrypting the data itself. I only care about securing the connection from the

The default generic method for "show" has arguments show(object) -- (no "...") -- which precludes any kind of arguments like "digits", etc. Is it impossible, or a horrible idea, to override the generic definition? (The "arm" package has defined a new generic, "display", which does a similar thing but has an intermediate level of detail (between "print/show...

I have numerous qcow2 images which need to be reduced in size and have their maximum size (virtual size) reduced. Physical disk space became so low that VMs "auto-paused" themselves, I moved enough images to solve the immediate problem but need to rectify the underlying issue. It seems that qcow[2] files are grown in size such that the data inside of them takes about 50-60% of the

...compatibility problem. The virtio device should advertise whether it's using that bypass mode of operation and virtio_pci should react accordingly. There is a demand for being able to operate on top of an IOMMU on powerpc as well for some embedded stuff using PCI as a transport so your patch precludes that. Cheers, Ben. > > Signed-off-by: Andy Lutomirski <luto at amacapital.net> > --- > drivers/virtio/virtio_pci.c | 90 ++++++++++++++++++++++++++++++++++++++++----- > 1 file changed, 81 insertions(+), 9 deletions(-) > > diff --git a/drivers/virtio/virtio_pci.c b/dr...

...compatibility problem. The virtio device should advertise whether it's using that bypass mode of operation and virtio_pci should react accordingly. There is a demand for being able to operate on top of an IOMMU on powerpc as well for some embedded stuff using PCI as a transport so your patch precludes that. Cheers, Ben. > > Signed-off-by: Andy Lutomirski <luto at amacapital.net> > --- > drivers/virtio/virtio_pci.c | 90 ++++++++++++++++++++++++++++++++++++++++----- > 1 file changed, 81 insertions(+), 9 deletions(-) > > diff --git a/drivers/virtio/virtio_pci.c b/dr...