This patch mirrors the change made to the Unix equivalent in
r351916. This in turn fixes bugs related to the use of FileOutputBuffer
to output to "-", i.e. stdout, on Windows.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm wondering why it wasn't caught by a Windows bot if I missed it for Windows. Could you write a test that fails currently and passes after this change?
Comment Actions
The stdout.s test you added in fact failed on Windows because this change was missing, and @thakis disabled it in rL351949. So, I think we can just re-enable stdout.s to test this.
Yes, I was going to re-enable this test in a separate patch (as it's in LLD) and perhaps revert the changes to the WASM tests too. It was these WASM test failures that got me looking into this issue in the first place.