search for: lipo

...lementation of llvm-objcopy for MachO with the long-term plan to build some popular binary-level tools on top of it. That effort stopped at the stage where some boilerplate code for reading/writing MachO files was reviewed & committed to LLVM/tools/llvm-objcopy. Later I started working on llvm-lipo (a drop-in replacing for the tool "lipo" for manipulating "fat" binaries), but that code has never been sent for code review. The original plan was to use the approach similar to llvm-strip, where the new tool is just another "driver" for llvm-objcopy. This approach wo...

...ry similar feelings / thoughts. After some thinking it seems to me that this discussion/problem which I have brought up is, in fact, more relevant to the tools which really need a robust mutable model of an object file (like objcopy, strip, install_name_tool, etc), but the particular case of "lipo" might be simpler, I need to double check that / will take a closer look again. What I mean - the tool "lipo" manipulates "fat" binaries by extracting, removing, replacing slices (slice = object file for a particular architecture), but the slices themselves are unmodified,...

...er some thinking it seems to me that this discussion/problem which I >> have brought up is, in fact, >> more relevant to the tools which really need a robust mutable model of an >> object file (like objcopy, strip, install_name_tool, etc), >> but the particular case of "lipo" might be simpler, I need to double >> check that / will take a closer look again. >> What I mean - the tool "lipo" manipulates "fat" binaries by extracting, >> removing, replacing slices >> (slice = object file for a particular architecture), but t...

Hi! since the first time I compiled llvm for 32 and 64 on macos (xcode 3.2) I get errors from lipo which I so far ignored since they only occur for the executables but I only need the libraries. but It would be interesting if someone knows where they come from. They look like this: CreateUniversalBinary build/llvm/bin/Debug/opt normal "i386 x86_64" cd /Users/jwilhelmy/Coding/Lib/llvm...

Hey everyone! Recently there has been some progress on LLVM-based tools for manipulating MachO binaries: llvm-objcopy has been gaining a lot of important bits to support MachO (it's relatively close to the point where one can implement the strip-like functionality), llvm-lipo is functional and supports most of cctools' lipo options (https://llvm.org/docs/CommandGuide/llvm-lipo.html). There is another useful utility called install_name_tool (see e.g. https://www.unix.com/man-page/osx/1/install_name_tool/ ), this tool is capable of changing the rpaths, the names of th...

I guess I should add this to the long list of things Apple has broken that used to work well on NEXTSTEP (the operating system that has been turned into OS X). Now that you mention it, I remember having a problem getting flac to cross-compile in one build step, so I just did the manual lipo glue that you talked about. I assumed it was only because I was too lazy to figure out how to get Xcode to work, but from your report it seems like there is much more to the problem. From your steps, it seems that it is possible to cross-compile, but only if you build one architecture at...

...gt; Hey everyone! > Recently there has been some progress on LLVM-based tools for manipulating > MachO binaries: llvm-objcopy has been gaining a lot of important bits to > support MachO (it's relatively close to the point where one can implement > the strip-like functionality), llvm-lipo is functional and supports most of > cctools' lipo options (https://llvm.org/docs/CommandGuide/llvm-lipo.html > ). > There is another useful utility called install_name_tool (see e.g. > https://www.unix.com/man-page/osx/1/install_name_tool/ ), > this tool is capable of changing t...

...compiled for another flavor of x86. I care about the usage model, which is important for LTO - a dispatch function (compiled for the least common denominator) + plus set of specialized functions for sse4, avx ,avx2 and etc., which are called by dispatch function depending on runtime cpu id check. lipo may help achieving this on Darwin, but it's not exactly what I need. I need a solution suitable for LTO. Actually lipo may work for me as a workaround, but I need cross platform solution. The current solution doesn't really address this (on x86 at least), as sub-target is not recreated if...

...t; LTO - a dispatch function (compiled for the least common denominator) + > plus set of specialized functions for sse4, avx ,avx2 and etc., which are > called by dispatch function depending on runtime cpu id check. > > > Okay. The terminology was a bit overloaded. :-) > > > lipo may help achieving this on Darwin, but it's not exactly what I > need. I need a solution suitable for LTO. Actually lipo may work for me as > a workaround, but I need cross platform solution. > > > > The current solution doesn't really address this (on x86 at least), as &g...

...runtest checking for i686-pc-cygwin-ar... (cached) ar checking for i686-pc-cygwin-as... (cached) as checking for i686-pc-cygwin-dlltool... (cached) dlltool checking for i686-pc-cygwin-ld... (cached) /usr/lib/gcc/i686-pc-cygwin/4.3.4/../ ../../../i686-pc-cygwin/bin/ld.exe checking for i686-pc-cygwin-lipo... no checking for lipo... no checking for i686-pc-cygwin-nm... (cached) nm checking for i686-pc-cygwin-ranlib... (cached) ranlib checking for i686-pc-cygwin-strip... (cached) strip checking for i686-pc-cygwin-windres... (cached) windres checking for i686-pc-cygwin-objcopy... (cached) objcopy check...

...IR: /Users/makira/Desktop/git_repository/sonicbirth/ThirdParty/build/tools/clang/runtime/compiler-rt/clang_darwin/eprintf FINAL-ARCHIVE: clang_darwin/eprintf: /Users/makira/Desktop/git_repository/sonicbirth/ThirdParty/build/tools/clang/runtime/compiler-rt/clang_darwin/eprintf/libcompiler_rt.a lipo: no input files specified lipo: Usage: lipo [input_file] ... [-arch <arch_type> input_file] ... [-info] [-detailed_info] [-output output_file] [-create] [-arch_blank <arch_type>] [-thin <arch_type>] [-remove <arch_type>] ... [-extract <arch_type>] ... [-extract_family...

...tion (compiled for the least common denominator) + >> plus set of specialized functions for sse4, avx ,avx2 and etc., which are >> called by dispatch function depending on runtime cpu id check. >> > >> Okay. The terminology was a bit overloaded. :-) >> >> > lipo may help achieving this on Darwin, but it's not exactly what I >> need. I need a solution suitable for LTO. Actually lipo may work for me as >> a workaround, but I need cross platform solution. >> > >> > The current solution doesn't really address this (on x86...

...model, which is important for LTO - a dispatch function (compiled for the least common denominator) + plus set of specialized functions for sse4, avx ,avx2 and etc., which are called by dispatch function depending on runtime cpu id check. > Okay. The terminology was a bit overloaded. :-) > lipo may help achieving this on Darwin, but it's not exactly what I need. I need a solution suitable for LTO. Actually lipo may work for me as a workaround, but I need cross platform solution. > > The current solution doesn't really address this (on x86 at least), as sub-target is not rec...

...ns and different copy of the comdat function to be picked up in the end. > > > > I wonder whether a prefix would be better? > > All the promotion/renaming scares me. I feel like there may be > dragons here we're not aware of. > > The promotion scheme is similar to LIPO which has been exercised on large number of huge C++ apps -- I think it is robust. > The only concrete concern I have (once you switch to hidden > visibility) is the interaction with non-LTO'd objects being linked > into the same executable, but I wonder if I'm missing somethin...

Sorry again, my bad. I actually was using --enable-pics instead of --enable-pic. Now LLVM is being compiled. Hope the last phase llvm-gcc compilation would be a success. Thanks a lot. Akramul --- On Sun, 2/1/11, akramul azim <bijoy123_8 at yahoo.com> wrote: From: akramul azim <bijoy123_8 at yahoo.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "Bill Wendling"

...portant for LTO - a dispatch function (compiled for the least common denominator) + plus set of specialized functions for sse4, avx ,avx2 and etc., which are called by dispatch function depending on runtime cpu id check. > > > Okay. The terminology was a bit overloaded. :-) > > > lipo may help achieving this on Darwin, but it's not exactly what I need. I need a solution suitable for LTO. Actually lipo may work for me as a workaround, but I need cross platform solution. > > > > The current solution doesn't really address this (on x86 at least), as sub-target i...

In my experience, with the gcc compiler, cross-compiling is highly reliable. If your code runs on one processor, then it will run on all. Linking and such might be an issue, which you will discover immediately when the first person tries to run what you've built on their system. It still would be great to run these tests on all four. Actually, you should be able to test 32-bit

...mented correctly. Many of the objects that rely upon those features weren't updated when those features were changed. I have a new way of doing this, but it's still in the alpha stage (I haven't yet sent the whitepaper to the group). Support for fat binaries is done on Darwin with the `lipo' command. Otherwise, I'm not sure if this really answers your question. :-) -bw -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131009/2fd103ac/attachment.html>

...at function to be picked up in the end. > Good point. > > > > > I wonder whether a prefix would be better? > > All the promotion/renaming scares me. I feel like there may be > dragons here we're not aware of. > > > The promotion scheme is similar to LIPO which has been exercised on large number of huge C++ apps -- I think it is robust. Sure, but other languages, platforms and conventions may yield other problems. Anyway, it's just a theoretical concern, I don't have anything concrete! > > The only concrete concern I have (once y...

Sorry I used --enable-pic, not --enable-pics. It was a typo. Akramul --- On Sun, 2/1/11, akramul azim <bijoy123_8 at yahoo.com> wrote: From: akramul azim <bijoy123_8 at yahoo.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "Bill Wendling" <wendling at apple.com> Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, llvmdev at cs.uiuc.edu Date: