platform/upstream/coreclr - Domain: Dotnet / Core; Licenses: MIT;

Age	Commit message (Collapse)	Author	Files	Lines
2019-01-23	Remove all traces of FEATURE_STACK_PROBE. (#22149)	Filip Navara	1	-3/+0

2017-01-18	Remove ILDASM GUI cruft (#8954)	mikedn	1	-131/+2

2016-09-08	ILDASM: Ignore Metadata flag for CoreCLR	Kyungwoo Lee	1	-19/+21
	Full metadata emission is disabled under coreclr. So is ILDASM instead of failing during the run.
2016-01-27	Update license headers	dotnet-bot	1	-4/+3

2015-12-07	Enable ildasm for *nix	Kyungwoo Lee	1	-3/+19
	This enables ildasm for cross-platforms. Unlike Window (where initialization is done when DLL attach), CoreCLR is explciltly hosted/initialized to get the Metadata related APIs. This also eliminates the need of setting dynamic library path. Currently, ildasm binary is assumed to be located same as CoreCLR binary. I added a simple CoreCLRLoader (not meant to run an assembly file) for just direct uses of APIs. Since I expect this library to be used for ilasm work. Resource string is also handled using a static string table based on my prior check-in. Other changes are mostly mechanic with regard to wide constant string.
2015-11-25	Enable ILDASM for Windows	Kyungwoo Lee	1	-3/+20
	This enables building ILDASM with Cmake for Windows. This ILDASM now depends on CoreCLR targeting cross-platform and thus I dropped some features like GUI/PDB -- default output is console. Metadata related APIs in CoreCLR are directly exported, and used in ILDASM: MetaDataGetDispenser GetMetaDataInternalInterface GetMetaDataInternalInterfaceFromPublic GetMetaDataPublicInterfaceFromInternal The code path is diverged by a definition FEATURE_CORECLR. There are still Window specific components. Among others, resource file/dll generation is the one that should be ported.
2015-11-24	Open sourcing ILDASM	dotnet-bot	1	-0/+698
	[tfs-changeset: 1551732]