Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@cherusker
Copy link
Contributor

Finally, I can make peace with the past (x) and close this chapter :)

(x) While working on #5191, I realised that MONO_NO_SANITIZE_THREAD was not precise enough for most use cases. The first try to fix this (#5255) was not right for mempool.c, however, #5310 finally brought an applicable solution.

@dnfclas
Copy link

dnfclas commented Aug 16, 2017

@cherusker,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

…perations

- avoid blacklisting whole functions with `MONO_NO_SANITIZE_THREAD`
- change `long` to `gint64` as it is more portable
@cherusker cherusker force-pushed the cherusker-2017-08-16-mempool-making-peace-with-the-past branch from bf13cf7 to 7eda8bd Compare August 16, 2017 19:12
@lewurm lewurm merged commit aa7cd58 into mono:master Aug 17, 2017
@cherusker cherusker deleted the cherusker-2017-08-16-mempool-making-peace-with-the-past branch August 17, 2017 09:10
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…perations (mono/mono#5387)

- avoid blacklisting whole functions with `MONO_NO_SANITIZE_THREAD`
- change `long` to `gint64` as it is more portable

Commit migrated from mono/mono@aa7cd58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants