-
Notifications
You must be signed in to change notification settings - Fork 419
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
Windows builds for macro targets in release mode break the compiler #2483
Comments
Tracked in Apple’s issue tracker as rdar://122442648 |
Is this something that was already known? I can't seem to see the issue via the link |
You're not supposed to - that's Apples internal bug tracking system, so presumably they filed (or had) an internal issue covering the same problem. |
@compnerd Have you seen this before? |
I have not - might be interesting to get this under a debugger. |
@compnerd If I can assist in any way feel free to instruct me. If you need additional logs or anything. |
What is really interesting is that we definitely would be building this file in release mode all the time - swift-syntax is part of the toolchain build and so we have this continuously building on Swift CI, GHA for The Browser Company's builds of the toolchain, and multiple developers building locally. |
Does building a macro package work in release mode for you locally? From what you said it sounds like? |
Could the difference be that you are building using CMake, @compnerd while @broken-bytes is building using SwiftPM? |
@ahoppen possible - that is a difference between the builds, though feels surprising. |
Not too surprising to be honest. I had a couple of issues with SPM whereas the same code with CMake worked. Cxx interop, for example. |
Description
Issue
When building any macro target on Windows in release mode, the Swift Compiler gets hung.
The last output with
-vv
set is always-o F:\Projects\MacroTest\.build\x86_64-unknown-windows-msvc\release\SwiftSyntax.build\SyntaxTypeNodes.swift.o
.Test setup
Steps to Reproduce
The text was updated successfully, but these errors were encountered: