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

Conversation

papaslavik
Copy link

Should the compare functions be different for the size and execution time optimization?

/cc @briansull @mikedn

@briansull
Copy link

briansull commented Jul 14, 2016

Yes, your changes are correct. This will change the order that we examine CSE candidates
when (CodeOptKind() == Compiler::SMALL_CODE) is true.
Which would be in places like static class constructors.

I would like to examine what the impact of this change is on Code size before we commit this.

@briansull
Copy link

@russellhadley We should see what the Asm diffs are for this commit

@russellhadley
Copy link

https://github.com/dotnet/jitutils has a set of tools that will let you run and analyze the codesize and show the diffs

@papaslavik
Copy link
Author

@briansull By the way, I tested on ARM that switching SMALL_CODE to everything while crossgen doesn't affect the size of System.Private.CoreLib.ni.dll

@russellhadley thanks for the link

@papaslavik
Copy link
Author

@russellhadley are there also any tests which would detect the difference?

@papaslavik
Copy link
Author

@Dmitri-Botcharnikov

@briansull
Copy link

I took a look at this and also ran ASM diffs and am satisfied that that this change is fine.

@briansull briansull merged commit 70769b7 into dotnet:master Jul 29, 2016
@papaslavik
Copy link
Author

Thank you @briansull !

Were there any actual diffs and could you share which tests you tried or at least point to the right direction? Just for a future memory consumption research...

picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
The sort for CSE size optimization should be different from exec

Commit migrated from dotnet/coreclr@70769b7
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.

4 participants