>>> It's not clear to me that we ought to do anything; this is a problem >>> only when building using compilers for MacOSX releases that have long >>> since been EOLed. >> >> Well, if you can confirm following, then it would still be appropriate >> to revert that change. Compile following snippet with -sectalign __DATA >> __common 4 argument and post nm output for resulting binary. >> >> .text >> .globl _main >> _main: >> ret >> >> .comm _one,4 >> .comm _two,8 >> .comm _four,16 >> >> Goal is to confirm that _two and _four are actually aligned at their >> sized even though section alignment is relaxed. > > Here's what I obtained on 10.4.11/ppc: >> $ cc -arch i386 -sectalign __DATA __common 4 -isysroot >> /Developer/SDKs/MacOSX10.4u.sdk -c -o alignments.o alignments.s ; nm >> alignments.o >> 00000010 C _four >> 00000000 T _main >> 00000004 C _one >> 00000008 C _two
No, not -c, but all the way so that it generates executable. Question is what is alignment of these variables in *final* executable, not intermediate .o. I should have been more explicit, sorry. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
