Displaying 20 results from an estimated 9000 matches similar to: "[LLVMdev] LLVM 3.4.1 - Testing Phase"
2014 Apr 21
2
[LLVMdev] 3.4.1 Regression caused by merging r198940
On Thu, Apr 17, 2014 at 09:57:32AM -0400, Tom Stellard wrote:
> On Fri, Apr 11, 2014 at 03:02:21PM -0700, Tom Stellard wrote:
> > Hi,
> >
> > I have just tagged the first release candidate for the
> > 3.4.1 release, so testers may begin testing. Please refer to
> > http://llvm.org/docs/ReleaseProcess.html for information on how to
> > validate a release.
2014 May 18
4
[LLVMdev] LLVM 3.4.2 - Testing Phase
Hi Tom,
When running the test script, I got an error message:
$ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple
armv7a-linux-gnueabihf -j2
# Validating llvm SVN URL
llvm 3.4.2 release candidate rc1 doesn't exist!
Do I need to get another test-release.sh script? This is the one from
release_34 branch we used to release 3.4.1.
cheers,
--renato
On 16 May 2014 22:55, Tom Stellard
2011 Dec 16
3
[LLVMdev] llvm/clang test failures on powerpc-darwin8
Hi,
Thanks for the quick reply again.
> On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote:
>> Hi,
>>
>> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and
>> have the following test results to share.
>> Summary below, full log at:
>>
2014 Dec 12
9
[LLVMdev] 3.5.1 Testing Phase Begins
Hi,
3.5.1-rc1 has been tagged, so it is time to begin testing. We can
always use more testers, so if you would like to volunteer, let me
know.
For those that are new to testing, please review the documentation
for how validate a new release:
http://llvm.org/docs/ReleaseProcess.html
Remember that when we check for regressions we want to compare the
test results of 3.5.1-rc1 with 3.5.0-final.
2015 May 11
8
[LLVMdev] 3.6.1 -rc1 has been tagged. Testing begins.
Hi,
I have tagged the 3.6.1-rc1 so testing can begin. We can always use
more testers, so if you are interested in helping, let me know.
Instructions for validating an LLVM release can be found here:
http://llvm.org/docs/ReleaseProcess.html
Reminder: We are using 3.6.0 as our baseline for regression testing.
Thanks,
Tom
2011 Dec 15
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote:
> Hi,
>
> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and
> have the following test results to share.
> Summary below, full log at:
> http://www.csl.cornell.edu/~fang/sw/llvm/r146586-powerpc-darwin8-results.txt
>
> The only edits required were those I
2014 May 12
12
[LLVMdev] LLVM 3.4.2 Release Plan - Testers Needed
Hi,
I would like to begin the 3.4.2 release process for LLVM. There have
been two issues identified in 3.4.1, which there is interest in having
fixed in a 3.4.x release:
1. Build failure with gcc 4.9 (This is not a regression, 3.4 also fails
to build with gcc 4.9).
2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4
libLLVM-3.4.1.so
I will also accept any other bug-fixes that
2014 Apr 14
2
[LLVMdev] LLVM 3.4.1 - Testing Phase
On 04/14/2014 02:31 PM, Arnaud Allard de Grandmaison wrote:
> Hi All,
>
> As kindly pointed by Sebastian, please forget my point about the release
> script. I read the mail from Tom 2 days ago, and forgot that the script was
> available in the tag / branch when I acted today :(
>
> I uploaded clang+llvm-3.4.1-rc1-x86_64-unknown-ubuntu12.04.tar.xz to
> ftp.llvm.org.
>
2014 May 15
3
[LLVMdev] 3.4 branch gcc 4.9 build error
On Thu, 15 May 2014 02:25:30 +0200, Tom Stellard wrote:
> On Sat, May 10, 2014 at 11:48:23PM +0200, Tuncer Ayaz wrote:
> > Tom,
> >
> > now that 3.4.1 is out, any chance of a 3.4.2 with just the three
> > fixes or at least merging them to the 3.4 branch?
>
> I've pushed the two approved patches to the 3.4 branch, can you
> verify that they work with gcc
2011 Dec 15
2
[LLVMdev] llvm/clang test failures on powerpc-darwin8
Hi,
I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and
have the following test results to share.
Summary below, full log at:
http://www.csl.cornell.edu/~fang/sw/llvm/r146586-powerpc-darwin8-results.txt
The only edits required were those I posted to llvm-commits yesterday (re:
"some missing clang libs"). And I also edited LitConfig.py to point to
2013 Sep 12
1
[LLVMdev] LLVM 3.3.1 Release Plans
On Tue, Sep 10, 2013 at 09:02:58PM -0700, Tom Stellard wrote:
> On Fri, Aug 23, 2013 at 04:17:02PM -0700, Tom Stellard wrote:
> > Hi,
> >
> > The number of stable patches has slowed down in the last few weeks, and
> > we are approaching the halfway point between 3.3 and 3.4, so I think now
> > is a good time to start planning for the 3.3.1 release. Here is the
2014 May 15
2
[LLVMdev] 3.4 branch gcc 4.9 build error
On 15/05/2014 22:12, Tom Stellard wrote:
> On Thu, May 15, 2014 at 01:38:32PM +0200, Tuncer Ayaz wrote:
>> On Thu, 15 May 2014 02:25:30 +0200, Tom Stellard wrote:
>>
>>> On Sat, May 10, 2014 at 11:48:23PM +0200, Tuncer Ayaz wrote:
>>>> Tom,
>>>>
>>>> now that 3.4.1 is out, any chance of a 3.4.2 with just the three
>>>> fixes
2014 Jun 12
2
[LLVMdev] problems to recompile LLVM version 3.4.1 with gcc48 / SuSE 13.1
On Thu, Jun 12, 2014 at 10:57:46AM +0200, Armin Steinhoff wrote:
>
> Hi,
>
> first problem was:
>
> >FileManager.cpp:311:21: error: range-based for loops are not allowed
> >in C++98 mode
> >for (auto & fe: SeenFileEntries) {
> >^
> >FileManager.cpp:312:14: error: request for member getValue in fe,
> >which is of non-class type int
2014 Jan 13
10
[LLVMdev] LLVM 3.4 stable releases
Hi,
I would like to try again to do stable releases for LLVM 3.4.
Even though we were unsuccessful with stable releases for LLVM
3.3, I learned some things going through the process, which I think
will increase the chance for success with LLVM 3.4.
So, here is my TODO list for a successful 3.4.1 release:
1. Get volunteers to help
This is probably the most important thing on this list. Stable
2014 Apr 08
2
[LLVMdev] 3.4.1 Release Plans
On Tue, Apr 08, 2014 at 04:08:13PM +0400, Robert Khasanov wrote:
> Hi Reid,
>
> Would you approve your patches r203146 and r202774 to be backported to
> 3.4.1? They fix stability issues in x86 asm.
>
Hi Robert,
I was able to merge r203146, but it used a c++11 feature:
std::string::back() which I replaced with
std::string::at(std::string::size() - 1).
r202774 was not merged,
2014 May 12
2
[LLVMdev] Point Releases - tags
On 12 May 2014 10:29, "C. Bergström" <cbergstrom at pathscale.com> wrote:
> I suspect 3.4.1 is based off
> https://github.com/llvm-mirror/clang/tree/release_34
>
> (llvm probably has something similar I suppose?)
This is correct. Though, I don't know if anyone tagged 3.4.1 on that
branch, but I suspect what was released is the HEAD of that branch.
Tom would know
2013 Sep 11
0
[LLVMdev] LLVM 3.3.1 Release Plans
On Fri, Aug 23, 2013 at 04:17:02PM -0700, Tom Stellard wrote:
> Hi,
>
> The number of stable patches has slowed down in the last few weeks, and
> we are approaching the halfway point between 3.3 and 3.4, so I think now
> is a good time to start planning for the 3.3.1 release. Here is the
> tentative schedule:
>
> September 3: 3.3.1-rc1
> - This won't actually be
2013 Aug 23
2
[LLVMdev] LLVM 3.3.1 Release Plans
Hi,
The number of stable patches has slowed down in the last few weeks, and
we are approaching the halfway point between 3.3 and 3.4, so I think now
is a good time to start planning for the 3.3.1 release. Here is the
tentative schedule:
September 3: 3.3.1-rc1
- This won't actually be a 'real' Release Candidate. The purpose of
rc1 will be to update and test the release scripts
2011 Dec 16
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
On Fri, Dec 16, 2011 at 01:51:57AM -0500, David Fang wrote:
> Hi,
> Thanks for the quick reply again.
>
>> On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote:
>>> Hi,
>>>
>>> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and
>>> have the following test results to share.
>>>
2014 Apr 27
2
[LLVMdev] LLVM 3.4.1 Testing Phase Part 2
No regressions this time. Fedora and OpenSUSE binaries uploaded.
On Sat, Apr 26, 2014 at 12:47 PM, Tom Stellard <tom at stellard.net> wrote:
> Dropping llvmdev and cc'ing testers directly, so this email
> won't be held in moderation for having too many recipients.
>
> I like having tester discussions on list, so it would probably
> be best to reply to the original