search for: q018

On 5/2/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > Well, I don't quite understand why AC_C_BIGENDIAN and the solution > you're proposing is likely to break other big endian machines (the ones > that don't have __BIG_ENDIAN__). Can you send a patch that addresses > that (i.e. still uses AC_C_BIGENDIAN when it works)? It is not that AC_C_BIGENDIAN

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

...of my projects, libsndfile, endian issues is not the only think that breaks in univesal binaries. The problem is that I detect cpu features other than just endian-ness at configure time; things that cannot be detected purely from compiler flags. See: http://www.mega-nerd.com/libsndfile/FAQ.html#Q018 However, my biggest objection to universal binaries for libsndfile is that libsndfile has a huge and comprehensive test suite and running the test suite during a universal build will only test the native build, not the cross-compiled build. As far as I am concerned, cross-compiled code that isn...

...libsndfile on Intel macs. After I spent a bunch of my very valuable time the idiot reporting the issue finally confessed that he was compiling libsndfile as a universal binary on PPC and then seeing bugs on Intel. The result of all this was a FAQ: http://www.mega-nerd.com/libsndfile/FAQ.html#Q018 and me adding code to libsndfile to detect when it was being compiled as a UB and erroring out if it was. For libsndfile, the *only* reliable way to create a 32 bit intel/ ppc UB is: 0) configure for intel 1) make 2) make check 3) configure for powerpc 4) make 5) make check 6) use lipo to...

...ndian issues is not the only > think that breaks in univesal binaries. The problem is that I > detect cpu features other than just endian-ness at configure time; > things that cannot be detected purely from compiler flags. > > See: > http://www.mega-nerd.com/libsndfile/FAQ.html#Q018 Can you elaborate on what kind of CPU vagaries come into play besides endianess? Do they affect all code or just highly-optimized code? I have built several open source projects as universal binaries and they basically function. If you know of specific risks to look out for, your experiences would...

...I spent a bunch of my very valuable time the > idiot reporting the issue finally confessed that he was compiling > libsndfile as a universal binary on PPC and then seeing bugs on > Intel. > > The result of all this was a FAQ: > > http://www.mega-nerd.com/libsndfile/FAQ.html#Q018 > > and me adding code to libsndfile to detect when it was being compiled > as a UB and erroring out if it was. > > For libsndfile, the *only* reliable way to create a 32 bit intel/ > ppc UB is: > > 0) configure for intel > 1) make > 2) make check > 3) configure...