Upgrade frontend & libs to v2.102.1 #4323
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Remove global `@system:` annotations from C headers * Implement DIP1035 - system variables
Having source file decoding in part of parse is a bit of a stretch: Module should not care where the source file comes from, only that it is fed valid code. For example, when using DMD as a library, one might want to directly provide 'string' to Module, hence the coupling with ubyte[] is hindering this. Splitting this code in its own function is a step towards removing the coupling, and eventually moving this closer to file-handling routines rather than parsing routines.
…be in XMM0 register (dlang/dmd!14568)
merge stable Signed-off-by: Nicholas Wilson <thewilsonator@users.noreply.github.com> Merged-on-behalf-of: Nicholas Wilson <thewilsonator@users.noreply.github.com>
That behavior was introduced when `in` was equivalent to `const`, which is no longer the case and will cause issues when `in` enforces `scope`.
…ng/dmd!14562) * Fix issue 22306 - scope array variable should be stack allocated * Update changelog/scope-array-on-stack.dd Co-authored-by: Max Haughton <maxhaton@gmail.com> Co-authored-by: Max Haughton <maxhaton@gmail.com>
…580) Fixes incorrect fix for https://issues.dlang.org/show_bug.cgi?id=19788
… assignment Fix issue 13060. Signed-off-by: Luís Ferreira <contact@lsferreira.net>
* test * add integer vector comparisons
…atch any overload
…tance doesn't match any overload
…ution failure Show expression, not just identifier. Show candidates.
…xceptions from finalizers A v2.102 regression, which newly enabled `StackTrace` constructions from within GC finalizers. The construction is `@nogc`, but apparently depends on the `typeid(StackTrace)` monitor having been allocated already, i.e., a previous `StackTrace` construction. So pre-allocate a dedicated mutex in the module constructor to make the `StackTrace` construction really `@nogc`. `druntime/test/allocations/src/alloc_from_assert.d` then passes on Windows again (not tested by DMD, but by LDC). While at it, also prevent `InvalidMemoryOperation` errors when trying to print exceptions within finalizers - by not resolving anything (=> empty printed trace), as resolving currently heavily depends on the GC.
… to a link-time address (dlang/dmd!14657) * Fix issue 23514 - Incorrect compilation when adding a 64-bit constant to a link-time address The current cast to int causes a loss of precision, which can result in incorrect compilation. * Add test23514.d * Enable optimization in test * Improve test case * Use ulong instead of size_t * Restrict test to 64-bit targets * Re-enable test for 32-bit targets * Disable test for win64 and add comment
|
Alright, just 2 remaining dmd-testsuite failures on FreeBSD, with enabled optimizations only: |
|
Oh and looks like the macOS-arm64 CI jobs don't hang anymore for some druntime integration test. :) |
…hrowing exceptions from finalizers (dlang/dmd!14901) * Fix Issue 23731 - InvalidMemoryOperation error on Windows when throwing exceptions from finalizers A v2.102 regression, which newly enabled `StackTrace` constructions from within GC finalizers. The construction is `@nogc`, but apparently depends on the `typeid(StackTrace)` monitor having been allocated already, i.e., a previous `StackTrace` construction. So pre-allocate a dedicated `Mutex` in the module constructor to make the `StackTrace` construction really `@nogc`. `druntime/test/allocations/src/alloc_from_assert.d` then passes on Windows again (not tested by DMD, but by LDC). While at it, also prevent `InvalidMemoryOperation` errors when trying to print exceptions within finalizers - by not resolving anything (=> empty printed trace), as resolving currently heavily depends on the GC. * [work around cyclic modules dependency...] * druntime: Test test/allocations/src/alloc_from_assert.d on Windows too As it regressed with v2.102.
kinke
force-pushed
the
merge-2.102
branch
5 times, most recently
from
e060df4
to
19b56e7
Compare
These 2 tests regressed with v2.102 with enabled optimizations; the tests themselves are unchanged. I guess some druntime change broke them, but doubt the tests were ever really robust with FreeBSD's libexecinfo, which doesn't seem to cope well with elided frame pointers at all - at least with CI-tested FreeBSD 12.
kinke
changed the title
This is important for CTFE-string-appending etc. for targets without proper druntime support, such as WebAssembly. See ldc-developers#4324 for an examplary breakage caused by the hook addition in D v2.101, rendering dub totally unusable for such targets. In particular, skip all the `-profile=gc` stuff when not using that cmdline option.
… `-profile=gc` (dlang/dmd!14914) * druntime: Only define _d_arraysetlengthTTrace when compiling with -profile=gc Analogous to dlang/dmd!14912, and covered by druntime/test/profile/src/profilegc.d too. * druntime: Guard more stuff behind `version (D_ProfileGC)` Keeping the templated hooks lean.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.