search for: release1

> The 2.7 binaries are available for testing: > http://llvm.org/pre-releases/2.7/pre-release1/ Any plans for LLVM binaries and LLVM-GCC front-end binaries for MinGW32 similar to 2.6? Jon

...or regressions found in 2.7 and not for miscellaneous bug fixes. I will no longer be merging in patches that are not a regression as defined in our release process (http://llvm.org/docs/HowToReleaseLLVM.html#release-qualify). Here is the updated schedule: Mar 7 - Code Freeze (9PM PST) Mar 13 - Pre-release1 testing begins Mar 24 - Pre-release1 testing ends Mar 24 - Regression fixing week. Mar 31 - Regression fixing week ends. Apr 4 - Pre-release2 testing begins Apr 11 - Pre-release2 testing ends Apr 12 - Release! Thanks, Tanya -------------- next part -------------- An HTML attachment was scrubbed....

Just a reminder that 2.5 pre-release1 testing ends today (11:59PM PST). Please have your testing completed and the results sent to me. Thanks! -Tanya

Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in pre-release2, so please search the bug database bef...

On 2009-08-31 08:50, Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > Hi Tanya, Here are the results for x86_64 Linux (Debian unstable): > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will...

PS: Forgot to say that this was with objdir = srcdir for llvm; objdir != srcdir for llvm-gcc; languages c,c++,fortran.

Hi Tanya, I see the following warnings when building. I'm not sure how to fix any of them. The last one looks like it might be serious (seems like a job for Chris). llvm[1]: Compiling Path.cpp for Release build In file included from Path.cpp:270: Unix/Path.inc: In member function ‘bool llvm::sys::Path::eraseFromDisk(bool, std::string*) const’: Unix/Path.inc:661: warning: ignoring return

Hi, Were you able to get past this error: make[1]: Entering directory `/builddir/build/BUILD/llvm-2.5/lib/VMCore' llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td tblgen: IntrinsicEmitter.cpp:137: void EmitTypeForValueType(std::ostream&, llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"' failed. make[1]: Leaving directory

LLVMers, The 2.6 pre-release community testing period has ended. We are now going to focus on fixing the bugs found which are required before pre- release2 can be sent out. If anyone is able to help fix 2.6 bugs, please see the master 2.6 bug to find all bugs that need to be fixed: http://llvm.org/PR4886 Because of the number of bugs outstanding, we will be pushing back the release

Hi Tanya, On darwin9, the binaries in the darwin10 packages give: $ /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as --help dyld: unknown required load command 0x80000022 Trace/BPT trap That could be unavoidable, of course. Also, could you document what build mode the packages use (or release both Debug and Release-Asserts packages)? Since +Asserts and -Asserts have different ABIs, I'd have

Hm, I also note that: $ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64 Why's the i386 package have an x86_64 binary in it? That could explain why it doesn't work on darwin9. On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Hi Tanya, > > On darwin9, the

With Microsoft C++ (Windows Vista, 32-bit): LLVM 2.7 compiles (via cmake) without a hitch. I can't test it with my own code yet, will need to port from 2.6 to 2.7 first. I was going to try running Kaleidoscope as a test case, but it doesn't get built by default the way it did in 2.6, and running nmake in the Kaleidoscope directory performs no operation. Am I missing something here?

On 20 March 2010 16:42, Russell Wallace <russell.wallace at gmail.com> wrote: > With Microsoft C++ (Windows Vista, 32-bit): > > LLVM 2.7 compiles (via cmake) without a hitch. > > I can't test it with my own code yet, will need to port from 2.6 to 2.7 > first. > > I was going to try running Kaleidoscope as a test case, but it doesn't > get built by default

Ah, okay, thanks. Is the same true of Clang? On Sat, Mar 20, 2010 at 5:10 PM, Aaron Gray <aaronngray.lists at googlemail.com> wrote: > On 20 March 2010 16:42, Russell Wallace <russell.wallace at gmail.com> wrote: >> >> With Microsoft C++ (Windows Vista, 32-bit): >> >> LLVM 2.7 compiles (via cmake) without a hitch. >> >> I can't test it with

On Sat, Mar 20, 2010 at 7:54 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > It doesn't *recommend* running cmake in-source. It is just that the > instructions are written that way. When generating VS solution files, > building in-source is not a problem. It is when generating makefiles, as > the generated makefiles will overwrite those provided with LLVM's > sources.

Ah, thanks... curious, that set of instructions recommends running make in place (in the combined llvm directory), instead of in a separate directory as when building llvm without clang. Anyway, following those instructions (substituting unpacking the tar files for the svn checkout) gets me a .sln file (the resulting makefile doesn't work, but the .sln does), in which the build all command

Okay; it doesn't seem to build with cmake, though? C:\d\clang>\cmake-2.8.0-win32-x86\bin\cmake.exe c:\d\clang-2.7 -- Building for: NMake Makefiles -- The C compiler identification is MSVC -- The CXX compiler identification is MSVC -- Check for CL compiler version -- Check for CL compiler version - 1500 -- Check if this is a free VC compiler -- Check if this is a free VC compiler - no --

Hi, I would like to compare 2 lists resulted from a sql query! bu there are different levels, so when I want to do: release1<-sqlQuery(channel,paste("select distinct c.ID,c.Title TitleCrit from category cat, category_criteria cc, criteria c, question_criteria qc, question q, form_question fq, form f, release_form rf, release r, product_release pr, product p where cat.ID=cc.category and cc.criteria=c.ID and c.ID=q...

Russell Wallace <russell.wallace at gmail.com> writes: > Okay; it doesn't seem to build with cmake, though? > > C:\d\clang>\cmake-2.8.0-win32-x86\bin\cmake.exe c:\d\clang-2.7 > -- Building for: NMake Makefiles Follow the instructions for building clang: http://clang.llvm.org/get_started.html [snip]

On Sat, Mar 20, 2010 at 10:13 AM, Russell Wallace <russell.wallace at gmail.com> wrote: > Ah, okay, thanks. Is the same true of Clang? > Clang builds with MSVC, though to build something you have to have a 'gcc' in your path to build the assembly that is produced.