similar to: [LLVMdev] Bitcode from build-self-4-mingw32

The buildbot build-self-4-mingw32 is failing with an assertion: Assertion failed: (isStackEmpty() && "Stack not empty at end of basic block?"), function processBasicBlock, file /Users/buildslave/zorg/buildbot/smooshlab/slave/build-self-4-mingw32/llvm.src/lib/Target/X86/X86FloatingPoint.cpp, line 305. Could anyone produce a bitcode file for that failure, please? --------------

Hi all, A question for the register allocation people: I'm currently trying to split intervals over loop boundaries. I have a situation where a floating point value is split over a loop boundary, and the register allocator choses to spill the value outside the loop. That leaves me with a floating point load in the loop preheader, which is crashing LLC with X86FloatingPoint.cpp:305:

Hello everyone, Zorg is a common code for multiple different buildbot setups. This is why it sits in its own subtree. The only tricky thing there is that it assumes some relative position of zorg and master setup. Documenting this would save somebody some time. All together wasn't a problem so far. But having a better documentation and a set of files for a simple local setup is a good idea.

Hi all, Our buildbot at: http://google1.osuosl.org:8011/ has been upgraded (it is also now linked from the front page). It has a number of handy new features: 1. I imported the 'console' view used by Chromium into our version of buildbot. You can see it here: http://google1.osuosl.org:8011/console This is experimental, but it seems to work well and once you learn to read it it is

Hi All, Recent conversations [1][2] would suggest we need to rethink zorg or at the very least improve the documentation. I've CC'ed Daniel Dunbar, Galina Kistanova and Duncan Sands because it seemed that they have contributed the most code to Zorg Organisation ========= The current organisation of the Zorg repository doesn't make a huge amount of sense from my perspective. There

Please use the correct link : http://63.145.236.72:8011 and ignore the previous. Also log for broken build is here: make[1]: Entering directory `/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build llvm[1]: Compiling APInt.cpp for Release+Asserts build In file included from APFloat.cpp:15: In file

I have tracked it down to the real reason. The revisions 139934-139937 has changed the order in which configure chooses a compiler. Clang is checked first, then llvm-gcc, and then gcc. I can see the reason for this change. However, in this particular case it has broken the build because Ubuntu includes clang 2.8 which doesn't know where includes are. I have removed clang from the host to

Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host? -eric On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote: > The host c++ standard library is missing <utility>, it appears. > > > On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > >> Please use the correct link : >>

The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >

On Mon, Jan 28, 2013 at 11:04 AM, <dag at cray.com> wrote: > We're thinking about running our own buildbot against the upstream llvm > and clang sources. I'm talking to our build folks and seeing what they > can allow. Maybe we can contribute some build slaves to the osuosl > buildbot but I'm not sure. > > If we do end up having to run our own buildbot,

On Thu, Jan 19, 2012 at 10:39 AM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > Alright.  We definitely don't want to model it as a general call, then.  Normal calls clobber lots of registers. > > The options are: > > 1. Use a pseudo-instruction that X86FloatingPoint understands and turns into a call after arranging for the argument to be in ST0. >   You should

On Jan 24, 2012, at 2:30 PM, Joe Groff wrote: > On Fri, Jan 20, 2012 at 2:10 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: >> X86FloatingPoint.cpp with comments is all you get. > > Thanks for your help, Jakob. Attached is a first-pass attempt at a > patch. I don't want to post to -commits yet because I have no idea if > this is fully correct, but it seems

Put it in the llvm/docs directory and link to the main documentation page? Maybe add a link the main buildbot page too. -Tanya On Oct 26, 2011, at 5:54 PM, Galina Kistanova wrote: > Hello everybody, > > I want to put some kind of instruction on how to add new slave to llvm master. > I think it should be somewhere on llvm.org, but not sure on exact place. > > Any

Hello everybody, I want to put some kind of instruction on how to add new slave to llvm master. I think it should be somewhere on llvm.org, but not sure on exact place. Any comments/suggestions will be appreciated. Thanks Galina If you want to add your build configuration to the LLVM buildbot infrastructure. 1. Check the existing build configurations to make sure the one you are

On Fri, Jan 20, 2012 at 2:10 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > X86FloatingPoint.cpp with comments is all you get. Thanks for your help, Jakob. Attached is a first-pass attempt at a patch. I don't want to post to -commits yet because I have no idea if this is fully correct, but it seems to work in simple test cases. Am I on the right track? Could this patch ever

On Jan 19, 2012, at 10:12 AM, Joe Groff wrote: > 2012/1/19 Jakob Stoklund Olesen <stoklund at 2pi.dk>: >> How many of these libcalls do you need to implement? What exactly is the calling convention? Which registers are clobbered etc. > > There is only one (that I know about so far). The MSVCRT `_ftol2` > function implements floating-point-to-unsigned conversion for i386

On Tue, Jan 24, 2012 at 4:32 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote: > Yes, your definition of the new instruction looks sane. > > However, you shouldn't expand the instruction right away in EmitInstrWithCustomInserter(), and leaving the pseudo and call instructions side by side is not going to work. > > Just leave the pseudo-instruction alone until it hits

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

We're thinking about running our own buildbot against the upstream llvm and clang sources. I'm talking to our build folks and seeing what they can allow. Maybe we can contribute some build slaves to the osuosl buildbot but I'm not sure. If we do end up having to run our own buildbot, what's the best way to integrate that into the upstream web page and status notifier? Basically,

Dear LLVM developers, My name is Gabor Ballabas. I work for the University of Szeged (Hungary) and we have an ongoing project with the goal of setting up and maintaining an LLVM buildbot for the ARMv8 - alias Aarch64 - architecture. Due to lack of existing hardware for this architecture we use ARM's Foundation Model to run the Aarch64 binaries. (See: