| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Add -msse2 compile option
Cherry-pick of https://github.com/dotnet/runtime/pull/33135
* Use prefixed hex format in asm
Cherry-pick of https://github.com/dotnet/runtime/pull/33205
* [Tizen] Add CoreCLR tests build dependencies v3.1.3 for x86
* [Tizen] Add CoreCLR tests build dependencies v3.1.3 for x64
* [Tizen] Allow build of tests for x86/x64
|
|
Signed-off-by: Timur <t.mustafin@partner.samsung.com>
|
|
Signed-off-by: Timur <t.mustafin@partner.samsung.com>
|
|
This allows to perform build for different arches in the same repository
|
|
|
|
- CLRTest.CrossGen.targets is used as a template for crossgen part of individual test script
- runtest.sh is used for launching tests
|
|
|
|
Cherrypick only test parts of below patches in public dotnet/runtime github
- be8e050a6d27040d6c249382d99d57d973e919b2 Implement instantiating and unboxing through portable stublinker code… (#106)
- 0e949491faee53d2a7ad4d5649be17e98e5d3a96 Some minor ABI stress improvements
- 3f339687a8151e989bbb4673aab9b0abcddf5642 Mark emitted types assembly as collectible in ABI stress (dotnet/coreclr#26253)
- a25dd1a45b6fdad114ffaa915550906c986aa1ca Remove redundant ABI stress tests (dotnet/coreclr#26183)
- 57945676a6395da61b61ce427a055e77d330db86 Fix GenerateShuffleArray to support cyclic shuffles (dotnet/coreclr#26169)
- 3b0ba1ee24823030a3fc7278dd064d24a49a90bb Add ABI stress tests (dotnet/coreclr#26090)
|
|
|
|
* Fix PIE options
We were missing passing the -pie linker option. That means that while we
were compiling our code as position independent, the executables
(not shared libraries) were not marked as position independent and
ASLR was not applied to them. They were always loaded to fixed addresses.
This change adds the missing -pie option and also replaces all the individual
settings of -fPIE / -fPIC on the targets we build by a centralized setting
of CMAKE_POSITION_INDEPENDENT_CODE variable that causes cmake to add the
appropriate compiler options everywhere.
* Fix native parts of coreclr tests build
The native parts of the tests are not built using the root CMakeLists.txt
so I am moving enabling the position independent code to configurecompiler.cmake
Change-Id: Ieafff8984ec23e5fdb00fb0c2fb017e53afbce88
|
|
|
|
|
|
|
|
runtest.sh
|
|
* Fail to explicitly tail call on x86 unix.
* Correctly return 100
* Correct return value
* Add noway assert in morphTailCall to avoid morphing slow tail calls on unix.
* Address feedback
|
|
This is the fix for #27924. This is a GC hole bug that was found externally, #27590.
The cause is that the JIT was using the target type of the subtract when it needed
to make a copy of the source, but it needs to use the source type.
## Customer Impact
Corruption of state that is non-deterministic and hard to track down.
## Regression?
Not a recent regression, but exposed by Unsafe.ByteOffset.
## Testing
The fix has been verified in the runtime repo.
## Risk
Low: The fix is straightfoward and only impacts 3 lines of code.
|
|
|
|
* Port PR #258 to 3.1
* Fix test proj file
|
|
* Port the 5.0 fix for issue #1104 3.1
- Pull Request Runtime\#1734
- This change corrects a cut-and paste typo with a previous commit.
- Includes test case Runtime_1104.cs
* Updated the csproj to use 3.1 syntax
|
|
(#27996)
|
|
* [release/3.1] Port fix for JIT silent bad code
Release/3.1 port of https://github.com/dotnet/runtime/pull/797.
Fixes https://github.com/dotnet/runtime/issues/764
The jit might incorrectly order a read from a struct field with an operation
that modifies the field, so that the read returns the wrong value.
Silent bad code; program behaves incorrectly.
Yes, introduced in the 3.0 cycle.
Verified the user's test case now passes; no diffs seen in any existing framework
or test code.
**Low**: the jit is now spilling the eval stack entries to temps in cases where it
did not before; this should be conservatively safe.
cc: @brucefo
____
If we're appending an assignment whose LHS is is a location within a local
struct, we need to spill all references to that struct from the eval stack.
Update the existing logic for this to handle the case where the LHS is a field
of a local struct, and the field is updated by unusual means (here, `initobj`).
Fixes dotnet/runtime#764.
* Fix test
|
|
Fix for #27923
The jit might fail to locate a class handle for a ref class, leading to an
unexpected crash while jitting.
## Customer Impact
Unexpected and hard to diagnose crash/exception
## Regression?
Yes, introduced during the development 3.0 cycle. 2.x behaves correctly.
## Testing
Verified the user's test case now passes; no diffs seen in any existing
framework or test code.
## Risk
**Low**: the jit will now fall back to using the handle for System.Object if no
better option can be found.
cc @BruceForstall
____
In some cases we may end up in lvaSetClass without a valid ref class handle
from either the IR or the stack. Use the handle for object as a conservative
fallback.
|
|
* Change non_virtual_calls_to_instance_methods test to non-il-sdk format
* Work around maxpath hit by method name
* Fix compile item to short file name
|
|
interface methods (#27756) (#27868)
* est for non_virtual_calls_to_instance_methods
* Fix handling of callvirt to instance methods on interface types that are not virtual
- Use call type to indicate if its non-virtual or not, instead of opcode
* Use ilproj to protect against future C# compiler changes
- This test needs to test the use of specific opcodes, and so an IL proj is required
|
|
* Add fix for restore of ilasm
The restore logic in buildtools tried to use a netcoreapp2.1 TFM for Linux-musl.
This ended up restoring Linux-x64 binaries which then broke the test build.
This change works around this by saving a copy of the depproj that BuildTools used into
the tree and restore it as a 3.0 app manually in init-tools on our side of the build.
* Change to a 3.0 SDK for servicing
|
|
|
|
|
|
|
|
Port https://github.com/dotnet/coreclr/pull/27210 to release/3.1
|
|
* Update dependencies from https://github.com/dotnet/corefx build 20190903.6
- Microsoft.NETCore.Platforms - 3.0.0-rc1.19453.6
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-rc1.19453.6
* Update dependencies from https://github.com/dotnet/corefx build 20190904.8
- Microsoft.NETCore.Platforms - 3.0.0-rc1.19454.8
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-rc1.19454.8
* Update dependencies from https://github.com/dotnet/corefx build 20190906.2
- Microsoft.NETCore.Platforms - 3.1.0-preview1.19456.2
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-preview1.19456.2
* changing the target framework for tests to 3.1
* Update dependencies from https://github.com/dotnet/corefx build 20190906.20
- Microsoft.NETCore.Platforms - 3.1.0-preview1.19456.20
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-preview1.19456.20
* Update dependencies from https://github.com/dotnet/corefx build 20190907.5
- Microsoft.NETCore.Platforms - 3.1.0-preview1.19457.5
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-preview1.19457.5
* Update dependencies from https://github.com/dotnet/corefx build 20190909.13
- Microsoft.NETCore.Platforms - 3.1.0-preview1.19459.13
- Microsoft.Private.CoreFx.NETCoreApp - 4.7.0-preview1.19459.13
* 3.0 -> 3.1
|
|
before the SIMDScalar handling. (#25905) (#25987)
* Ensure that we check for implicit ivals for single argument intrinsics before the SIMDScalar handling.
* Adding test template entries for the unary overloads of the Sse41.Round functions
* Regenerating the hardware intrinsic test templates.
|
|
* Make a dedicated polling thread for EventCounters
* Cleanup
* remove debug prints
* nit
* Fix comment
* addressing issues from code review
* Fix an assertion from getting fired when we have multiple listeners
* Fix a test issue
* code review feedback
* Fix a potential deadlock
* Fix another deadlock
* Allow s_sleepDurationInMilliseconds to be reset to a larger value
* More issues fix
* Let thread wake up from sleep if needed
* Some suggestions for the counters fix.
The resulting behavior should be the same as what is there now (assuming I didn't mess anything up), these are all just code simplifications that hopefully make it easier to review and maintain going forward. In total I think this reduces the change size in CounterGroup.cs by ~30%.
- With the addition of the AutoResetEvent the ManualResetEvent is no longer needed, removed it.
- Removed the various if foo != null checks for the shared state, it is all initialized once when then thread is created and then assumed to be non-null elsewhere.
- Removed a 2nd lock acquisition inside OnTimer
- Replaced an if with Math.Min in PollForValues
* fix test
|
|
* Do not fast tail call if caller has multislot structs
* apply patch
* Address offline feedback
|
|
* Fix issue 25709
* rename
* Fix regression test
* cleanup
* Code review feedback
* set maxincrement to 3
* test fix
|
|
(#25747)
Related to https://github.com/dotnet/coreclr/issues/25690
Port of https://github.com/dotnet/coreclr/pull/25746
|
|
|
|
* Add Microsoft.Diagnostics.Tools.RuntimeClient to dependencies.props
* add EventPipe tests for provider coherence, buffer size resilience, and rundown event presence
|
|
* refresh GC reliability tests
* Update stress instructions (PR feedback)
|
|
|
|
- Microsoft.NETCore.Platforms - 3.0.0-preview8.19354.4
- Microsoft.Private.CoreFx.NETCoreApp - 4.6.0-preview8.19354.4
* Disable failing test
|
|
|
|
parameters (#25558)
* Fix instantiation stub maker for case where no register is used by function parameters
|
|
* Enable coredumps on unix
* Remove morph change
|
|
|
|
https://github.com/dotnet/corefx/pull/38856 (#25389)
|
|
|
|
|
|
Plus, add comments to the new exclusion file
|
|
Re-enable corefx tests
|
|
|
