search for: darwin10

...other failure. I just wanted to point this out so that people can take a look: -bw Here's the failure from our buildbot: Assertion failed: (DestReg == VirtReg && "Unknown load situation!"), function RewriteMBB, file /Volumes/Sandbox/Buildbot/llvm/build.llvm- gcc-x86_64-darwin10-selfhost/llvmCore.roots/llvmCore~obj/src/lib/ CodeGen/VirtRegRewriter.cpp, line 2294. /Volumes/Sandbox/Buildbot/llvm/build.llvm-gcc-x86_64-darwin10-selfhost/ llvmgcc42.roots/llvmgcc42~obj/obj-i686-i686/./gcc/xgcc -B/Volumes/ Sandbox/Buildbot/llvm/build.llvm-gcc-x86_64-darwin10-selfhost/ llvmgcc...

...ARGET_MACHO and not optimizing for size unless configured with --enable-frame-pointer. Enable -fasynchronous-unwind-tables unless configured with --enable-frame-pointer. Enable -maccumulate-outgoing-args by default unless configured with --enable-frame-pointer. After testing on x86_64-appled-darwin10 and i386-apple-darwin10, I had the same enabled on darwin releases which default to dwarf2 now in FSF gcc trunk using... --- trunk/gcc/configure.ac 2010/08/13 15:50:40 163226 +++ trunk/gcc/configure.ac 2010/08/13 17:06:42 163227 @@ -1584,8 +1584,9 @@ [ --enable-frame-pointer enable -fno-omit-fr...

...o get verbose linking output from fc... configure: WARNING: compilation failed checking for Fortran 77 libraries of fc... checking how to get verbose linking output from gcc -std=gnu99... -v checking for C libraries of gcc -std=gnu99... -lcrt1.10.6.o -L/usr/ local/lib -L/usr/lib/gcc/i686-apple-darwin10/4.2.1/x86_64 -L/usr/lib/ i686-apple-darwin10/4.2.1 -L/usr/lib/gcc/i686-apple-darwin10/4.2.1 -L/ usr/lib/gcc/i686-apple-darwin10/4.2.1/../../../i686-apple- darwin10/4.2.1 -L/usr/lib/gcc/i686-apple-darwin10/4.2.1/../../.. - lSystem checking for dummy main to link with Fortran 77 libraries... rm:...

Hello everybody, Just a short note that clang build "clang-x86_64-darwin10-self-mingw32" is broken and the very last successful was build #465 for revision 141282. All newer revisions fail. The builder is available here: http://63.145.236.72:8011/builders/clang-x86_64-darwin10-self-mingw32/builds/505 Thanks Galina

...l wrote: > > I think that it would be a good idea to have a buildbot set up to > > run the test suite with -vectorize. Could one of the existing > > machines do this also? > > It took some time, but we have this now: > > http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize > > The first run shows that there are a couple of test-suite failures > with the vectorizer: > > http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/108/steps/lnt.nightly-test/logs/tests.FAIL > > Hal, interested to take a look? If...

On Fri, Oct 7, 2011 at 3:21 PM, Galina Kistanova <gkistanova at gmail.com>wrote: > Hello everybody, > > Just a short note that clang build "clang-x86_64-darwin10-self-mingw32" is > broken and the very last successful was build #465 for revision 141282. > All newer revisions fail. > > The builder is available here: > > http://63.145.236.72:8011/builders/clang-x86_64-darwin10-self-mingw32/builds/505 This looks like Peter's work on...

Hi Daniel, > Sebastian, this looks like it is most likely some kind of fallout from > your changes. Thanks for letting me know about these failing testcases. In the logs of the buildbot: http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio I see that the bot is configuring llvm with: --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 --target=i686-pc-mingw32 Before my patches, specifying --target had no effect as it was the --host value that was...

...idea to have a buildbot set up to > >>> run the test suite with -vectorize. Could one of the existing > >>> machines do this also? > >> > >> It took some time, but we have this now: > >> > >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize > >> > >> The first run shows that there are a couple of test-suite failures > >> with the vectorizer: > >> > >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/108/steps/lnt.nightly-test/logs/tests.FAIL &gt...

On Fri, Apr 08, 2011 at 08:28:27AM +0200, Duncan Sands wrote: > Hi Jack, > > > The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn > > (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the > > build fails as... > > what does the command > ./TargetInfo -p > return (the TargetInfo program is created during the dragonegg build). > Some of your errors are consistent with this program failing to run. > Duncan, Yes, the result from &quot...

Hm, I also note that: $ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64 Why's the i386 package have an x86_64 binary in it? That could explain why it doesn't work on darwin9. On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Hi...

On Aug 16, 2010, at 7:59 AM, Jack Howarth wrote: > Despite the absence of testsuite failures at -m32 or -m64 on either > i386-apple-darwin10 or x86_64-apple-darwin10, there are still some concerns > about the origins of the original Mach-O comment above. There also was > a concern that -fomit-frame-pointer would break Shark but my testing in > darwin10 suggests it still can profile code via the dwarf2. Thanks in > advance fo...

The current dragonegg trunk svn used under FSF gcc 4.5.2 with llvm 2.9 is able to bootstrap FSF gcc 4.5.2 itself on x86_64-apple-darwin10... Using built-in specs. COLLECT_GCC=gcc-mp-4.5 COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin10/4.5.2/lto-wrapper Target: x86_64-apple-darwin10 Configured with: ../gcc-4.5.2/configure --prefix=/opt/local --build=x86_64-apple-darwin10 --enable-languages=c,c++,objc,obj-c++,fortran,j...

...wrote: > Hi Daniel, > >> Sebastian, this looks like it is most likely some kind of fallout from >> your changes. > > Thanks for letting me know about these failing testcases. > > In the logs of the buildbot: > http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio > I see that the bot is configuring llvm with: > --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 > --target=i686-pc-mingw32 > > Before my patches, specifying --target had no effect as it was th...

...;>> to run the test suite with -vectorize. Could one of the existing > >>>>> machines do this also? > >>>> > >>>> It took some time, but we have this now: > >>>> > >>>> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize > >>>> > >>>> The first run shows that there are a couple of test-suite > >>>> failures with the vectorizer: > >>>> > >>>> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/108/st...

...think that it would be a good idea to have a buildbot set up to >>> run the test suite with -vectorize. Could one of the existing >>> machines do this also? >> >> It took some time, but we have this now: >> >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize >> >> The first run shows that there are a couple of test-suite failures >> with the vectorizer: >> >> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize/builds/108/steps/lnt.nightly-test/logs/tests.FAIL >> >> Hal, inter...

...elease of gdb 7.0 (which will be required to debug optimized code generated by gcc 4.5 due changes related to the var tracking association merge and other code). They currently have patches proposed that allows gdb 7.0 to debug code in darwin9.6. However there was some change made in darwin9.8 and darwin10 which no longer allows the previous approach of making gdb belong to the procmod group... sudo chgrp procmod gdb sudo chmod g+s gdb Under darwin9.6 and darwin10 (but not darwin9.5), this results in the error... (gdb) break 4 Breakpoint 1 at 0x10000154c: file himenoBMTxpa.c, line 4. (gdb) r Start...

...ctorize. Could one of the > >>>>>>> existing machines do this also? > >>>>>> > >>>>>> It took some time, but we have this now: > >>>>>> > >>>>>> http://lab.llvm.org:8011/builders/clang-x86_64-darwin10-nt-O3-vectorize > >>>>>> > >>>>>> The first run shows that there are a couple of test-suite > >>>>>> failures with the vectorizer: > >>>>>> > >>>>>> http://lab.llvm.org:8011/builders/clang-x86_6...

On Mon, Aug 16, 2010 at 11:07:06AM -0700, Eric Christopher wrote: > > On Aug 16, 2010, at 7:59 AM, Jack Howarth wrote: > > > Despite the absence of testsuite failures at -m32 or -m64 on either > > i386-apple-darwin10 or x86_64-apple-darwin10, there are still some concerns > > about the origins of the original Mach-O comment above. There also was > > a concern that -fomit-frame-pointer would break Shark but my testing in > > darwin10 suggests it still can profile code via the dwarf2. Thanks in...

>> >> http://63.145.236.72:8011/builders/clang-x86_64-darwin10-self-mingw32/builds/505 > > This looks like Peter's work on clang-tblgen vs. llvm-tblgen.... Yes, exactly. It seems cross-builds were not updated to this new scheme -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Sat, Oct 08, 2011 at 12:32:54PM +0400, Anton Korobeynikov wrote: > >> > >> http://63.145.236.72:8011/builders/clang-x86_64-darwin10-self-mingw32/builds/505 > > > > This looks like Peter's work on clang-tblgen vs. llvm-tblgen.... > Yes, exactly. It seems cross-builds were not updated to this new scheme This is now fixed as of Clang r141453/LLVM r141454. Thanks, -- Peter