similar to: [LLVMdev] Statistic API change

Displaying 20 results from an estimated 40000 matches similar to: "[LLVMdev] Statistic API change"

2002 Oct 01
0
[LLVMdev] Statistic API change
This is just a note to mention that I just checked in this patch: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20020930/000541.html This change breaks the Statistic<> api, so any code not in CVS will have to be updated to work with the new system. In short, these are the changes you'll have to make: * #include "Support/Statistic.h" instead of
2002 Dec 03
5
Locked Dirs
Hey there I recently downloaded a folder off an ftp that had [hxc] as the bwginning name of thr dir, now it says it's locked when I try to delete it in KDE. when I try to rm -f in a console it says it doesn't exist, I can't move it, delete it , or change anything about it. When I output a ls -la to a txt it says this about it "drwxr-xr-x 2 root root 4096 Dec 2
2007 Jul 04
0
[LLVMdev] API design (and Boost and tr1)
On Wed, 4 Jul 2007, David A. Greene wrote: > I have to think about this a bit but one complication is that clients aren't > always using std-like containers. There are several places that look like > this: > > Value *array = { v1, v2, v3, v4}; > blah = new CallInst(...,&array[0], 4,...); > > Since array doesn't have begin/end members we'd need some kind
2014 May 04
2
[LLVMdev] indirect calls tracking and control flow graph
Thank you, I tried to compile it with llvm 3.4 through these commands: petsas at shinigami:~/software/poolalloc$ ./configure --with-llvmsrc=/home/petsas/software/llvm --with-llvmobj=/home/petsas/software/llvm petsas at shinigami:~/software/poolalloc$ make but I'm getting get this error: make[1]: Entering directory `/home/petsas/software/poolalloc/lib' make[2]: Entering directory
2015 Jul 03
3
[LLVMdev] DEBUG_TYPE
In include/llvm/ADT/Statistic.h, the identifier “DEBUG_TYPE” is never defined. I’ve noticed it’s defined as different things in a few other header files, including llvm/Analysis/BlockFrequencyInfoImpl.h, llvm/Analysis/RegionInfoImpl.h, llvm/Support/UnicodeCharRanges.h, llvm/Transforms/InstCombine/InstCombineWorkList.h, and llvm/Transforms/Utils/SSAUpdaterImpl.h. Should I edit Statistic.h so that
2003 Aug 01
0
[LLVMdev] Changes to the DEBUG macro.
This is an important change for people using the DEBUG macro (which should be all of you :). The critical piece is that you now need to #include "Support/Debug.h" to get access to DEBUG, not "Support/Statistic.h". In addition to this change, you can now make the DEBUG output much more fine-grained than before. For details, consult the programmer's guide:
2010 Aug 14
0
[LLVMdev] Questions about trip count
On Thu, Aug 12, 2010 at 5:22 PM, Tobias Grosser <grosser at fim.uni-passau.de>wrote: > On 08/12/2010 09:41 PM, Douglas do Couto Teixeira wrote: > >> Dear guys, >> >> I am having problems to obtain good information from the LoopInfo. >> I am always getting a trip count of 0, even though I am clearly passing >> a loop with a constant bound. I am using
2015 Jun 08
2
[LLVMdev] Removing AvailableExternal values in GlobalDCE (was Re: RFC: ThinLTO Impementation Plan)
Talked to Eric Fri and he suggested that this might be the first of several places where we want behavior of LTO compiles to diverge from normal -O2 compiles. So for now I have implemented this such that we pass down -flto to the -cc1 job, and that gets propagated as a code gen option and into the PassManagerBuilder. I have left the current logic translating -flto to the -emit-llvm-bc option,
2017 Sep 19
0
RFC: Use closures to delay construction of optimization remarks
Sean, hopefully you’re OK with that reasoning. I went ahead and committed this in r313691. > On Sep 16, 2017, at 10:43 PM, Adam Nemet <anemet at apple.com> wrote: > > >> On Sep 16, 2017, at 4:49 PM, Sean Silva <chisophugis at gmail.com <mailto:chisophugis at gmail.com>> wrote: >> >> Actually maybe something like: >> >> if (auto &E
2006 Sep 08
2
[LLVMdev] build broken on linux/amd64
On Fri, 8 Sep 2006, [UTF-8] Rafael Esp?ndola wrote: > I am not sure if it is the correct solution, but the attached patch > fixes the problem. Your solution is correct, in that it will work and follows with the current ifdef approach. I applied this patch though, which doesn't use the ifdefs, hopefully it is more robust:
2007 Jun 14
2
API towards cFerret
Hello list, I know this is a little OT but I wonder how I would go about using cFerret directly through C/C++ for indexing. Right now I do index = Index::Index.new(:path => ''/path/to/index'') index << {:title => "Programming Ruby", :content => "blah blah blah"} How would I do this in C/C++ against cFerret? Thanks! //Henrik
2017 Sep 17
2
RFC: Use closures to delay construction of optimization remarks
> On Sep 16, 2017, at 4:49 PM, Sean Silva <chisophugis at gmail.com> wrote: > > Actually maybe something like: > > if (auto &E = ORE.emitMissed(DEBUG_TYPE)) { > E.emit(...) << ...; > } Well, the point of this interface was exactly to avoid writing a conditional. If you’re willing to use a conditional you can already write this: if
2015 Nov 02
4
Prefixing DEBUG messages with DEBUG_TYPE (was re: [PATCH] D13259: LLE 6/6: Add LoopLoadElimination pass)
----- Original Message ----- > From: "Matthias Braun via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Daniel Berlin" <dberlin at dberlin.org> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, November 2, 2015 1:16:18 PM > Subject: Re: [llvm-dev] Prefixing DEBUG messages with DEBUG_TYPE (was re: [PATCH] D13259: LLE 6/6: Add
2009 Sep 15
0
[LLVMdev] C API linking problem
"Paul Melis" <llvm at assumetheposition.nl> writes: >>> 15:29|melis at juggle2:~/c/llvmpy> gcc -W -Wall -o blah `llvm-config >>> --cflags >>> --ldflags --libs all` t.c >>> /tmp/ccs4MbKp.o: In function `main': >>> t.c:(.text+0x21): undefined reference to `LLVMContextCreate' >>> collect2: ld returned 1 exit status
2015 Nov 02
2
Prefixing DEBUG messages with DEBUG_TYPE (was re: [PATCH] D13259: LLE 6/6: Add LoopLoadElimination pass)
Moving this discussion here from the review thread. RIght now, we have a few passes that prefix DEBUG message with various things, so folks using -debug can tell where the debug message came from. But this is not consistent, and in fact, most passes don't do it. Worse, the prefixes used do not often match the DEBUG_TYPE of the pass. It would be nice to fix this, and just have the DEBUG
2015 Apr 24
2
Development version of R: Improved nchar(), nzchar() but changed API
Those of you who track R development closely, will have noticed yesterday's commit of enhanced versions of nchar() and nzchar(). ------------------------------------------------------------------------ r68254 | maechler | 2015-04-23 18:06:37 +0200 (Thu, 23 Apr 2015) | 1 line Changed paths: M doc/NEWS.Rd M src/library/base/R/New-Internal.R M src/library/base/R/zzz.R M
2005 May 19
0
[LLVMdev] JIT + tail cals
On Wed, 18 May 2005, Chris Lattner wrote: > Yup, something like this should work. Two comments though: > 2. I haven't done much testing with the JIT and tail calls. I wouldn't be > suprised if there are minor issues that need to be fixed. I will try > to take a look and see what remains to be done over the next couple of > days. As I expected, there were issues. I
2006 Mar 15
1
[LLVMdev] Re: Garbage collection questions
On Tue, 14 Mar 2006, Sandro Magi wrote: > I've attached the lazy ref-counting collector if anyone's interested. > There are a few suggested enhancements in the source for those who > might want to extend it, such as bounds for real-time constraints, or > adding generations to reduce the overhead of filtering out the live > roots. :-) By the way, how are you testing this?
2009 Jul 27
2
[LLVMdev] PROPOSAL : Introduce NamedMetadata
On Mon, Jul 27, 2009 at 1:13 PM, Dan Gohman<gohman at apple.com> wrote: > > On Jul 27, 2009, at 10:10 AM, Devang Patel wrote: > > >> In LLVM IR metadata is used to attach auxiliary information with >> various IR constructs. Currently metadata information is represented >> using MDNode and MDString. The metadata can refer to LLVM values but >> these
2009 Dec 21
2
[LLVMdev] [PATCH] Implement dbgs()
On Saturday 19 December 2009 00:16, Chris Lattner wrote: > > Or I think I can just assume (Yikes!) that if the signal handler is > > invoked it will really be a circular_raw_ostream since the handler > > should (!) only be set up in debug mode. > > > > That scares me a bit, though. > > Why don't you just check #ifndef NDEBUG like the code that sets it up?