search for: errorprone

...rks if building a tool). I wish to be able to do the following, assuming that I named that library LLVM_C gcc -lc -lLLVM_C c_file_using_llvm.c -I<stuff> -L<stuff> I *could* build everything as a shared library, and include everything on the command line that way, but that seems a bit errorprone, not to mention the fact that building everything with PIC takes ~3x longer. -- -Alex

...owing, assuming that I named that > > library LLVM_C > > > > gcc -lc -lLLVM_C c_file_using_llvm.c -I<stuff> -L<stuff> > > > > I *could* build everything as a shared library, and include everything > > on the command line that way, but that seems a bit errorprone, not to > > mention the fact that building everything with PIC takes ~3x longer. > > This should be possible, though our current makefile system is not going > to do this automatically right now. Can I add submit a patch to do something like this (if it doesn't disturb the ma...

...wish to be able to do the following, assuming that I named that > library LLVM_C > > gcc -lc -lLLVM_C c_file_using_llvm.c -I<stuff> -L<stuff> > > I *could* build everything as a shared library, and include everything > on the command line that way, but that seems a bit errorprone, not to > mention the fact that building everything with PIC takes ~3x longer. This should be possible, though our current makefile system is not going to do this automatically right now. -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

...so likewise needs to be added in many files - It is very tedious to do this properly. The process I followed was: - delete / comment out all include files - add back the obvious from a quick scan of the code - build - fix - build - fix - build - fix ... - next file... - The result is errorprone as only the allyesconfig + allmodconfig variants are tested. But reallife configurations are more diverse. Current diffstat: 111 files changed, 771 insertions(+), 401 deletions(-) This is for the 5 drivers alone and not the header cleanup. So long story short - this is not good and not the w...

On Mar 13, 2011, at 2:01 PM, Arnaud Allard de Grandmaison wrote: > Hi all, > > The IndVarSimplify pass seems to be too aggressive when it enlarge the induction variable type ; this can pessimize the generated code when the new induction variable size is not natively supported by the target. This is probably not an issue for x86_64, which supports natively all types, but it is a real one

Hi, I''m trying to clarify if it''s at all possible to live resize a disk image. After trying and failing it seems that the reason a disk image cannot be resized - is that domU is only able to detect changes in partitions (eg. partprobe), not in block devices as the xvd driver lacks a rescan feature. My domU sees disk images as blockdevices - that is without a partition table,

On Fri, 13 May 2005, Alexander Friedman wrote: >>> This requires being able to parse strings. The LLVM 'Parser.h' interface >>> (and implementation) has the built in assumptions that it will always be >>> parsing from the file system. Would you guys accept a patch that makes >>> it more general (ie, parse from file or string)? >> >> Yes,

On Wed, Jan 16, 2019 at 07:10:18PM +0100, Sam Ravnborg wrote: > Hi Daniel. > > > v5: Actually try to sort them, and while at it, sort all the ones I > > touch. > > Applied this variant on top of drm-misc and did a build test. > Looked good for ia64, x86 and alpha. > > Took a closer look at the changes to atmel_hlcd - and they looked OK. > > But I noticed

> > This requires being able to parse strings. The LLVM 'Parser.h' interface > > (and implementation) has the built in assumptions that it will always be > > parsing from the file system. Would you guys accept a patch that makes > > it more general (ie, parse from file or string)? > > Yes, that's a generally useful thing to have, I'd like to see it

I upgraded from 6.2 to 6.3 p5 last night. Upon rebooting, the second disk in the mirror is missing. # atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad0 ONLINE 1 ---- MISSING # grep ata /var/run/dmesg.boot ad0: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-master UDMA100 ad1: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-slave UDMA100 ar0: disk0

Hi all, The IndVarSimplify pass seems to be too aggressive when it enlarge the induction variable type ; this can pessimize the generated code when the new induction variable size is not natively supported by the target. This is probably not an issue for x86_64, which supports natively all types, but it is a real one for several embedded targets, with very few native types. I attached a patch to