similar to: Setting up a silent buildslave

You don't really need to use the llvm builders infrastructure, just setup a local jenkins (or whatever) bot that triggers from the llvm svn, see http://stackoverflow.com/questions/10014252/jenkins-ci-how-to-trigger-builds-on-svn-commit 2016-05-27 22:26 GMT+03:00 Asiri Rathnayake via cfe-dev < cfe-dev at lists.llvm.org>: > Hi Galina, > > I would like to setup a silent

I was hoping to avoid the trouble of having to setup a master buildbot. But may be it's just easier to run Zorg as-is locally alongside the buildslave. I'll give that a go. Cheers, / Asiri On Fri, May 27, 2016 at 8:45 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You don't really need to use the llvm builders infrastructure, just setup > a local jenkins (or

Hi Asiri, You can use your local master for this or use silent master. Silent buildbot is currently copy of llvm buildbot, but does not sent any notifications. The both have the same set of builders and it's easy to switch a slave between them. To add slave/builder please add your slave and builder to zorg, but point your slave to silent master: use lab.llvm.org:9994 instead of

On 11 July 2016 at 17:06, Asiri Rathnayake <asiri.rathnayake at gmail.com> wrote: > Ignore me please, noted that you said it's the identical configuration with > just the library re-ordering. > > Shall I revert the link ordering until we have time to investigate? I can't see anything wrong in reverting the order, though. Maybe it's best, so we make sure it wasn't

On Tue, Dec 27, 2016 at 2:45 PM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake > <asiri.rathnayake at gmail.com> wrote: > > > > > > On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev > > <llvm-dev at lists.llvm.org> wrote: > >> > >> When I tried to build with

On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake <asiri.rathnayake at gmail.com> wrote: > > > On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that >> it doesn't try to use the in-tree libcxx but looks for one built >> and

I changed the library order in response to a review comment [1], but can't see how that's causing this failure. @Renato: can you check on that box if reverting the library order actually fixes the problem? Just to double check if that's indeed the cause. Thanks. / Asiri [1] http://reviews.llvm.org/D14293#inline-118681 On Mon, Jul 11, 2016 at 4:01 PM, Craig, Ben via llvm-dev <

> I find it amusing that you think that there's a "correct behavior" when the standard specifies > that an operation should throw an exception and you have disabled exceptions. You got me there! I think it's OK to be consistent across all the places and call abort(), this is what I've been doing in my current patch. I will double check this behavior with other

On Tue, Apr 25, 2017 at 1:37 PM, Asiri Rathnayake < asiri.rathnayake at gmail.com> wrote: > > > On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> >> wrote: >> > >> > well, top-of-branch lldb

Hi All, libcxx is fairly well designed to work in a no-exceptions environment, with most of the sources diligently using the _LIBCPP_NO_EXCEPTIONS macro. However, it seems to have bit-rotted a bit and could use some TLC right now. A no-exceptions variety of libcxx would be quite useful when you want to use all of libcxx goodness without the overhead of exceptions (especially in embedded

On Tue, Dec 27, 2016 at 1:29 PM, Carsten Mattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > When I tried to build with -DLLVM_ENABLE_LIBCXX, I found out that > it doesn't try to use the in-tree libcxx but looks for one built and > installed > in the system. > IIRC, -DLLVM_ENABLE_LIBCXX reduces to passing --stdlib=libc++ (see [1]) to the compiler. What you can

On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> > wrote: > > > > well, top-of-branch lldb uses this code, that's how I found it. Do you > mean libc++'s demangler? > > Thanks for explaining, this is the first time

Hi, I'm trying to generate some SPARCv8 assembly for a sparc target that doesn't have an FPU. I'm unable to get the flow to generate calls to a soft-float library. Since I wasn't able to find a definitive answer, I was hoping someone might be able to offer some pointers or shed some light. Running "clang -c -emit-llvm -msoft-float test.c -o test.bc" doesn't generate

The document here explains pretty well how to add a buildslave to the buildbot: http://llvm.org/docs/HowToAddABuilder.html However, it's not clear to me how to add a new build config. I would like to add a buildslave that builds with -Werror so we can catch and correct warnings early. How should I go about adding a new build configuration? Do I edit one of the .py files in zorg? Thanks!

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >> The document here explains pretty well how to add a buildslave to the >> buildbot: >> >> http://llvm.org/docs/HowToAddABuilder.html >> >> However, it's not clear to me how to add a new build config. I would >> like

Dmitri Gribenko <gribozavr at gmail.com> writes: > On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: >> Dmitri Gribenko <gribozavr at gmail.com> writes: >> >>> On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >>>> The document here explains pretty well how to add a buildslave to the >>>> buildbot:

On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: > Dmitri Gribenko <gribozavr at gmail.com> writes: > >> On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >>> The document here explains pretty well how to add a buildslave to the >>> buildbot: >>> >>> http://llvm.org/docs/HowToAddABuilder.html >>>

On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: > The document here explains pretty well how to add a buildslave to the > buildbot: > > http://llvm.org/docs/HowToAddABuilder.html > > However, it's not clear to me how to add a new build config. I would > like to add a buildslave that builds with -Werror so we can catch and > correct warnings

On Tue, Jan 15, 2013 at 8:24 PM, <dag at cray.com> wrote: > Dmitri Gribenko <gribozavr at gmail.com> writes: > >> On Tue, Jan 15, 2013 at 7:07 PM, <dag at cray.com> wrote: >>> Dmitri Gribenko <gribozavr at gmail.com> writes: >>> >>>> On Tue, Jan 15, 2013 at 2:43 AM, <greened at obbligato.org> wrote: >>>>> The

If you're willing to install libc++ you can easily work around this by running `ninja install-cxx install-cxxabi` before running any of the LLVM or Clang build targets. /Eric On Tue, Dec 27, 2016 at 7:45 AM, Carsten Mattner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, Dec 27, 2016 at 3:38 PM, Asiri Rathnayake > <asiri.rathnayake at gmail.com> wrote: >