Skip to content

crossgen2-comparison windows x86 Release to x86 windows failing for System.Private.CoreLib #115661

Closed

Description

@elinor-fung

Example build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1043288&view=results

Comparing crossgen results in "C:\h\w\9D490889\w\AAA3099F\u\prebuiltWork\log" and "C:\h\w\9D490889\w\AAA3099F\uploads" directories for files of type "NativeOrReadyToRunImage":
File hash sum mismatch for "System.Private.CoreLib" assembly for files of type "NativeOrReadyToRunImage":
 - "C:\h\w\9D490889\w\AAA3099F\u\prebuiltWork\log" has "eb257a2ff5dc02fb96f92a781432bb5ef7c52b2bfa1ff42c5bbba04f960bb79c"
 - "C:\h\w\9D490889\w\AAA3099F\uploads" has "a6a96aba010df04e946fad72fef8e4e90f4fbbdcf3afff9f37be2c621df61344"
Number of omitted results: 0
Number of mismatched results: 1
Total number of files compared: 236

Activity

  1. removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 21, 2025
  2. modified the milestones: 11.0.0, 10.0.0 on Jul 21, 2025
  3. max-charlamb commented on Jul 21, 2025

    @max-charlamb
    Member

    I looked into how the two System.Private.Corelib.dll differ and it appears the codegen for

    System.ValueTuple`2<System.Numerics.Vector`1<float>,System.Numerics.Vector`1<float>> System.Runtime.Intrinsics.VectorMath.<SinCosSingle>g__ScalarFallback|29_1<System.Numerics.Vector`1<float>, System.Numerics.Vector`1<int>, System.Numerics.Vector`1<double>, System.Numerics.Vector`1<long>>(System.Numerics.Vector`1<float>)
    

    is different when compiling on x86 vs x64. I'm wondering if this could be a codegen issue. There were some commits in the range that modified x86 intrinsics.

    x86 target compiling on x64
    x86 target compiling on x86

    The following 3 byte difference in encoding causes further instructions to not line up (among other differences).

    x86 on x64
    0000000000670B8B F30F11849DBCFFFFFF   movss     [ebp+ebx*4-44h],xmm0
    
    x86 on x86
    0000000000670B8B F30F11449DBC         movss     [ebp+ebx*4-44h],xmm0
    

    I will keep looking into why these are generated differently.

  4. locked and limited conversation to collaborators on Aug 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions