-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Address Sanitizer support in CoreCLR #74623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
e0c4a60
6fc2555
d7fe870
007da09
8d3615d
92c4858
a1f9900
2978de4
203e70c
eb9bf22
413410b
da30efe
b99fab9
cd167b3
8fcc66f
931f444
6732866
3c7dd54
04d2d9f
97c848f
9946108
982e701
6239952
6769613
35d9bd7
8b19fd3
5ae90d3
647f73b
5873281
d996328
2e452d4
2130d7b
dc26f51
6cc6ad8
591093e
d285048
7187ff2
6448d19
113f5b2
11cccdf
c0357af
133e99b
b863d6f
8a51e72
98ed710
4efdf96
6855c78
db5b069
6383866
0f0fdf5
36a450e
f6987ed
619966b
929a042
5913ca4
b8b3762
c2433e5
fa15f17
757a329
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,10 +13,7 @@ | |
|
|
||
| <PropertyGroup> | ||
| <CrossDir></CrossDir> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition="'$(BuildArchitecture)' != '$(TargetArchitecture)'"> | ||
| <CrossDir Condition="'$(TargetArchitecture)' == 'arm' or '$(TargetArchitecture)' == 'arm64' or '$(TargetArchitecture)' == 'armel'">x64</CrossDir> | ||
| <CrossDir Condition="'$(TargetArchitecture)' == 'x86'">$(BuildArchitecture)</CrossDir> | ||
| <CrossDir Condition="'$(CrossBuild)' == 'true' or '$(BuildArchitecture)' != '$(TargetArchitecture)'">$(BuildArchitecture)</CrossDir> | ||
| </PropertyGroup> | ||
| <!-- If we're building a sanitized build, we need to use an unsanitized build of crossgen2's native components since we run crossgen2 here with a non-sanitized dotnet host. --> | ||
|
||
| <PropertyGroup Condition="'$(BuildArchitecture)' == '$(TargetArchitecture)' and '$(EnableNativeSanitizers)' != ''"> | ||
jkoritzinsky marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like we're depending on the cross-targeting components whenever we are building sanitized runtime, but I don't understand what the two have to do with each other. It seems like it should be possible to do a sanitized runtime build without requiring the cross-tools. Or is the idea that we build the tools once sanitized, and use the cross-tools build to build the same tools unsanitized?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cross-tools are used in the build process with the downloaded CLI. When we build the sanitized tools, we can't load them into an unsanitized process easily across all platforms, so we build the tools that need to be loaded into the build process in the same way we do when we do a cross build.