| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
* Update contributor docs
* Update
* Added up-for-grabs and ports
* Update binary licensing
* Update\
* Simplify developer workflow doc
* Update per feedback
|
|
|
|
Factor in additional exception cases from Andy and fix some wording from
Joe.
|
|
|
|
* Add GC Reliability Framework CI job
* Three changes:
1) To address offline feedback, update the CI trigger phase document
and the GC testing instructions
2) Set the timeout for GC RF CI jobs to 24 hours, so they don't time
out (they will run for 15 hours by default)
3) Refactor "scenario == 'gc_reliability_framework' to its own method
so that new GC RF scenarios can easily and cleanly be added if
desired in the future
|
|
|
|
|
|
|
|
|
|
|
|
Fixed "with heap" option to actually include all the heaps. The way /proc/$pid/maps
was parsed missed most of the RW data/heap regions.
Added -u/--full full core dump options.
Removed the useless m_memStatus variable in enummem.cpp.
|
|
|
|
Remove support for the x86 compat JIT from .NET Core.
|
|
Add instructions for running local perf tests
|
|
|
|
|
|
These changes remove support for the x86 compat JIT from the build, the
runtime, and the various perf/test scripts.
Fixes #10733, #10734.
|
|
Fix fgNewBBinRegion when inserting into filters.
|
|
* [ARM32] clang 3.9 as a default for ARM cross build
Use clang 3.9 as a default compiler for ARM cross build
* Both arm and armel will be built using clang 3.9 as a default
* ARM CI will use clang 3.9 as a default
* ARM pipieline build will use clang 3.9 as a default
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
* [ARM32] Update docs describing clang-3.9 and ARM cross build
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
* [ARM] Check minimum version requirement of clang for ARM cross build
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
In order to ensure that the GC operates properly when handling
exceptions, the CLR ABI requires that control exits a filter region
throguh its terminal instruction. `fgNewBBinRegion` was violating this
invariant, however, which lead to GC stress failures when the GC was
invoked immediately after a filter finished executing but before control
entered any handlers. This change fixes the behavior of
`fgNewBBinRegion` when inserting new blocks into filter regions.
There are two cases to consider when inserting a new BB into a filter
region:
1. The filter region consists of multiple blocks
2. The filter region consists of a single block
The first case is straightforward: instead of inserting a new BB after
the last block of the filter, insert it before the last block of the
filter. Because the filter contains multiple blocks, the predecessor of
the filter must also be in the filter region.
The latter case requires splitting the single block, as inserting a new
block before the single block would otherwise change control flow (the
filter would begin with the new block rather than the single block). In
order to acheive this with minimal complexity, this change first inserts
a `BBJ_ALWAYS` block that transfers control to the existing single
block, then inserts a second new block immediately before the existing
single block. The second new block is then returned. To put it
visually, the transformation is from this:
```
filter start: BBN (BBJ_EHFILTERRET)
```
to this:
```
filter start: BBN + 1 (BBJ_ALWAYS -> BBN)
BBN + 2 (jumpKind)
BBN (BBJ_EHFILTERRET)
```
and the function returns `BBN + 2`.
Fixes VSO 406163.
|
|
Uses the createdump utility code as a library.
Changed the "-m, --micro" option to "-t, --triage".
Lots of cleanup.
|
|
Change default minidump type to MiniDumpWithPrivateReadWriteMemory.
Remove language about uploading triage dumps.
Turn off diagnostic output.
|
|
Add the Linux minidump support documentation
One minor fix to createdump.
|
|
Update Viewing JIT dumps to 2.0 and csproj
|
|
Updated link referenced in CI builds; old link was broken
|
|
|
|
|
|
- None of the badge links were correct, resulting in every badge always showing
as "Building" regardless of actual status
- The OSX badge links would 404.
- We were still using shields.io badges, which have been unreliable.
I've fixed all of these.
|
|
A few small changes to make it easier to compare selections in the
installer UI against the list in the doc:
- Re-order the list to match the order presented in the installer UI
- Place the individual items under groupings matching the installer
- Change casing to match installer UI
|
|
|
|
The List.cs link is broken in contributing.md. This PR updates the link to List.cs accordingly.
Fix #10822
|
|
* remove fedora 23
* Fedora rename
|
|
Fix class name in ryujit-overview.md
|
|
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
|
|
Document describes an initial approch to enregistering local variables
that live across EH flow. Today the JIT forces all local vars that are live
across EH flow that kills all registers to live on the stack. The transformation outlined ensures consistency on the stack across the EH kills but allows the enregistration with in either the normal flow of control or with in any EH handlers.
|
|
* Fix link for up-for-grabs issues
|
|
|
|
|
|
- Add Linux arm/x86 CI trigger phrases
- Add Ubuntu16.10 x64 pri0 trigger phrase
- Remove Ubuntu15.10 x64 pri0 trigger phrase
|
|
Add document on CLR Jump Stubs
|
|
|
|
GitHub recently changed how atx headings (beginning with `#`) are
rendered. A space is now required between `#` and the following text
for the heading to be recognized.
Update headings in the docs to match the expected format.
See https://github.github.com/gfm/#atx-headings
|
|
* Initial document on AssemblyLoadContext Design
|
|
Update CLR ABI PSPSym Section
|
|
|
|
for VS2017 and to clarify that MSDIA120.dll must be registered.
|
|
Updating the build scripts to support VS2017.
|
