[Mono-bugs] [Bug 695704] New: eglib compilation fails for x64 target (Win64)

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=695704

https://bugzilla.novell.com/show_bug.cgi?id=695704#c0


           Summary: eglib compilation fails for x64 target (Win64)
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.10.x
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: jarkko at profoundic.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Community User
           Blocker: No


Description of Problem:

When opening eglib.vcproj project in VS2008 and changing the project settings
in C/C++ => Optimization => Optimization => Full Optimization (/Ox) and setting
Whole Program Optimization to No, the code generation in Visual Studio 2008
never finishes.

Steps to reproduce the problem:
1. Open msvc/eglib.vcproj in VS2008
2. Select Release_eglib build and x64 target
3. Open property page for eglib project
4. In Configuration Properties => C/C++ => Optimization change the following
two settings:
4.1. Optimization => Full Optimization (/Ox)
4.2. Whole Program Optimization => No
5. Rebuild the project => the compilation never finishes but hangs at
"Generating Code..." phase


Actual Results:
Compilation hangs at "Generating Code..." phase

Expected Results:
Should finish compilation & library generation normally

How often does this happen? 
Every time

Additional Information:
I was able to locate the offending line in the code causing this issue. In
gmem.c file and g_memdup() function, when commenting the following two lines
out the compilation succeeds as expected:
    if (ptr != NULL)
        memcpy (ptr, mem, byte_size);


Thanks, Jarkko

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.