Re: Mach-O and SECTION .rodata

Michael Militzer <[email protected]>
Newsgroups gmane.comp.video.xvid.devel
Message-ID <[email protected]>
Hi,

that's good news indeed. I have added a note in the README.

The easiest solution will certainly be to check for latest versions of yasm/
nasm in ./configure as soon as new releases containing the bug fix will
become available.

Regards,
Michael


Quoting Takashi Mochizuki <[email protected]>:

> Hew! Cool.
> Now MacOS X can process asm code without alignment hack. (latest nasm
> also has that bug though)
>
> How about to describe it in README? like:
> - yasm 0.7.99.2161 or later is required for MacOS X build. -
>
> Takashi
>
> On 2008/12/08, at 3:53, David DeHaven wrote:
>
>>
>>>>> After a few hour search, I have found
>>>>> -   
>>>>> <http://lists.mplayerhq.hu/pipermail/ffmpeg-cvslog/2008-August/015984.html
>>>>>>
>>>>>
>>>>> Directive ALIGN for SECTION .rodata may not function well - under
>>>>> "some" MacOS X; at least my mac.
>>>>> (It seems to be, not yasm/nasm issue though... by ld64?)
>>>>
>>>> I'm going to go out on a limb here and say ld64 is doing exactly
>>>> what
>>>> it's supposed to do and the bug is in the mach-o object code in
>>>> nasm/
>>>> yasm.
>>>
>>> Seems I was right. In yasm/modules/objfmts/macho/macho-objfmt.c if I
>>> force address alignment in macho_objfmt_calc_sectsize then it builds
>>> and runs just fine using .rodata instead of .text.
>>>
>>> Running xvid_bench right now and it hasn't crashed yet...
>>
>> Patch was submitted to yasm-devel and is now in yasm SVN HEAD (as of
>> r2161). I built xvid_bench with it and it ran just fine.
>>
>> -DrD-
>>
>> _______________________________________________
>> Xvid-devel mailing list
>> [email protected]
>> http://list.xvid.org/mailman/listinfo/xvid-devel
>
> _______________________________________________
> Xvid-devel mailing list
> [email protected]
> http://list.xvid.org/mailman/listinfo/xvid-devel
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.