dotnet/roslyn

Document compiler /determinism effect on generated assembly

Open

#10,321 opened on Apr 4, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-CompilersConcept-DeterminismDocumentationhelp wanted

Description

We should document the way a deterministic assembly records its timestamp.

Look for IMAGE_DEBUG_TYPE_REPRO in https://msdn.microsoft.com/en-us/windows/hardware/gg463119.aspx

Contributor guide

Tech stack
csharp
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic knowledge of PE file formatfamiliarity with Roslyn compiler
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Look into the Roslyn compiler's emission phase, specifically how deterministic assembly timestamps are handled. The documentation should refer to IMAGE DEBUG TYPE REPRO in the PE format. Check files like 'Emit.cs' or 'PEModuleBuilder.cs' in the Roslyn codebase for relevant code. The issue is old with no prior work, so start by reviewing the linked MSDN documentation and then explore Roslyn's source to understand the current implementation.