similar to: [LLVMdev] -fomit-frame-pointer on intel darwin

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

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

Hi all, There's been a recent bootstrap failure that might be covered up because of another 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-

On Tue, 12 Jun 2012 11:15:12 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 02/05/2012 02:42 PM, Hal Finkel 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: > >

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

On Thu, 21 Jun 2012 01:03:46 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/20/2012 11:07 PM, Hal Finkel wrote: > > On Tue, 12 Jun 2012 11:15:12 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 02/05/2012 02:42 PM, Hal Finkel wrote: > >>> I think that it would be a good idea to have a buildbot set up to >

I hope this is the place for this... I have to rebuild from scratch under Snow Leopard, and when I attempted to build R-2.9.1, I get the following results from ./ configure: checking how to 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

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? Thanks again, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory

On Sun, 24 Jun 2012 08:17:32 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/24/2012 05:42 AM, Hal Finkel wrote: > > On Thu, 21 Jun 2012 16:25:13 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 06/21/2012 04:23 PM, Hal Finkel wrote: > >>> On Thu, 21 Jun 2012 01:03:46 +0200 > >>> Tobias

On Thu, 21 Jun 2012 16:25:13 +0200 Tobias Grosser <tobias at grosser.es> wrote: > On 06/21/2012 04:23 PM, Hal Finkel wrote: > > On Thu, 21 Jun 2012 01:03:46 +0200 > > Tobias Grosser<tobias at grosser.es> wrote: > > > >> On 06/20/2012 11:07 PM, Hal Finkel wrote: > >>> On Tue, 12 Jun 2012 11:15:12 +0200 > >>> Tobias

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:

On 02/05/2012 02:42 PM, Hal Finkel 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

Does anyone know what I should be doing if I want to cross compile LLVM for the ARM architecture? I want to use the LLVM JIT on ARM for a class project this semester. I have built and/or installed a few different gcc arm (arm-linux, and also one that is arm-elf) toolchains, and have had trouble getting LLVM 2.6 to configure and compile using the --host and --build switches of the config. If there

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 Tanya, > > On darwin9, the

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

On 06/24/2012 02:42 PM, Hal Finkel wrote: > On Sun, 24 Jun 2012 08:17:32 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 06/24/2012 05:42 AM, Hal Finkel wrote: >>> On Thu, 21 Jun 2012 16:25:13 +0200 >>> Tobias Grosser<tobias at grosser.es> wrote: >>> >>>> On 06/21/2012 04:23 PM, Hal Finkel wrote: >>>>>

On 06/20/2012 11:07 PM, Hal Finkel wrote: > On Tue, 12 Jun 2012 11:15:12 +0200 > Tobias Grosser<tobias at grosser.es> wrote: > >> On 02/05/2012 02:42 PM, Hal Finkel 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? >>

Hi Tanya, On darwin9, the binaries in the darwin10 packages give: $ /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as --help dyld: unknown required load command 0x80000022 Trace/BPT trap That could be unavoidable, of course. Also, could you document what build mode the packages use (or release both Debug and Release-Asserts packages)? Since +Asserts and -Asserts have different ABIs, I'd have

Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

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