Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Clean up runtest script #8

Closed
wants to merge 1 commit into from
Closed

Clean up runtest script #8

wants to merge 1 commit into from

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Feb 2, 2015

Gets rid of a "cannot find file specified" error message when running from a clean enlistment, fixes a spacing issue and a "cyclic copy error" xcopy issue.

Gets rid of a "cannot find file specified" error message when running from a clean enlistment, fixes a spacing issue and a "cyclic copy error" xcopy issue.
@ramarag
Copy link
Member

ramarag commented Feb 2, 2015

this has been done as part of my earlier change see - #4
more specifically - https://github.com/dotnet/coreclr/pull/4/files#diff-adec353b8bdbfa8c549ed738939291e8R107

@mmitche mmitche closed this Feb 2, 2015
@mmitche mmitche deleted the get-rid-of-cannot-find-file-error branch February 2, 2015 22:12
richlander added a commit to richlander/coreclr that referenced this pull request Apr 8, 2015
kyulee1 added a commit to kyulee1/coreclr that referenced this pull request Mar 14, 2016
When zero-initializing locals, JIT emits wrong instruction sequence --
e.g, 28 byte zero-intialization as shown below.
The issue was JIT passed wrong arguments to emitIns_R_R_I.

Before (Fail)
```
 stp     xzr, xzr, [x2],dotnet#16
 str     xzr, [x2,dotnet#2]  --> just two byte offset (no x2 post-increment)
 str     wzr, [x2]
```

After (Pass)
```
 stp     xzr, xzr, [x2],dotnet#16
 str     xzr, [x2],dotnet#8
 str     wzr, [x2]
```
jashook referenced this pull request in jashook/coreclr Dec 1, 2017
# This is the 1st commit message:

Remove CoreFX runtest dependency

This change will start using build-test.sh generatelayoutonly to build
the coreoverlay directory for use with runtest.sh.

# This is the commit message #2:

Missing ./

# This is the commit message #3:

Fix untar location

# This is the commit message #4:

Use portable builds

# This is the commit message #5:

Get ci green

# This is the commit message #6:

Small changes

# This is the commit message #7:

Small changes

# This is the commit message #8:

Small changes

# This is the commit message #9:

Add generateonly builds.sh

# This is the commit message #10:

Ensure correct test location

# This is the commit message #11:

netci change

# This is the commit message #12:

netci change

# This is the commit message #13:

Working on setting up build-test

# This is the commit message #14:

Remove generatelayoutonly

# This is the commit message #15:

Undo some of the changes to use generatelayoutonly

# This is the commit message #16:

Correctly remove build-test.sh invocation

# This is the commit message #17:

Fix build-test generatelayoutonly

# This is the commit message #18:

Fix a few netci issues
sbomer pushed a commit to sbomer/coreclr that referenced this pull request Jun 19, 2018
josalem pushed a commit to josalem/coreclr that referenced this pull request May 31, 2019
* add env var for varying number of tracers
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
When zero-initializing locals, JIT emits wrong instruction sequence --
e.g, 28 byte zero-intialization as shown below.
The issue was JIT passed wrong arguments to emitIns_R_R_I.

Before (Fail)
```
 stp     xzr, xzr, [x2],dotnet/coreclr#16
 str     xzr, [x2,dotnet/coreclr#2]  --> just two byte offset (no x2 post-increment)
 str     wzr, [x2]
```

After (Pass)
```
 stp     xzr, xzr, [x2],dotnet/coreclr#16
 str     xzr, [x2],dotnet/coreclr#8
 str     wzr, [x2]
```


Commit migrated from dotnet/coreclr@59ea856
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants