search for: sourcebase

I tried using $name in this manner: remotefile { "/etc/auto_direct.local": mode => 644, source => "solall/$name" } (The remotefile function is handy, BTW) When I use $name here, instead of specifying the actual path to the file (solall/etc/auto_direct.local), puppetd ends up making /etc/auto_direct.local an empty directory. Shouldn''t $name

...hing is that it makes the extra checking code apparently useless :( > I'd like to get the extra checks working so that they can help find our > more subtle bugs. Any idea what we should do here? I don't really have a good idea, but I also don't want to significantly uglify the sourcebase... -Chris -- http://nondot.org/sabre/ http://llvm.org/

Hi, I've been running LLVM with _GLIBCXX_DEBUG (extra checks) turned on to see what would happen, and it's been a complete disaster. The major problem is the use of this API: new CallInst(V, &Args[0], Args.size()); repeated throughout LLVM. When Args is empty, Args[0] is invalid, even if the next operation is taking the address. Trying to fix it illustrates the depth of the

> > I'd like to get the extra checks working so that they can help find our > > more subtle bugs. Any idea what we should do here? > > I don't really have a good idea, but I also don't want to significantly > uglify the sourcebase... #define V_CALLINST(V, Args) new CallInst(V, Args.size() == 0 ? NULL : &Args[0], Args.size()) :p -Keith

...ces nor Sieve scripts etc. # # Originally created by Peter Lindgren <peter at norrskenkonsult.com> # Use this script at your own risk. No warranties whatsoever, of any kind! # Basic settings: The first one you must definitely change, it's where you have mounted the old server's home: SOURCEBASE=/mnt/casiopea-home DESTBASE=/home # Just an abbreviation: MD=Maildir # Change field separator, for find's sake as there might be folders with spaces: # (doesn't play well together with the for loop otherwise) OLDIFS=${IFS} IFS=' ' # User loop: # Depending on your source system...

On 11 November 2010 07:46, Chris Lattner <clattner at apple.com> wrote: > It's actually not any harder to change and keep up to date than anything else.  HTML pages have the advantage of showing up in a recursive grep of the sourcebase, and showing up in llvm-commits so they fall into the peer review process. Hi Chris, I understand that this is more of a personal preference than a technical discussion... Diff-ing HTML is not easy and enforcing style even less. Most Wiki have revision control (albeit, different than your main s...

...are explicitly dated. > On the other hand, HTML documents, while > good for release process, are hard to change and keep it up-to-date. It's actually not any harder to change and keep up to date than anything else. HTML pages have the advantage of showing up in a recursive grep of the sourcebase, and showing up in llvm-commits so they fall into the peer review process. > As I said before, I'm looking for a (or writing a new) script to > convert from the Wiki to LLVM-HTML style, and I think we should use > the Wiki more often to keep not only the documents up-to-date, but >...

.... But it still results in undefined behavior. > > I'd like to get the extra checks working so that they can help find our > > more subtle bugs. Any idea what we should do here? > > I don't really have a good idea, but I also don't want to significantly > uglify the sourcebase... Passing two iterators is in the spirit of the standard library, so I don't consider that uglification. I understand others may disagree. In any event, leaving this kind of code in is asking for trouble down the road. -Dave

...ried it on the snapshot of 1/28/06 > using a user authenticated via GSSAPI/Kerberos, with this result, which > I think is acceptable: [...] It's not clear to me from the output, but does the connection close after the PAM account check failed? > Could we make this part of the openssh sourcebase? I think so, once it's clear that it's doing what it is intended, which is to make the behaviour more consistent with the different auth methods. (Damien?) -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement co...

Are there any ports of Ogg decoder to dsPIC processors ? Thanks don

Hi, this is a bit of a newbie question: I am trying to discover, given a block with a conditional and its successors, which condition (T/F) each successor applies to. There's almost identical code in CFGPrinter.cpp, but where it gets called in GraphWriter.h, the child_iterator type is a pretty hairy thing, so I still don't quite understand how to get one from a BasicBlock in my own

...0, Keith Bauer wrote: > > > I'd like to get the extra checks working so that they can help find our > > > more subtle bugs. Any idea what we should do here? > > > > I don't really have a good idea, but I also don't want to significantly > > uglify the sourcebase... > > #define V_CALLINST(V, Args) new CallInst(V, Args.size() == 0 ? NULL : > &Args[0], Args.size()) I'd actually prefer a new constructor here. One that doesn't take any Args at all. API wise its a little more clear what's going on, so you'd have: if (Args.size())...

...defined behavior is bad :) >>> I'd like to get the extra checks working so that they can help find our >>> more subtle bugs. Any idea what we should do here? >> >> I don't really have a good idea, but I also don't want to significantly >> uglify the sourcebase... > > Passing two iterators is in the spirit of the standard library, so I don't > consider that uglification. I understand others may disagree. I totally agree that it is clean, the question is, how do we make it work? Here's a different suggestion that cloning all the code....

...en files - Substantial improvements to the instcombine and reassociation passes - New DEBUG_TYPE macro: http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-August/000439.html - The -trace[m] runtime has been improved 12. Lots of house cleaning and restructuring are happening to the LLVM sourcebase and build system as we prepare for the big release. LLVM now compiles with GCC 3.3. Although a lot of progress is being made, it looks like we may have to slip the 1.0 release until the middle or end of september (~1 month), to get the infrastructure for bug-tracking and regression testing up...

On Nov 11, 2010, at 5:08 AM, Renato Golin wrote: > On 11 November 2010 07:46, Chris Lattner <clattner at apple.com> wrote: >> It's actually not any harder to change and keep up to date than anything else. HTML pages have the advantage of showing up in a recursive grep of the sourcebase, and showing up in llvm-commits so they fall into the peer review process. > > Hi Chris, > > I understand that this is more of a personal preference than a > technical discussion... > > Diff-ing HTML is not easy and enforcing style even less. Most Wiki > have revision con...

Coming back to the issues that I had integrating LLVM with MSSP, will the code in include/Support also be put in the llvm namespace? That will solve many problems and help prevent others. Rahul ---- Original message ---- >Date: Sun, 9 Nov 2003 10:13:03 -0600 (CST) >From: Chris Lattner <sabre at nondot.org> >Subject: [LLVMdev] LLVM namespac'ification >To: LLVMdev List

On 10 November 2010 07:27, Chris Lattner <clattner at apple.com> wrote: > I'd like to do more similar ones in the future, and encourage other contributors to also write other blog entries in general. Hi Chris, After discussing these topics in the dev meeting, I also have some input. First, blog posts are great for communicating changes and maybe outlining design decisions, but

Is it intentional that password auth using PAM continues trying to log on (giving password 3 prompts) in the case that a user is disabled (so that pam_account returns an error code). It can be argued both ways (saying 'you are disabled' is giving out too much information, making it look like you are entering the wrong password confuses and frustrates the user)

...h does not stop on errors. After that, I am combining all the .o files generated using 'llvm-ld --link-as-library --disable-opt' command. This sometimes causes problems with warnings of symbol duplications, duplication of main methods etc. Is there a proper approach of running analysis on a sourcebase which contains .o files (bytecode files) generated by llvm-gcc? Following is the sample output when I attempt to compile httpd with above mentioned setup. /bin/sh /httpd-2.0.55/srclib/apr/libtool --silent --mode=compile llvm-gcc -g -O2 -DHAVE_CONFIG_H -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I.....

On Nov 6, 2010, at 8:57 AM, Jan Sjodin wrote: > Hi Chris and Daniel, Hi Jan, These are good points! I'm cc'ing llvmdev, because this is pertinent to the larger community. > I was happy to be able to talk with both of you during the Dev Meeting. Today I > started to think a bit more about code reviews, LLVM and the future. From my > perspective the major thing that sets