Displaying 20 results from an estimated 70000 matches similar to: "[LLVMdev] 2.5 Pre-release1 available for testing"
2010 Apr 05
0
[LLVMdev] [cfe-dev] 2.7 Pre-release1 available for testing
On 03/30/2010 09:21 PM, Török Edwin wrote:
> On 03/30/2010 09:15 PM, Tanya Lattner wrote:
>> Thanks for testing the release!
>>
>>> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3,
>>> 64-bit. I built srcdir == objdir, I have built llvm and clang myself,
>>> and used the binaries for llvm-gcc.
>>>
>>> 1. llvm-gcc 2.7 vs
2009 Sep 05
0
[LLVMdev] 2.6 pre-release1 ready for testing
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 be
> fixed in
2010 Mar 30
2
[LLVMdev] [cfe-dev] 2.7 Pre-release1 available for testing
On 03/30/2010 09:15 PM, Tanya Lattner wrote:
>
> Thanks for testing the release!
>
>> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3,
>> 64-bit. I built srcdir == objdir, I have built llvm and clang myself,
>> and used the binaries for llvm-gcc.
>>
>> 1. llvm-gcc 2.7 vs 2.6
>> compared to my results from Aug 31 2009, ignoring CBE
2010 Mar 30
0
[LLVMdev] [cfe-dev] 2.7 Pre-release1 available for testing
On Mar 24, 2010, at 2:47 PM, Török Edwin wrote:
> On 03/17/2010 10:12 PM, Tanya Lattner wrote:
>> The 2.7 binaries are available for testing:
>> http://llvm.org/pre-releases/2.7/pre-release1/
>>
>> You will also find the source tarballs there as well.
>>
>> We rely on the community to help make our releases great, so please help
>> test 2.7 if you
2009 Sep 03
0
[LLVMdev] 2.6 pre-release1 ready for testing
On Thu, Sep 3, 2009 at 6:24 AM, Olivier
Meurant<meurant.olivier at gmail.com> wrote:
> Hi Tanya,
>
> I have tried the 2.6 pre-release on the following host :
>
> Windows XP pro SP2 with mingw/msys :
>
> uname -a
> MINGW32_NT-5.1 OLIVE 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown
>
> gcc -v
> Reading specs from d:/mingw/bin/../lib/gcc/mingw32/3.4.5/specs
2010 Mar 24
1
[LLVMdev] [cfe-dev] 2.7 Pre-release1 available for testing
On 03/17/2010 10:12 PM, Tanya Lattner wrote:
> The 2.7 binaries are available for testing:
> http://llvm.org/pre-releases/2.7/pre-release1/
>
> You will also find the source tarballs there as well.
>
> We rely on the community to help make our releases great, so please help
> test 2.7 if you can. Please follow these instructions to test 2.7:
>
> /To test llvm-gcc:/
2009 Feb 09
0
[LLVMdev] 2.5 Pre-release1 available for testing
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
2009 Sep 03
2
[LLVMdev] 2.6 pre-release1 ready for testing
Hi Tanya,
I have tried the 2.6 pre-release on the following host :
Windows XP pro SP2 with mingw/msys :
uname -a
MINGW32_NT-5.1 OLIVE 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown
gcc -v
Reading specs from d:/mingw/bin/../lib/gcc/mingw32/3.4.5/specs
Configured with: ../gcc-3.4.5/configure --with-gcc --with-gnu-ld
--with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw
--enable-threads
2009 Feb 07
0
[LLVMdev] 2.5 Pre-release1 available for testing
I'm trying to build the 2.5 prerelease on my MacBook, and I'm getting
a bus error in tblgen:
$ rm -r * && ../src/configure --prefix=`pwd`/../install && make -j1
VERBOSE=1 ENABLE_OPTIMIZED=0
...
llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td
/Users/jyasskin/src/llvm-2.5/obj/Debug/bin/tblgen -I
/Users/jyasskin/src/llvm-2.5/src/lib/VMCore -I
2009 Apr 07
0
[LLVMdev] 2.5 Pre-release1 available for testing
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
2009 Mar 10
1
[LLVMdev] 2.5 Pre-release1 available for testing
Michel Salim wrote:
> On Fri, Feb 6, 2009 at 8:42 PM, Tanya Lattner <tonic at nondot.org> wrote:
>> LLVMers,
>>
>> The 2.5 pre-release is available for testing:
>> http://llvm.org/prereleases/2.5/
>>
> I'm updating the Fedora packaging of LLVM, and with the 02/20
> prerelease it fails to build on ppc64:
>
>
2009 Feb 23
0
[LLVMdev] 2.5 Pre-release1 available for testing
On Fri, Feb 6, 2009 at 8:42 PM, Tanya Lattner <tonic at nondot.org> wrote:
> LLVMers,
>
> The 2.5 pre-release is available for testing:
> http://llvm.org/prereleases/2.5/
>
I'm updating the Fedora packaging of LLVM, and with the 02/20
prerelease it fails to build on ppc64:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1148023
make[1]: Entering directory
2010 Mar 17
9
[LLVMdev] 2.7 Pre-release1 available for testing
The 2.7 binaries are available for testing:
http://llvm.org/pre-releases/2.7/pre-release1/
You will also find the source tarballs there as well.
We rely on the community to help make our releases great, so please help test 2.7 if you can. Please follow these instructions to test 2.7:
To test llvm-gcc:
1) Compile llvm from source and untar the llvm-test in the projects
directory (name it
2009 Aug 31
10
[LLVMdev] 2.6 pre-release1 ready for testing
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 before filing
a new bug.
If you have time, I'd appreciate anyone who can help test the
2009 Aug 31
0
[LLVMdev] 2.6 pre-release1 ready for testing
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 before filing
> a new bug.
>
>
2006 Apr 19
3
[LLVMdev] 1.7 Pre-Release Ready for Testing
On 4/19/06, Patrick Meredith <pmeredit at uiuc.edu> wrote:
> I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test it out.
> Missed the 18th,but I'll try to have it done asap.
>
>
> On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote:
> I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir.
>
> Rob
>
Sorry for being
2006 Apr 19
0
[LLVMdev] 1.7 Pre-Release Ready for Testing
I haven't seen anyone claim x86 linux objdir == srcdir, so I'll test
it out. Missed the 18th,but I'll try to have it done asap.
On Apr 18, 2006, at 2:51 PM, Robert L. Bocchino Jr. wrote:
> I'll test on Darwin/PPC, precompiled llvmgcc, objdir == srcdir.
>
> Rob
>
> On Apr 16, 2006, at 1:42 PM, Chris Lattner wrote:
>
>> On Sun, 16 Apr 2006, Tanya Lattner
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
On Mon, Sep 17, 2007 at 12:25:40PM -0700, Chris Lattner wrote:
> On Mon, 17 Sep 2007, Emil Mikulic wrote:
> >> The 2.1 pre-release (version 1) is available for testing:
> >> http://llvm.org/prereleases/2.1/version1/
> >
> > I suspect the utils/TableGen/FileParser.h.cvs in the tarball may be
> > stale. I tried building LLVM without bison installed and got:
2009 Feb 12
0
[LLVMdev] Reminder: 2.5 pre-release1 testing ends today!
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
2009 Feb 09
0
[LLVMdev] LLVM Release Criteria
Hello,
I'd like to clarify a few points on how the release process works.
Each release must satisfy the following criteria for each supported
target:
* LLVM-GCC & LLVM must build in both release and debug mode. They must
also build srcDir != objDir. LLVM-GCC must build with support for c, c++,
fortran, and obj-c/obj-c++ (Mac only).
* LLVM-GCC must bootstrap.
* "make check"