Skip to content

[release/6.0] Add alignment to mapped field stream - #64559

Merged
safern merged 4 commits into
release/6.0from
backport/pr-63305-to-release/6.0
Feb 8, 2022
Merged

[release/6.0] Add alignment to mapped field stream#64559
safern merged 4 commits into
release/6.0from
backport/pr-63305-to-release/6.0

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jan 31, 2022

Copy link
Copy Markdown
Contributor

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.

@ghost

Copy link
Copy Markdown

Tagging subscribers to this area: @dotnet/area-system-reflection-metadata
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #63305 to release/6.0

/cc @davidwrighton

Customer Impact

Testing

Risk

Author:github-actions[bot]
Assignees:-
Labels:

area-System.Reflection.Metadata

Milestone:-

@davidwrighton

Copy link
Copy Markdown
Member

@jaredpar Jared, would it be possible to run some Roslyn tests to ensure that Roslyn doesn't experience any unexpected failures with this change?

@ericstj

Copy link
Copy Markdown
Member

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>

@ericstj

Copy link
Copy Markdown
Member

need to add the project changes to version this and build it

I went ahead and did this.

@ericstjericstj added the Servicing-consider Issue for next servicing release review label Feb 1, 2022
@leecowleecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Feb 1, 2022
@leecowleecow added this to the 6.0.3 milestone Feb 1, 2022
<TargetFrameworks>$(NetCoreAppCurrent);netstandard2.0;net461</TargetFrameworks>
<Nullable>enable</Nullable>
<IsPackable>true</IsPackable>
<GeneratePackageOnBuild>true</GeneratePackageOnBuild>

Copy link
Copy Markdown
Contributor

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

@stevehartersteveharter left a comment

Copy link
Copy Markdown
Contributor

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

@akoeplinger
akoeplingerforce-pushed the backport/pr-63305-to-release/6.0 branch from bf30f14 to c273161CompareFebruary 7, 2022 22:44
@safern

Copy link
Copy Markdown
Member

Failures are known.

@safern
safern merged commit 69edc60 into release/6.0Feb 8, 2022
@safern
safern deleted the backport/pr-63305-to-release/6.0 branch February 8, 2022 02:09
@ghostghost locked as resolved and limited conversation to collaborators Mar 10, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@davidwrighton@ericstj@safern@steveharter@leecow@joperezr