Front page | perl.perl5.porters |
Postings from February 2014
On 28 February 2014 15:47, Nicholas Clark <nick@ccl4.org> wrote:
> On Tue, Feb 04, 2014 at 02:35:23PM -0800, Tony Cook via RT wrote:
>> On Mon Feb 03 23:34:31 2014, bulk88 wrote:
>> > 1. disabling pmc in miniperl can be done for all OSes, there is also
>> > the PERL_IS_MINIPERL macro, so no need to -D it
>>
>> Not trivially, platforms which use Makefile.SH use the same pp_ctl$(O) for both miniperl and the final perl.
>>
>> We'd need to what's done with op.c/opmini.c and perl.c/perlmini.c, and I don't think it's worth it.
>
> I'm not convinced that it's worth it either, given that
>
> 1) unlike Win32, it's not trivial to do this due to the re-use of pp_ctl$(o)
> 2) there doesn't seem to be any noticeable speed hit on *nix
>
>> > 2. ${^WIN32_SLOPPY_STAT} for Win32 miniperl only
>> >
>> > 3. /lib first on Win32 miniperl only
>
> These seem reasonable, but I don't even know how to do the first, so don't
> know how easy it is. The latter *is* easy, but it's 90% testing, which I can't
> do either.
>
> On the subject of testing (that I can't) as George's smoker is unhappy again,
> could someone on Win32 try out the branch smoke-me/nicholas/fake-pm_to_blib
> and verify that it still builds on Win32? (I think that it should work)
> It avoids the entire use of ExtUtils::MakeMaker and make for building about
> 80 of the "simple" pure-perl modules, so it should speed things up.
> Based on the experience of disabling PMCs, I hope that on Win32 it's quite a
> bit faster.
>
Yes, that builds and tests ok for me. And the build is visibly quicker
too. I didn't compare timings, but I didn't need to to see that it's
quicker -- always the best kind of speed-up! :-)
Thread Previous
|
Thread Next