similar to: [LLVMdev] uninitialized value warnings: LLVMParser.cpp

On cygwin-1.7, clang and llvm can be built fine through 3 stages. With --disable-assertions (RC3's default), I saw a few warnings in llvm/lib/AsmParser/LLParser.cpp with g++-4.3.4. (and two warnings, PR9515) ...Takumi $ uname.exe -a CYGWIN_NT-6.1-WOW64 HEAVEN64 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin $ gcc --version gcc (GCC) 4.3.4 20090804 (release) 1 * Stage 1 configured by

Hi, I got a problem when I am trying to add a dummy basic block. Let say there are two blocks, A and B. A----->B I am trying to generate new BB called C which is located between A and B, but not break the edge of AB. The graph is like the following A---->B \ / \ / C There is new BB 'C' with edges AC and CB. It is kind of like what breakcriticaledge pass does.

On Thu, Feb 12, 2009 at 4:47 AM, Ted Kremenek <kremenek at apple.com> wrote: > On Feb 11, 2009, at 8:14 PM, Ben Laurie wrote: > >> On Wed, Feb 11, 2009 at 8:24 PM, Ted Kremenek <kremenek at apple.com> wrote: >>> >>> Actually, neither of these methods are needed for ImmutableSet. >>> ImmutableSet already has an 'isEmpty()' method and I have

On Wed, Feb 11, 2009 at 8:24 PM, Ted Kremenek <kremenek at apple.com> wrote: > Actually, neither of these methods are needed for ImmutableSet. > ImmutableSet already has an 'isEmpty()' method and I have never really seen > a case where "size()" needs to be explicitly calculated. If you need size() > itself, however, this seems like a perfectly valid addition.

I am at revision 45341, and I am getting a build failure on Leopard involving an unknown option to the ocaml compiler: llvm[3]: Compiling optimized llvm.ml for Debug build /opt/fink/bin/ocamlopt: unknown option `-g'. Usage: ocamlopt <options> <files> ... My ocaml binaries are compiled from source using fink: (kremenek at tedbook:llvm)$ which ocamlopt /opt/fink/bin/ocamlopt

On Feb 11, 2009, at 8:14 PM, Ben Laurie wrote: > On Wed, Feb 11, 2009 at 8:24 PM, Ted Kremenek <kremenek at apple.com> > wrote: >> Actually, neither of these methods are needed for ImmutableSet. >> ImmutableSet already has an 'isEmpty()' method and I have never >> really seen >> a case where "size()" needs to be explicitly calculated. If

Hi Chris, llvm.org/perf gives again error 500s. I remember you had a look the last time. Would you mind looking again? Also, is there something which we could do to make LNT more robust. Do you have an idea what the last issue was about? Thanks, Tobias -------- Original Message -------- Subject: buildbot failure in LLVM on polly-perf-O3-polly-scev-codegen-isl Date: Fri, 21 Feb 2014 17:08:44

DOn 2007-12-24, at 01:29, Ted Kremenek wrote: > I am at revision 45341, and I am getting a build failure on Leopard > involving an unknown option to the ocaml compiler: > > llvm[3]: Compiling optimized llvm.ml for Debug build > /opt/fink/bin/ocamlopt: unknown option `-g'. > Usage: ocamlopt <options> <files> > ... > > > My ocaml binaries are compiled

If you look at an .sln file, there's a long sequence of digits associated with every project, something like this 8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942. For the lack of a better word I called it "encoding". After I changed the dependencies between projects in the solution, msvs replaced those numeric sequences by new ones literally for every project in the solution file. The diff now

I am not certain, but I know one person to ask. I sent them an email off list and will follow up shortly. > On Aug 18, 2015, at 7:32 AM, deus ex <deusex12345678 at gmail.com> wrote: > > Hello, > > someone has an idea where I could get the other .svg LLVM Logo derivates? That would be great :) > > Thanks in advance. > > greetings, > > dex > >

Hi Dmitri, I know what you are saying, but in the end I think we are lucky if diffs against project files have any meaningful information. Nobody right now assumes responsibility for regularly updating the VS files, so we routinely get patches from different people when they decide to upgrade the project files, and these patches change the .sln files in arbitrary ways. If you have

Thank you very much, this one I found I meant the other logos. Unfortunately there is no link to the other logos .svg or .ai format. Do you have a clue or how I could contact the creator of this logo? Thanks again for your patience. greetings, dex 2015-08-15 0:27 GMT+02:00 Ted Kremenek <kremenek at apple.com>: > There is a link to the Adobe Illustrator Version at the bottom of the

On Jun 10, 2014, at 5:36 PM, C. Bergström <cbergstrom at pathscale.com> wrote: > On 06/11/14 06:58 AM, Ted Kremenek wrote: >> ** NOTE: This is a compiler job announcement. ** >> >> The Apple Source Languages team is looking for exceptional engineers to work on the Swift programming language: > Maybe this has been asked already and I missed it - Will Swift be open

Ted, Thanks for taking care of this. I found that in order to build clang (in addition to the vcproj changes I posted earlier today) I had to add a dependency such that the clangDriver project depends on the CodeGen (basically the CodeGen checkbox has to be checked in the list of the clangDriver's dependencies). This in effect adds codegen.lib to the list of libraries linked into clang.exe

Actually, neither of these methods are needed for ImmutableSet. ImmutableSet already has an 'isEmpty()' method and I have never really seen a case where "size()" needs to be explicitly calculated. If you need size() itself, however, this seems like a perfectly valid addition. On Feb 11, 2009, at 10:57 AM, Ted Kremenek wrote: > > On Feb 11, 2009, at 10:54 AM, Bill

On Wednesday 10 February 2010 14:58:58 Dan Gohman wrote: > On Feb 10, 2010, at 12:42 PM, David Greene wrote: > > On Wednesday 10 February 2010 12:58:25 Chris Lattner wrote: > >> I think that adding a bit to LoadSDNode and StoreSDNode would make > >> sense. > > > > Ok. The consequence is that a number of functions will have to change to > > propagate

On Feb 10, 2010, at 12:42 PM, David Greene wrote: > On Wednesday 10 February 2010 12:58:25 Chris Lattner wrote: > >> I think that adding a bit to LoadSDNode and StoreSDNode would make sense. > > Ok. The consequence is that a number of functions will have to change to > propagate this bit, analogous to what happens with isVolatile. It's > essentially what we do

On Thursday 11 February 2010 13:31:58 David Greene wrote: > > Putting a bit (or multiple bits) in MachineMemOperand for this > > would also make sense. > > Is there any chance a MachineMemOperand will be shared by multiple > instructions? So I tried to do this: %r8 = load <2 x double>* %r6, align 16, !"nontemporal" and the assembler doesn't like it.

Hi, Well, yes i did try your suggestion but i keep on running into a compilation problem. The error is: llvm[0]: Compiling Hello.cpp for Release build (PIC) /home/saraswat/llvm/llvm-2.1/include/llvm/ADT/GraphTraits.h: In instantiation of `llvm::GraphTraits<llvm::ilist_iterator<llvm::BasicBlock> >': Hello.cpp:59: instantiated from here

Dear Ted and All, Thanks. This has helped some. However, I'm now getting errors from libtool about an object being modified after free. Is libtool supposed to work with LLVM bitcode files? If so, would grabbing the latest source potentially fix the problem (I'm currently using XCode 3.1), or will I need a way to convince xcodebuild to use something other than libtool? -- John T.