920740 - MASM crash in ctypes with VS2013 amd64_x86 cross-compile

Status: RESOLVED WORKSFORME

(Firefox Build System :: General, defect)

Description

[(Away)]

I am separating this issue from Bug 914523 so that we can keep it as an active blocker against the VC12 meta-bug.


(In reply to zhoubcfan from comment #6)
> another problem is in ctype. the amd_x86 cross compiler has problem, though
> the native one is fine.
> 
> 
> cl -nologo -EP  -I. -Id:/develop/mozilla/central/js/src/ctypes/libffi -I.
> -Id:/d
> evelop/mozilla/central/js/src/ctypes/libffi/include -Iinclude
> -Id:/develop/mozil
> la/central/js/src/ctypes/libffi/src -I.
> -Id:/develop/mozilla/central/js/src/ctyp
> es/libffi/include -Iinclude
> -Id:/develop/mozilla/central/js/src/ctypes/libffi/sr
> c  -DHAVE_CONFIG_H
> d:/develop/mozilla/central/js/src/ctypes/libffi/src/x86/win32
> .S > src/x86/win32.asm
> win32.S
> ml -nologo -safeseh -c -Fosrc/x86/win32.obj src/x86/win32.asm
>  Assembling: src/x86/win32.asm
> 
> MASM : fatal error A1016: Internal error
> 
>   Version 12.00.20824.1
> 
>   ExceptionCode            = C0000005
>   ExceptionFlags           = 00000000
>   ExceptionAddress         = 00007FF79414F407 (00007FF794130000) "c:\Program
> Fil
> es (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64_x86\ml.exe"
>   NumberParameters         = 00000002
>   ExceptionInformation[ 0] = 0000000000000000
>   ExceptionInformation[ 1] = FFFFFFFFFFFFFFFF
> 
> CONTEXT:
>   Rax    = 0000000000000000  R8     = 0000000000000000
>   Rbx    = 0000002F81D6C2D8  R9     = 000000000000002D
>   Rcx    = 0000002F81D6C300  R10    = 00007FF98B8A72A0
>   Rdx    = 0000000000000000  R11    = 0000002F81D6BF90
>   Rsp    = 0000002F81B7EAF0  R12    = 0000000000000000
>   Rbp    = 0000000000000007  E13    = 0000000000000000
>   Rsi    = 0000000000000000  R14    = 00007FF7941A55AE
>   Rdi    = 414C460400000000  R15    = 00007FF794130000
>   Rip    = 00007FF79414F407  EFlags = 0000000000010206
>   SegCs  = 0000000000000033  SegDs  = 000000000000002B
>   SegSs  = 000000000000002B  SegEs  = 000000000000002B
>   SegFs  = 0000000000000053  SegGs  = 000000000000002B
>   Dr0    = 0000000000000000  Dr3    = 0000000000000000
>   Dr1    = 0000000000000000  Dr6    = 0000000000000000
>   Dr2    = 0000000000000000  Dr7    = 0000000000000000

(In reply to Makoto Kato (:m_kato) from comment #8)
> I file as ml.exe issue as
> https://connect.microsoft.com/VisualStudio/feedback/details/800216/. 
> Thanks,  zhoubcfan.


It seems we only use ml.exe to compile one small file, so for now my local workaround is to just substitute the native-32bit version.

Comment 1

[Makoto Kato [:m_kato]]

msvcc.sh is hardcoded that that uses ml.exe in current PATH.  If we use custom msvcc.sh instead of libffi/msvcc.sh, we can fix this easily.

But microsoft says, "Yes, there is definitely an issue with the amd64_x86 ML.EXE. We're fixing this for the next release.", so I hope this is fixed by RTM version.

Comment 2

[[e-mail]]

it seems to be fixed in the rtm

Comment 3

[Masatoshi Kimura [:emk]]

Works for me, too.