-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[release/6.0] Add alignment to mapped field stream #64559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-reflection-metadata Issue DetailsBackport of #63305 to release/6.0 /cc @davidwrighton Customer ImpactTestingRisk
|
|
@jaredpar Jared, would it be possible to run some Roslyn tests to ensure that Roslyn doesn't experience any unexpected failures with this change? |
|
We need to add the project changes to version this and build it. To the SRM src csproj add <GeneratePackageOnBuild>true</GeneratePackageOnBuild>
<ServicingVersion>1</ServicingVersion> |
I went ahead and did this. |
| <TargetFrameworks>$(NetCoreAppCurrent);netstandard2.0;net461</TargetFrameworks> | ||
| <Nullable>enable</Nullable> | ||
| <IsPackable>true</IsPackable> | ||
| <GeneratePackageOnBuild>true</GeneratePackageOnBuild> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW the versioning info here
steveharter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified it's a direct port of 7.0
bf30f14 to
c273161
Compare
|
Failures are known. |
Backport of #63305 to release/6.0
/cc @davidwrighton
Customer Impact
Enable development of the
CreateSpan<T>support feature within the Roslyn compiler during the .NET 7 timeframe. For complex packaging reasons, the Roslyn compiler cannot take a dependency on bug fixes added to in a development release of the .NET system, so fixes required to develop vNext Roslyn need to be backported to a servicing release of .NET.Testing
The backport includes tests to validate that the MappedFieldStream is aligned as it should be.
Risk
Low risk. This will change the output of various compilers by adjusting padding, but not in a way which is concerning. The Roslyn team has confirmed that this sort of difference is acceptable.