similar to: [LLVMdev] powerpc-darwin8 build/test status page

18.01.2012, 02:46, "David Fang" <fang at csl.cornell.edu>: > Hi, >          For anyone who might be interested, I've thrown together a little > page to track my builds of llvm and clang, both release 3.0 and > svn-trunk, on powerpc-darwin8. > > http://www.csl.cornell.edu/~fang/sw/llvm/ > > I'll update the list of logs each time I svn-update and

On Wed, Jan 18, 2012 at 10:51:38PM +0400, Konstantin Tokarev wrote: > > > 18.01.2012, 02:46, "David Fang" <fang at csl.cornell.edu>: > > Hi, > > ?????????For anyone who might be interested, I've thrown together a little > > page to track my builds of llvm and clang, both release 3.0 and > > svn-trunk, 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

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: >>

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. >>>

>> These results have far fewer failures than svn-trunk, and are also >> comparable to bootstrapping with gcc-4.6.2, summarized here: >> http://paste.lisp.org/display/126363 >> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >> This consistency between different bootstraps of the release gives me >> some hope that g++-4.0.1 is

On Fri, Dec 16, 2011 at 12:17:32PM -0500, David Fang wrote: >>> These results have far fewer failures than svn-trunk, and are also >>> comparable to bootstrapping with gcc-4.6.2, summarized here: >>> http://paste.lisp.org/display/126363 >>> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >>> This consistency between

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

Hi, > ----- Original Message ----- >>> ----- Original Message ----- >>>> Hi all, >>>> My recent commit r187027 fixed a simple oversight of forgetting >>>> to >>>> check for __ppc__ (only checking __powerpc__), which broke my >>>> powerpc-apple-darwin8 stage1 tests, since the system gcc only >>>> provided

> ----- Original Message ----- >> Hi all, >> My recent commit r187027 fixed a simple oversight of forgetting to >> check for __ppc__ (only checking __powerpc__), which broke my >> powerpc-apple-darwin8 stage1 tests, since the system gcc only >> provided >> __ppc__. I was wondering if this justifies using simpler macros like >> >> #define

Hi all, My recent commit r187027 fixed a simple oversight of forgetting to check for __ppc__ (only checking __powerpc__), which broke my powerpc-apple-darwin8 stage1 tests, since the system gcc only provided __ppc__. I was wondering if this justifies using simpler macros like #define LLVM_PPC (defined(__ppc__) || defined(__powerpc__) ...) #define LLVM_PPC64 (defined(__ppc64__) ||

----- Original Message ----- > > ----- Original Message ----- > >> Hi all, > >> My recent commit r187027 fixed a simple oversight of forgetting > >> to > >> check for __ppc__ (only checking __powerpc__), which broke my > >> powerpc-apple-darwin8 stage1 tests, since the system gcc only > >> provided > >> __ppc__. I was

Hi, I've been slowly but steadily working towards enabling the Mach-O/PPC backend for MC, starting with the mach-o relocation entry translation. patches/logs: http://www.csl.cornell.edu/~fang/sw/llvm/ git: http://github.com/fangism/llvm/tree/powerpc-darwin8 git: http://github.com/fangism/clang/tree/powerpc-darwin8 I've managed to get the simplest single-function-call hello-world

Hi, I havea minor suggestion for http://llvm.org/docs/TestingGuide.html: Under 'Requirements', might be worth mentioning that running the basic llvm/clang regression tests (check-all) requires a version of bash that supports pipefail, i.e. bash 3.0+. On older system where /bin/sh is too old, one simply needs to hack LitConfig.py to point to /somewhere/else/bash that meets this

----- Original Message ----- > Hi all, > My recent commit r187027 fixed a simple oversight of forgetting to > check for __ppc__ (only checking __powerpc__), which broke my > powerpc-apple-darwin8 stage1 tests, since the system gcc only > provided > __ppc__. I was wondering if this justifies using simpler macros like > > #define LLVM_PPC (defined(__ppc__) ||

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. If you have any questions or need something clarified, just email the list. For the 3.4.1 release we want to compare test results against 3.4-final. I have added support to the

Hi, Some time in the last few weeks I noticed my cmake build of svn-trunk on powerpc-darwin8 start to warn about atomics being unavailable and thus building thread-unsafe. I just looked into it and found an easy solution, using the atomic functions in <libkern/OSAtomic.h> in /usr/include. The attached patch does this and also modifies the cmake and autoconf tests to 'pass'

Hi Daniel, Thanks very much - I really appreciate you tracking this down. David - once Daniel's patch goes in it would be interesting to see what impact his work has had on PPC. I expect this will fix some of the tests there too. Regarding the AArch64 stub-addr return: My read is that createStubFunction returns a pointer to the start of the stub for AArch64. Those switch cases are a bit

LLVM Weekly - #1, Jan 6th 2014 ============================== Welcome to the inaugural issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. I've been a long time lurker on the LLVM and Clang mailing lists and have been using LLVM extensively in my PhD research for the past 4 years. I thought it might be worthwhile to

On Feb 3, 2015, at 1:40 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > >> On 2015 Feb 3, at 13:26, Chris Bieneman <beanz at apple.com> wrote: >> >> >>> On Feb 3, 2015, at 1:06 PM, Jonathan Roelofs <jroelofs.lists at gmail.com> wrote: >>> >>> >>> >>> On 2/3/15 12:08 PM, Chris Bieneman wrote: