[Mingw-w64-public] [PATCH 2/2] genpeimg: add support for ARMNT and ARM64 images.

2021-08-03 Thread Jeremy Drake via Mingw-w64-public
Signed-off-by: Jeremy Drake --- mingw-w64-tools/genpeimg/src/img_pe.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/mingw-w64-tools/genpeimg/src/img_pe.c b/mingw-w64-tools/genpeimg/src/img_pe.c index e7ecbcd5b..345fc4e44 100644 --- a/mingw-w64-tools/genpeimg/src/img_pe.c

[Mingw-w64-public] [PATCH 1/2] genpeimg: update DLL characteristics flags

2021-08-03 Thread Jeremy Drake via Mingw-w64-public
Added high-entropy-va and control-flow-guard flags. Also fixed an apparent copy-paste error on posix subsystem, and added numeric value to XBOX subsystem for consistency with the others. Signed-off-by: Jeremy Drake --- mingw-w64-tools/genpeimg/src/genpeimg.c | 12 +++- mingw-w64-tools/g

[Mingw-w64-public] [PATCH 0/2] Update genpeimg

2021-08-03 Thread Jeremy Drake via Mingw-w64-public
I was recently looking for an open-source tool to change the subsystem of an executable. I came across genpeimg, and it looks like this would be a good addition to it. First, though, I wanted to get it updated with the latest Windows changes: new DLL characteristcs flags, and new image machine ty

[Mingw-w64-public] Please add noexcept to __acrt_iob_func and __iob_func

2021-08-03 Thread sotrdg sotrdg
further hack things around wincrt. · tearosccebe/fast_io@86ef492 (github.com) The problem is that the compiler will generate unwind code and __clang_terminate() for the code which should not generate. Just

Re: [Mingw-w64-public] [PATCH] Use __builtin_frame_address on Clang.

2021-08-03 Thread Jeremy Drake via Mingw-w64-public
On Wed, 4 Aug 2021, Martin Storsjö wrote: > On Tue, 3 Aug 2021, Jeremy Drake wrote: > > > While debugging this, noticed ruby seems to make *extensive* use of > > setjmp/longjmp. Originally it was trying to use __builtin_setjmp but that > > was crashing around the setjmp call (maybe clang's __buil

Re: [Mingw-w64-public] [PATCH] Use __builtin_frame_address on Clang.

2021-08-03 Thread Martin Storsjö
On Tue, 3 Aug 2021, Jeremy Drake wrote: While debugging this, noticed ruby seems to make *extensive* use of setjmp/longjmp. Originally it was trying to use __builtin_setjmp but that was crashing around the setjmp call (maybe clang's __builtin_setjmp wants a different size of jmp_buf?). FWIW,

Re: [Mingw-w64-public] [PATCH] Use __builtin_frame_address on Clang.

2021-08-03 Thread Jeremy Drake via Mingw-w64-public
On Tue, 3 Aug 2021, Martin Storsjö wrote: > On Mon, 2 Aug 2021, Jeremy Drake via Mingw-w64-public wrote: > > > Ruby was running into a crash calling longjmp on a jmp_buf obtained by > > calling setjmp from a function that had previously called alloca. This > > was resulting in mingw_getsp returni

Re: [Mingw-w64-public] [PATCH] Use __builtin_frame_address on Clang.

2021-08-03 Thread Martin Storsjö
On Mon, 2 Aug 2021, Jeremy Drake via Mingw-w64-public wrote: Ruby was running into a crash calling longjmp on a jmp_buf obtained by calling setjmp from a function that had previously called alloca. This was resulting in mingw_getsp returning the *current* SP rather than the "frame address"/"bas