bulk88
bulk88
> Was there ever a time that you could successfully build perl without specifying CCHOME if "CCHOME" is not the default "C:\MinGW" ? Yes I was able to. I just...
> Yes - both 5.30.0 and 5.32.0 build for me (with just gmake test, though there are some test failures. But 5,34,0 does not: I don't have an opinion if...
indents fixed, alpha sorted, replaced cargo culted comments, some of the macros, in my VC 2022 SDK (IDK how old it is), they exist, where MS Devs specifically say to...
> I don't have tuits to benchmark the change, but I looked at the timings of GitHub Actions runs on a few recent blead commits. > The numbers are pretty...
[win64_build_product_proc_times.pl.txt](https://github.com/user-attachments/files/17355645/win64_build_product_proc_times.pl.txt) Attaching timing, without the patch above, in floating point seconds, of building Win64 perl, 1 core was used/not parallel. 600-1000 ms per .c seems high, and its perl specific,...
Should this large set macros be made a public feature like ```PERL_NO_GET_CONTEXT``` or less relevant, ```NO_XSLOCKS```, be documented maybe ```PERL_NO_GUI_H``` or ```PERL_NO_W32_GUI``` or ```PERL_NO_W32_GUI_H``` for XS devs/CPAN? and sprinkle it...
Some research, I am not the only person complaining `#include ` is unacceptable bloatware for compile times. Other FOSS are very unhappy at the amount of child `.h` files automatically...
> I strongly suspect @tsee tested this with a micro-benchmark, but I do not know what benchmark was used. Without researching, (correct this if I am wrong) I think pp_add()...