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

Age	Commit message (Collapse)	Author	Files	Lines
2017-08-07	Cleanup code access security from the unmanaged runtime (#13241)	Jan Kotas	1	-3/+0

2017-05-17	Finish deleting dead CAS code from CoreLib (#11436)	Jan Kotas	1	-188/+3
	Fixes #9321 and deletes CleanupToDoList.cs Delete unmanaged security implementation
2017-02-14	Remove never defined FEATURE_REMOTING	danmosemsft	1	-49/+0

2017-02-14	Remove never defined FEATURE_METHOD_RENTAL	danmosemsft	1	-3/+0

2017-02-14	Remove never defined FEATURE_ISOSTORE	danmosemsft	1	-3/+0

2017-02-10	Remove always defined FEATURE_CORECLR	danmosemsft	1	-68/+0

2017-02-10	Remove always undefined FEATURE_APTCA	danmosemsft	1	-19/+0

2016-03-21	Delete legacy netcf compat support (part 1)	Jan Kotas	1	-5/+0

2016-01-27	Update license headers	dotnet-bot	1	-4/+3

2015-10-20	Implementation of System V ABI struct passing.	Lubomir Litchev	1	-5/+8
	This PR adds support for System V x86_64 ABI classification and calling convention to the VM and the Jit, including, but not limited to Ubuntu Linux and Mac OS X. The general rules outlined in the System V x86_64 ABI (described at http://www.x86-64.org/documentation/abi.pdf) are followed with a few little exceptions, described below: 1. The hidden argument for by-value passed structs is always after the ÎéÎíthisÎéÎí parameter (if there is one.). This is a difference with the Sysetem V ABI and affects only the internal jit calling conventions. For PInvoke calls the hidden argument is always the first parameter since there is no ÎéÎíthisÎéÎí parameter in this case. 2. Managed structs that have no fields are always passed by-value on the stack. 3. The jit proactively generates frame register frames (with RBP as a frame register) in order to aid the native OS tooling for stack unwinding and the like.
2015-04-16	Fix dangling else warnings	Jan Vorlicek	1	-1/+3
	This change fixes all dangling else warnings and removes the compiler flag that was disabling their reporting.
2015-03-21	Add host flag to disable transparency checks in CoreCLR	Jan Kotas	1	-18/+20
	A lot of security transparency annotations in corefx is missing or inconsistent. People keep running into MethodAccessExceptions because of that. It is not easy (nor cheap) to fix the annotations to make them consistent, and they are not actually required for any of the .NET Core scenarios. This change is introducing a hosting flag to disable security transparency checks on CoreCLR, and adds this flag to all .NET Core hosts. The .NET Core hosts outside of the CoreCLR tree (e.g. ASP.NET 5) will need this flag added as well. [tfs-changeset: 1437325]
2015-01-30	Initial commit to populate CoreCLR repo	dotnet-bot	1	-0/+2128
	[tfs-changeset: 1407945]