Displaying 20 results from an estimated 9000 matches similar to: "[LLVMdev] Reminder: LLVM 3.0 Branching Friday!"
2011 Oct 14
0
[LLVMdev] Reminder: LLVM 3.0 Branching Friday!
Hi Bill,
> As of this writing, we have:
>
> • several test failures on llvm-gcc self-host:
>
> http://lab.llvm.org:8011/builders/llvm-gcc-i386-linux-selfhost/builds/25
I can reproduce this here. I'll poke at it this weekend sometime.
> • a miscompile in one of the llvm-gcc testers:
>
> http://lab.llvm.org:8011/builders/llvm-x86_64-linux-checks/builds/55
>
>
2011 Oct 14
0
[LLVMdev] Reminder: LLVM 3.0 Branching Friday!
Bill Wendling <wendling at apple.com> writes:
> This is just a reminder to say that we will be branching for the LLVM 3.0 release Friday!
>
> 07:00:00 p.m. Friday October 14, 2011 PDT
> 02:00:00 a.m. Saturday October 15, 2011 GMT
Hi Bill,
I have some pending patches for 3.0 only. Will you be sending out an
announcement when the split is finished and such patches can be
2011 Oct 14
2
[LLVMdev] [cfe-dev] Reminder: LLVM 3.0 Branching Friday!
greened at obbligato.org (David A. Greene) writes:
> I have some pending patches for 3.0 only.
Of course I meant post-3.0 only.
-Dave
2011 Oct 14
0
[LLVMdev] [cfe-dev] Reminder: LLVM 3.0 Branching Friday!
On Oct 14, 2011, at 12:54 PM, David A. Greene wrote:
> greened at obbligato.org (David A. Greene) writes:
>
>> I have some pending patches for 3.0 only.
>
> Of course I meant post-3.0 only.
>
Yes, I'll send out a message when it's okay to submit post-3.0 patches.
-bw
2019 Sep 01
4
PowerPC Compiler Crash
http://lab.llvm.org:8011/builders/clang-ppc64be-linux/builds/37730/ is
an example of the ICE when D64146/rL370584 landed.
On 01/09/2019 02:23, Florian Hahn via llvm-dev wrote:
> Hi,
>
>> On Aug 31, 2019, at 15:14, Nandor Licker via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> Hello PowerPC fans,
>>
>> I am attempting to land D64146 and the PowerPC
2016 Jun 28
2
SVN almost dead, bots crazy
Hi,
Anyone knows what's going on with SVN?
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15
http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost-neon
http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh
etc.
svn: E175012: Connection
2015 Mar 04
3
[LLVMdev] Self-hosting failure in ARM again
Folks,
It seems we got the same issue with Clang alignment as before:
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost/builds/3025
http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-selfhost-neon/builds/485
http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh/builds/118
Commits between 231213 and 231255.
There are a few issues that could have brought it:
*
2016 Oct 31
2
[Zorg] Simplify ClangBuilder
Hi Richard, Marco,
I noticed that you two are the remaining bot owners using the
`getClangBuildFactory` from `ClangBuilder`. All the other bots using
that builder have moved to the new `getClangCMakeBuildFactory`,
including Windows ones.
Given that they do similar functionalities, I'd like to encourage you
to move to the new factory, so that we can simplify the builder's
code.
Thanks!
2011 Oct 13
1
[LLVMdev] Your commit 139841
Hi Andrew, it looks like your commit
r139842 | atrick | 2011-09-15 22:58:37 +0200 (Thu, 15 Sep 2011) | 2 lines
Reapply r139759. Disable IV rewriting by default. See PR10916.
broke this buildbot:
http://lab.llvm.org:8011/builders/llvm-x86_64-linux-checks
The failure is a bootstrap failure of llvm-gcc when comparing object files
from stages 2 and 3 (which don't match).
I was able
2016 Jun 12
2
clang-ppc64be-linux-lnt flakiness
I threw all the sanitizers I had access to on this test and didn't
find anything. The merging uses threads so I can't rule out
nondeterminism. It's strange that it only happens on ppc64le and only
on stage 2, so an actual miscompile wouldn't surprise me either.
On Sun, Jun 12, 2016 at 4:26 PM, Sean Silva <chisophugis at gmail.com> wrote:
> Also, `Clang Tools ::
2019 Sep 01
2
PowerPC Compiler Crash
-- The C compiler identification is GNU 7.3.1
-- The CXX compiler identification is GNU 7.3.1
According to buildbot log here
http://lab.llvm.org:8011/builders/clang-ppc64be-linux/builds/37730/steps/cmake%20stage%201/logs/stdio
for Simon's example ICE.
Best,
Jinsong Ji (纪金松), PhD.
XL/LLVM on Power Compiler Development
E-mail: jji at us.ibm.com
From: "Finkel, Hal J. via
2016 Jun 29
2
clang-ppc64be-linux-lnt flakiness
This just failed again:
http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/1579
Bill, could you take a look at this? This is like the 3rd time I've been
incorrectly pinged by this buildbot due to this issue.
-- Sean Silva
On Mon, Jun 13, 2016 at 8:07 PM, Sean Silva <chisophugis at gmail.com> wrote:
> Thanks for taking a look. The flaky ASan test failure in the
2011 Oct 25
0
[LLVMdev] Dragonegg and llvm-gcc self-host broken by miscompile of llvm-tblgen
These self-host builders all just starting failing. It looks like tablegen is
being miscompiled.
The first failed builds:
(1) http://lab.llvm.org:8011/builders/llvm-gcc-i386-linux-selfhost/builds/208
(2) http://lab.llvm.org:8011/builders/dragonegg-i386-linux/builds/194
(3) http://lab.llvm.org:8011/builders/dragonegg-x86_64-linux/builds/197
The odd thing is that I can't see any suspicious
2016 Jun 14
0
clang-ppc64be-linux-lnt flakiness
Thanks for taking a look. The flaky ASan test failure in the OP was stage1
so it sounds like there may be multiple problems :(
-- Sean Silva
On Sun, Jun 12, 2016 at 7:32 AM, Benjamin Kramer <benny.kra at gmail.com>
wrote:
> I threw all the sanitizers I had access to on this test and didn't
> find anything. The merging uses threads so I can't rule out
> nondeterminism.
2016 Jun 28
0
SVN almost dead, bots crazy
Dear Renato,
Are you still getting the error? I quick spot check on the server shows
that most processes are idle and there's 0.5 GB of RAM left. Nothing is
jumping out at me as clearly bad (though I am potentially overlooking
something).
Regards,
John Criswell
On 6/28/16 10:39 AM, Renato Golin via llvm-dev wrote:
> Hi,
>
> Anyone knows what's going on with SVN?
>
>
2016 Jun 29
1
clang-ppc64be-linux-lnt flakiness
I looked at this a bit a while back when you first asked but I didn't
see anything obviously wrong.
Benjamin, at least one of the referenced failures was on BE powerpc64.
I don't remember if that one
(http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883)
failed on stage 1 or 2 and the results pages are no longer available.
BTW, I tried testing the same revision many
2011 Feb 28
1
[LLVMdev] [cfe-dev] Reminder: LLVM 2.9 Branching in One Week
Hi Bill,
Will the 2.9 branch be reflected in the git mirrors?
Thanks,
Chad
On Sun, Feb 27, 2011 at 5:43 PM, Bill Wendling <wendling at apple.com> wrote:
> This is a reminder that we will be branching for LLVM 2.9 in one week!
> 07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011
> GMT
> What this means for you:
> Please keep a watch on all of your
2016 Jun 12
2
clang-ppc64be-linux-lnt flakiness
Hi Bill, just a heads up but this bot seems to have spuriously failed on a
build that only pulled in my commit r272505 which is unrelated.
http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/4883
-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160612/8b2c4493/attachment.html>
2015 May 19
5
[LLVMdev] [cfe-dev] LLVM IRC channel flooded?
On Tue, May 19, 2015 at 10:40 AM, James Y Knight <jyknight at google.com>
wrote:
> Yes, I also find the amount of bot spam in #llvm is basically intolerable.
> It makes it difficult to see actual people talking. At first, I just put
> all the bots on /ignore. Now I have an xchat script to move the botspam to
> another tab (tabify-004.pl). I'd recommend that the bots should
2011 Feb 28
3
[LLVMdev] Reminder: LLVM 2.9 Branching in One Week
This is a reminder that we will be branching for LLVM 2.9 in one week!
07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011 GMT
What this means for you:
Please keep a watch on all of your patches going into mainline. And pay close attention to the buildbots and fix any issues quickly.
Also, please try to finish up any last minute feature work. While it won't be the