search for: buidbot

...ke anything. I even checked the buildbot > > and it looked like it failed before I ever applied anything. Apologies > > for the mix- up. > > FYI, if you want to check the encoding of an instruction, you can do so > with a command like this: Thanks. It's strange that the buidbot shows this test failing long before I made the change. Why would that be? In any event, I've got the problem fixed. It was a cut-n-paste oversight on my part. As for documentation, where should that go in LangRef.html? There's nothing there yet that really talks about special metadata...

On Feb 15, 2010, at 1:04 PM, David Greene wrote: >> FWIW, this is because you broke the encoding of an instruction in your >> patch. This is incorrect: >> >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, >> VR128:$src), + "movntdq\t{$src, $dst|$dst, $src}", >> + [(alignednontemporalstore

...the buildbot >>> and it looked like it failed before I ever applied anything. Apologies >>> for the mix- up. >> >> FYI, if you want to check the encoding of an instruction, you can do so >> with a command like this: > > Thanks. It's strange that the buidbot shows this test failing long before I > made the change. Why would that be? It didn't. Here's a good build: http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5019 The following two builds are broken by your previous bug: http://smooshlab.apple.com:8010/builders/clang...

Hal, On Thu, Apr 30, 2015 at 5:06 PM, Hal Finkel <hfinkel at anl.gov> wrote: > We need to get the build system integration committed and the buildbots > updated to compile it > If you are speaking on libiomp buidbots, they are already established: http://lab.llvm.org:8011/builders/libiomp5-clang-x86_64-linux-debian http://lab.llvm.org:8011/builders/libiomp5-gcc-x86_64-linux-debian Andrey -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-de...

...d it looked like it failed before I ever applied anything. Apologies > >>> for the mix- up. > >> > >> FYI, if you want to check the encoding of an instruction, you can do so > >> with a command like this: > > > > Thanks. It's strange that the buidbot shows this test failing long > > before I made the change. Why would that be? > > It didn't. Here's a good build: > http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/5019 Well, I can't get there, but... Oh. Buildbot is not displaying what I would exp...

...the buildbot >>> and it looked like it failed before I ever applied anything. Apologies >>> for the mix- up. >> >> FYI, if you want to check the encoding of an instruction, you can do so >> with a command like this: > > Thanks. It's strange that the buidbot shows this test failing long before I > made the change. Why would that be? > > In any event, I've got the problem fixed. It was a cut-n-paste oversight on > my part. > > As for documentation, where should that go in LangRef.html? There's > nothing there yet that...

All, I'd like to resurrect the discussion on replacing libgomp with libiomp as the default OpenMP runtime library linked with -fopenmp. For reference, the previous discussion is accessible there: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140217/thread.html#99461 We are very close to getting *full* OpenMP 3.1 specification supported in clang (only one (!) clause is not