similar to: [LLVMdev] Off Topic: Building ld

On 14.01.2012, at 17:23, Joe Abbey wrote: > I have a need to build ld from source to understand an assert(0). > > I got excited when I found that ld64 on the opensource portal contains an xcodeproj > > http://opensource.apple.com/source/ld64/ld64-127.2/ > > But... it seems like I'm lacking mach-o/arm/reloc.h, and dyld_priv.h. > > I'm doing my best to stitch

Thanks for your response, that's kinda what I've gathered over the years. I was hoping that the Xcode project would have "just worked". I'll keep piece-mealing it together, and hope that it works. I'll try to post a radar. Joe Joe Abbey Director of S/W Development Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W: 765-889-4756 x2 C:

Renato, I was wondering when the videos might be uploaded. The slide material is great! Thanks! Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W: 765-889-4756 x2 C: 765-464-9893 jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

Legal... really? :( What a shame. I'll wait patiently, unless I can get a download link... :-D Don't wanna anger legal though... Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W: 765-889-4756 x2 C: 765-464-9893 jabbey at arxan.com<mailto:jabbey at arxan.com> www.arxan.com On Oct 17, 2011, at 10:20 AM, James Molloy

Hi Joe, I can answer that, as I'm dealing with it J The videos are stuck currently with our legal department. They've gotten extremely sensitive over it and we have had to get Tanya/Chris to agree to a secure dropbox so we can send the videos to them to put on the website (binaries don't live in SVN). Obviously Tanya is very busy with the release at the moment, so it's

Ben, Thanks for your help! > http://opensource.apple.com/source/cctools/cctools-806/include/mach-o/arm/reloc.h Yep, as Joe Ranieri pointed out, I had to tell MachOFileAbstraction.hpp about ARM relocs > http://opensource.apple.com/source/dyld/dyld-195.5/include/mach-o/dyld_priv.h I tried to use the dyld_priv.h from cctools to no avail, using the one from dyld (as you pointed out) worked

I'm the code owner of LLVM codegen and targets. I'm also the one of main developers on the original ARM target. That means, I would make the decisions on major development on ARM target if there are decisions to be made. But my role is very different from what people are looking for in this thread. To properly qualify a target like ARM which are supported on many different CPUs and

I see, so perhaps the LLVM ARM Backend is in need of a method of organizing volunteer qualifiers, as releases near? Has this generally been organized via this mailing list? Joe Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W: 765-889-4756 x2 C: 765-464-9893 jabbey at arxan.com<mailto:jabbey at arxan.com>

Hello, I've got a couple spare machines I'd like to enlist in build bot. I'm told that the llvm lab folks are the go-to group. I've got a couple machines prepped, I just need to register their names and passwords (I think). Let me know what else I need to do! Thanks, Joe Abbey Software Architect Arxan Technologies, Inc. 1305 Cumberland Ave, Ste 215 West Lafayette, IN 47906 W:

I think we need a group of maintainers rather than a single maintainer given the spectrum of ARM targets/ISAs/platforms required to support and the amount of people/system resources required. I & my team plan to actively participate in the bug-fixing process during the release cycle. If we can divide the bugs among the maintainers and establish a requirement that all open ARM bugs must be

Admittedly we're very interested in becoming ARM backend maintainers as our product heavily relies on LLVM. However, we don't have testing resources to test both our product and LLVM on a host of target boards. We have some chumbys, beagleboards, iPhones, iPod Touches, tables, Android Phones, etc. And most of those are already booked solid with our own regression tests (most of which

First LLVM Social in West Lafayette, IN. When: Thursday, Dec 6th @ 8:30pm Where: GreyHouse Coffee 100 Northwestern Avenue West Lafayette, IN 47906 https://plus.google.com/102658466942690664690/about Please RSVP, so I can let GreyHouse know if we need a meeting room. Cheers, Joe ______________________________ Joe Abbey Director of Software Development Arxan Technologies jabbey at

On 11 October 2011 18:22, Anton Korobeynikov <anton at korobeynikov.info> wrote: > 1. We should define which ARM-related features (in general, e.g. > platforms, cores, modes, etc.) we consider "release important" > 2. We should define the conditions how the features in 1. should be tested > 3. Someone should perform such testing for each release, provide help > with

On Oct 13, 2011, at 10:33 AM, Raja Venkateswaran wrote: > I think we need a group of maintainers rather than a single maintainer given the spectrum of ARM targets/ISAs/platforms required to support and the amount of people/system resources required. I & my team plan to actively participate in the bug-fixing process during the release cycle. If we can divide the bugs among the maintainers

Hi James, > It goes without saying that I +1 this. Well, the answer should be pretty easy, I think: 1. We should define which ARM-related features (in general, e.g. platforms, cores, modes, etc.) we consider "release important" 2. We should define the conditions how the features in 1. should be tested 3. Someone should perform such testing for each release, provide help with

No. -Tanya On Jan 3, 2012, at 5:29 PM, Joe Abbey <jabbey at arxan.com> wrote: > Tanya, > > Was there any video taken of Chris's keynote? > > Joe > > Joe Abbey > Director of S/W Development > Arxan Technologies, Inc. > 1305 Cumberland Ave, Ste 215 > West Lafayette, IN 47906 > jabbey at arxan.com > www.arxan.com > > On Jan 3, 2012, at

I've done a first pass over the past 6 months of changes and some notable things stood out: * The ARM backend has reworked Set Jump Long Jump EH Lowering. * The ARM backend includes improved support for Cortex-M * The ARM backend adds parsing and encoding ARM/Thumb/Thumb2 assembly There are also many many code generation improvements which select more optimal instructions. Those seemed

Please don't be alarmed by the failed compiles on llvm-ppc-darwin. They are likely not your fault. I'm trying to get a PPC build bot setup (arxan_bellini), and so far it's dying here: Linking CXX shared library ../../lib/libgtest.dylib Undefined symbols: "vtable for llvm::raw_ostream", referenced from: __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest.cc.o

As some of you may have noticed, all the slides and videos have been uploaded to the website: http://llvm.org/devmtg/2011-11/ Thanks to everyone for a great event! Thanks, Tanya

I'm so close to having LLVM build on PowerPC. If there's any PowerPC experts, help? Lines like this: outs() << "[" << format("%2d", i) << "]" << "(sec " << format("%2d", int16_t(symbol->SectionNumber)) << ")" << "(fl 0x" <<