Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Win arm64#2170

Closed
rahku wants to merge 1 commit intodotnet:masterfrom
rahku:winArm64
Closed

Win arm64#2170
rahku wants to merge 1 commit intodotnet:masterfrom
rahku:winArm64

Conversation

@rahku
Copy link

@rahku rahku commented Nov 26, 2015

Arm64 SDK is still to be released. Using a private drop of the toolset and these changes I am able to successfully build arm64 builds for windows. We need to set certain environment variables to override the location of toolset and sdk.

@rahku
Copy link
Author

rahku commented Nov 26, 2015

Please review.
@gkhanna79 @jkotas @janvorli @briansull

@jkotas
Copy link
Member

jkotas commented Nov 26, 2015

Could you please rebase away the merge commits? Assuming you have a typical setup:

git rebase -i master
git push -f origin winArm64

@rahku
Copy link
Author

rahku commented Nov 26, 2015

done

CMakeLists.txt Outdated
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should `cl.exe' be really hardcoded? Same goes for other binaries that got converted to a hardcoded name with .exe.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not hardcode the cl.exe. What is the problem with using the CMAKE_CXX_COMPILER?

@kangaroo
Copy link

Has this been checked to make sure it doesn't regress the arm64/linux build?
Additionally, can't CMAKE_TOOLCHAIN_FILE be used instead of all the hardcoded names?

CMakeLists.txt Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that this comment was there before, but it sounds weird. Could you please change it to "Enable edit and continue"? We don't need to enumerate the platforms, the surrounding ifs are descriptive enough.

@rahku
Copy link
Author

rahku commented Nov 26, 2015

Thanks for the review. I will try this again after I am back from my trip. closing for now. If anyone wants to use it ...can do so using winArm64 branch of my fork.

@rahku rahku closed this Nov 26, 2015
@jashook jashook reopened this Dec 3, 2015
@jashook
Copy link

jashook commented Dec 3, 2015

Reopening this pull request to start working on it some more.

I will have a change out to address comments soon.

@jashook
Copy link

jashook commented Dec 4, 2015

Messed up with the commit. Hopefully did it as expected, didn't entirely know whether to modify the original commit or no. I can change that if instructed.

@jkotas @janvorli PTAL.

@jashook jashook force-pushed the winArm64 branch 2 times, most recently from 02b9772 to a423f2e Compare December 5, 2015 00:45
@jashook jashook force-pushed the winArm64 branch 2 times, most recently from f2cd82b to bc9c031 Compare December 5, 2015 01:23
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is I386 really supported in CoreCLR currently? Otherwise we can unify these message()'s and drop the if()

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's supported in the sense that it builds successfully for x86 (or at least used to when I wrote that if).

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also we are working on x86 JIT bring up at the moment.

@kangaroo
Copy link

kangaroo commented Dec 5, 2015

LGTM modulo feedback, and @jkotas comments on the hard coded tools.

EDIT: No LGTM until the actual SDK is released for us proletariats.

@jashook jashook force-pushed the winArm64 branch 2 times, most recently from 3c992ef to e269c4d Compare December 8, 2015 02:09
@jashook
Copy link

jashook commented Dec 8, 2015

Outdated comment.

@jkotas PTAL

@gkhanna79
Copy link
Member

@jashook PEr https://msdn.microsoft.com/en-us/library/9a89h429.aspx?f=255&MSPPError=-2147217396, you should not need SAFESEH as it is applicable to x86 only (as noted in the PR as well).

Can you please share the failure you are running into?

@gkhanna79
Copy link
Member

@jashook Can you please squash the commits?

@mmitche Are the OSX build failures the issues you were looking into last week?

@mmitche
Copy link
Member

mmitche commented Dec 14, 2015

@gkhanna79 Yeah they are.

@jashook
Copy link

jashook commented Dec 14, 2015

@gkhanna79 Squashed

@jashook
Copy link

jashook commented Dec 15, 2015

@jkotas @gkhanna79 PTAL. Removed SafeSEH and verified that the build is still successful.

@gkhanna79
Copy link
Member

The x86 Windows Debug build failed due to the following:

18:30:15 Read in 1611 resources from "d:\j\workspace\dotnet_coreclr\x86_debug_windows_nt_prtest\src\mscorlib\src\mscorlib.txt"
18:30:15 Writing resource file... Done.
18:30:28 mscorlib -> d:\j\workspace\dotnet_coreclr\x86_debug_windows_nt_prtest\bin\obj\Windows_NT.x86.Debug\mscorlib.dll
18:31:03
18:31:03 Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
18:31:03 at Microsoft.Cci.ISymUnmanagedWriter2.Close()
18:31:03 at BclRewriter.Program.RunBclRewriter(String[] args)
18:31:03 at BclRewriter.Program.Main(String[] args)

@weshaggard @AlexGhiondea Are you aware of this issue?

@gkhanna79
Copy link
Member

LGTM. Please squash the commits, sign CLA and update this thread once done.

Successfully builds all binaries except sos.dll & x64 binaries
@AlexGhiondea
Copy link

@gkhanna79 no -- I have not seen that before. Does it repro consistently?

@gkhanna79
Copy link
Member

It looks occasional - you can see the history.

@jashook
Copy link

jashook commented Dec 15, 2015

Squashed, it also looks like Rahul needs to sign the CLA as I have already done that. Closing this PR then opening a new one to point to this.

@jashook jashook closed this Dec 15, 2015
@jashook jashook mentioned this pull request Dec 15, 2015
@rahku rahku deleted the winArm64 branch January 4, 2016 20:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.