Skip to content

Conversation

@jacobly0
Copy link
Member

This is all of the expected 0.14.0 progress on #21530, which can now be postponed once this commit is merged.

This required rewriting the (un)wrap operations since the original implementations were extremely buggy.

Also adds an easy way to retrigger Sema OPV bugs so that I don't have to keep updating #22419 all the time.

@jacobly0 jacobly0 force-pushed the x86_64-rewrite branch 2 times, most recently from 7c4f115 to e42376a Compare February 13, 2025 06:01
@jacobly0 jacobly0 force-pushed the x86_64-rewrite branch 3 times, most recently from 3c7e964 to cb655cf Compare February 13, 2025 10:54
@andrewrk
Copy link
Member

Might want to enable the corresponding tests, which live in test/cases/safety/*

@jacobly0 jacobly0 force-pushed the x86_64-rewrite branch 5 times, most recently from 750522d to 847a4fd Compare February 15, 2025 01:21
This is all of the expected 0.14.0 progress on ziglang#21530, which can now be
postponed once this commit is merged.

This required rewriting the (un)wrap operations since the original
implementations were extremely buggy.

Also adds an easy way to retrigger Sema OPV bugs so that I don't have to
keep updating ziglang#22419 all the time.
I observed a stack overflow during x86_64 CodeGen in a debug compiler
compiled by the llvm backend.  This happens while compiling
`main.buildOutputType` due to the Air being nested almost 500 levels.
@andrewrk andrewrk merged commit e5174c7 into ziglang:master Feb 15, 2025
9 checks passed
@jacobly0 jacobly0 deleted the x86_64-rewrite branch February 15, 2025 22:12
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.

2 participants