bulk88
bulk88
> Doing this showed a small issue > > ``` > util.c: In function ‘void Perl_set_context(void*)’: > perl.h:6412:26: warning: ‘nonnull’ argument ‘t’ compared to NULL [-Wnonnull-compare] > 6412 | STMT_START...
struct XPVNV ``` HV* xmg_stash; 0X0 union _xmgu xmg_u; 0X4 STRLEN xpv_cur; 0X8 union { STRLEN xpvlenu_len; 0XC } xpv_len_u union _xivu xiv_u ; 0x10 union _xnvu xnv_u; 0x14 BADDDDD...
same here, I wouldnt optimize very hard for ```__float128```, its an exotic build option, and no cpu in the world currently implements the type in hardware, so ```__float128``` is always...
I dont see anything very wrong with this current commit, I recommend applying it to blead. Only concern is I see the possibility of sneaking in a 32b wide ghost...
What happens to path #4 of a version object, the `4.4.3_001` syntax.
> - ex-const v ->- > - ex-const v ->4 Are these ghost OP structs that were optimized away, in tearms of they will never enter the runloop, but they...
you mean maybe that const IVs and const NVs and very tiny PVXes that fits in 4/8 bytes, w/o null chars, all 3 things being directly stored in the OP's...
Under the original design concept of iperlsys.h all of these are supposed to be public API and all CPAN XS module are supposes to use these macros instead of using...
repushed __debugbreak_int3 prototype was wrong
Prefer GCC calller's address API first even on Win32, use official MS API 2nd on Win32. Improve last resort fallback for all OSes. Add test that the macro works and...