Age | Commit message (Collapse) | Author | Files | Lines |
|
Port of #19156.
Avoid promoting structs that contain struct fields that themselves
wrap single simple fields, if those single simple fields are smaller
than their enclosing struct.
Otherwise we run the risk of losing track of the "extra" bytes in the
innner struct.
Addresses #19149.
|
|
Update CoreClr, CoreFx, PgoData to servicing-26724-06, servicing-26724-03, release-20180725-0038, respectively (release/2.1)
|
|
release-20180725-0038, respectively
|
|
|
|
Update CoreClr, CoreFx to servicing-26719-02, servicing-26719-03, respectively (release/2.1)
|
|
|
|
release-20180719-0105, respectively (#19014)
|
|
|
|
Update PgoData to release-20180717-0134 (release/2.1)
|
|
|
|
|
|
|
|
|
|
|
|
* Skip old time zones with offsets higher than 14h
* apply offline feedback
* fix braces
|
|
|
|
Update BuildTools, CoreClr, CoreFx, PgoData to rc1-03006-01, servicing-26708-02, servicing-26708-02, release-20180711-0041, respectively (release/2.1)
|
|
servicing-26708-02, servicing-26708-02, release-20180711-0041, respectively
|
|
|
|
Port the fix for Issue 17969 to Rel/2.1
|
|
servicing-26606-02, servicing-26703-08, release-20180706-0055, respectively
|
|
|
|
The MUSL implementation of sigaltstack checks that the ss.ss_size is
larger or equal than the MINSIGSTKSZ even when the ss_flags is set
to SS_DISABLE even though Linux man page for sigaltstack states that
when this flag is set, all other ss fields are ignored.
We were not setting the ss_size in this case and it was causing a memory
leak for each thread that has terminated on MUSL based Linux distros
like Alpine.
Glibc implementation doesn't check the ss_size when the SS_DISABLE is set
so the problem was really MUSL specific.
|
|
.NET Core 2.1.1
|
|
The MUSL implementation of sigaltstack checks that the ss.ss_size is
larger or equal than the MINSIGSTKSZ even when the ss_flags is set
to SS_DISABLE even though Linux man page for sigaltstack states that
when this flag is set, all other ss fields are ignored.
We were not setting the ss_size in this case and it was causing a memory
leak for each thread that has terminated on MUSL based Linux distros
like Alpine.
Glibc implementation doesn't check the ss_size when the SS_DISABLE is set
so the problem was really MUSL specific.
|
|
Port of #18348 to release/2.1
We need to make sure that if we reorder a callfinally during finally cloning
that the callfinally is actually the one being targeted by the last block in
the try range.
Closes #18332. Linked issue has some more detailed notes.
|
|
|
|
Reimplement most of Array.Clear in managed code using Span Clear helpers.
Fixes dotnet/corefx#29848
|
|
(#18667)
|
|
* Allow ILCodeVersion to fallback to default IL
For compat with profilers that used our APIs in unexpected ways we can allow
the ILCodeVersion to fallback to the default IL code when no IL was explicitly
given.
* Fix incorrect usage of ILCodeVersion::AsNode (issue #18602)
When the debugger is querying the active rejit IL for an IL method that has not been rejitted it incorrectly creates a VMPTR_ILCodeVersionNode for a code version that shouldn't have one.
|
|
|
|
Fixes #30263
|
|
|
|
(#18505) (#18526)
macOS 10.12+ supports clock_gettime (HAVE_CLOCK_MONOTONIC is defined)
However, mach_absolute_time has better resolution and should be used
as the primary clock source.
|
|
In anticipation of taking a dependence on netcoreapp2.1 for the
forthcoming PMI work from jitutils.
Also make sure to shut down build servers before cleaning up the SDK.
|
|
|
|
|
|
|
|
For some reason, the Alpine docker container running on a SELinux host maps
heap as RWX. When we allocate alternate stack from the heap, we also
change the protection of the first page to PROT_NONE so that it can
serve as a guard page to catch stack overflow. And when we free the
alternate stack, we restore the protection back to PROT_READ |
PROT_WRITE. The restoration fails in Alpine docker container running on
a SELinux host with EPROT failure and the SELinux log reports that an
attempt to change heap to executable was made. So it looks like the
kernel has added the PERM_EXEC to the permissions we have passed to the
mprotect call. There is a code in the mprotect implementation that can
do that, although I don't fully understand the conditions under which it
happens. This is driven by the VM_MAYEXEC flag in the internal VMA block
structure.
To fix that, I've modified the alternate stack allocation to use mmap /
munmap instead of C heap allocation.
|
|
StompWriteBarrier(WriteBarrierOp::StompResize) on ARM (#18107)
|
|
in PAL and GC on ARM and ARM64
|
|
|
|
|
|
|
|
Update CoreClr, CoreFx, PgoData to rtm-26515-07, rtm, release-20180529-0037, respectively (release/2.1)
|
|
|
|
respectively
|
|
release-20180514-0049, respectively (#17987)
|
|
Port build-test.sh changes from master to release/2.1
|
|
* Split unix test builds in slices
Ports #17161 to linux
* Address review feedback
|