Re^6: Perl 64-bit versions

Whilst it is possible to have multiple concurrent versions of Perl installed -- I have 5.8.9 32-bit and 5.10.1 64-bit -- and manage them using the windows alternative to shebang lines -- assoc/ftype/.pl/.pl8 -- I've tried it in the past and just find it a pain to work with. The multiple versions rather the extensions.

Whichever version I'm using, it always seems that the module I want to use is already installed everywhere but that version. The biggest pain is needing to work out which modules are pure perl and can just be copied over and which have a binary component that need proper installation.

Whilst the split between perl/lib and perl/site/lib has always seemed entirely pointless and arbitrary to me; maintaining a split between pure perl pacjages and those with a binary component seems like it would (have been) far more useful. Way to late now of course.

As an aside: do you perchance have a 64-bit 5.15.something installed anywhere? If so, could you try:

perl -wE"$v=''; vec( $v, 2**32, 1 )=1"
[download]

And see if the 31-bit limitation on vec has been lifted?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Re^6: Perl 64-bit versions Download Code

Replies are listed 'Best First'.
Re^7: Perl 64-bit versions by ikegami (Patriarch) on Mar 13, 2012 at 21:27 UTC
The biggest pain is needing to work out which modules are pure perl and can just be copied over and which have a binary component that need proper installation. Those in $arch (e.g. i686-linux-thread-multi) vs those that aren't. Perl can be setup to peek into the libs of previous version, and that's how it determines what's safe and what's not.	[reply]
Re^7: Perl 64-bit versions by ikegami (Patriarch) on Mar 13, 2012 at 21:31 UTC
Whilst the split between perl/lib and perl/site/lib has always seemed entirely pointless and arbitrary to me Well, it does allow you to get to a pristine core installation in seconds. Yeah, it's of limited value. But who cares.	[reply]
Re^7: Perl 64-bit versions by Tux (Canon) on Mar 13, 2012 at 16:23 UTC
That has always worked in 64bitint perls! Running perl-all -we $v="";vec($v,2**32,1)=1 : skipping 5.003 .. 5.13.11 : === base/perl5.14.0 5.014000 i686-linux-64int === base/tperl5.14.0 5.014000 i686-linux-thread-multi-64int-ld === base/perl5.14.1 5.014001 i686-linux-64int === base/tperl5.14.1 5.014001 i686-linux-thread-multi-64int-ld === base/perl5.14.2 5.014002 i686-linux-64int === base/tperl5.14.2 5.014002 i686-linux-thread-multi-64int-ld === base/perl5.15.0 5.015000 i686-linux-64int === base/tperl5.15.0 5.015000 i686-linux-thread-multi-64int-ld === base/perl5.15.1 5.015001 i686-linux-64int === base/tperl5.15.1 5.015001 i686-linux-thread-multi-64int-ld === base/perl5.15.2 5.015002 i686-linux-64int === base/tperl5.15.2 5.015002 i686-linux-thread-multi-64int-ld === base/perl5.15.3 5.015003 i686-linux-64int === base/tperl5.15.3 5.015003 i686-linux-thread-multi-64int-ld === base/perl5.15.4 5.015004 i686-linux-64int === base/tperl5.15.4 5.015004 i686-linux-thread-multi-64int-ld === base/perl5.15.5 5.015005 i686-linux-64int === base/tperl5.15.5 5.015005 i686-linux-thread-multi-64int-ld === base/perl5.15.6 5.015006 i686-linux-64int === base/tperl5.15.6 5.015006 i686-linux-thread-multi-64int-ld === base/perl5.15.7 5.015007 i686-linux-64int === base/tperl5.15.7 5.015007 i686-linux-thread-multi-64int-ld === base/perl5.15.8 5.015008 i686-linux-64int === base/tperl5.15.8 5.015008 i686-linux-thread-multi-64int-ld === /usr/bin/perl 5.014002 i586-linux-thread-multi Negative offset to vec in lvalue context at -e line 1. Exit status: 65280 === /pro/bin/perl 5.014001 i686-linux-64int-ld [download] Enjoy, Have FUN! H.Merijn	[reply] [d/l]
Re^8: Perl 64-bit versions by BrowserUk (Patriarch) on Mar 13, 2012 at 16:49 UTC
That has always worked in 64bitint perls! What is this (in your ouput?): `=== /usr/bin/perl 5.014002 i586-linux-thread-multi Negative offset to vec in lvalue context at -e line 1.` [download] And this (on mine): `C:\test>test -S=1 -L=12 5.014002 # +# perl version 1431374382 # +# offsets to vec 1070103942 224876390 1364159134 875710158 4060380287 # +# < 232 > 231 Negative offset to vec in lvalue context at C:/Perl64-14/site/lib/Bloo +m/Filter.pm line 206.` [download] Line 206 of Bloom::Filter: `# flip the appropriate bits on print(), vec($self->{filter}, $_, 1) = 1 foreach @{$self->_get +_cells($key)}; ## print() added` [download] perl -V: <Reveal this spoiler or all in this thread> With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply] [d/l] [select]
Re^9: Perl 64-bit versions by Eliya (Vicar) on Mar 13, 2012 at 18:50 UTC
I can confirm the problem for 4060380287, both with 5.14.2 and 5.15.8 (64-bit) `$ /usr/local/perl/5.14.2/bin/perl -we '$v=""; vec($v,4060380287,1)=1' Negative offset to vec in lvalue context at -e line 1. $ /usr/local/perl/5.15.8/bin/perl -we '$v=""; vec($v,4060380287,1)=1' Negative offset to vec in lvalue context at -e line 1.` [download] but not for 232 (and above — in which case it wraps around¹). Actually, it seems 231 .. 232-1 is buggy, though I haven't tested each and every one individually. For reference, my relevant config settings: ... Compiler: cc='gcc ', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasi +ng -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE - +D_FILE_OFFSET_BITS=64', optimize='-O2', cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -f +stack-protector -I/usr/local/include' ccversion='', gccversion='4.3.2 [gcc-4_3-branch revision 141291]', + gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=1 +6 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', + lseeksize=8 alignbytes=8, prototype=define ... Characteristics of this binary (from libperl): Compile-time options: HAS_TIMES MULTIPLICITY PERLIO_LAYERS PERL_DONT_CREATE_GVSV PERL_IMPLICIT_CONTEXT PERL_MALLOC_WRAP PERL_PRESERVE_IVUV PERL_USE_D +EVEL USE_64_BIT_ALL USE_64_BIT_INT USE_ITHREADS USE_LARGE_FILES USE_LOCALE USE_LOCALE_COLLATE USE_LOCALE_CTYPE USE_LOCALE_NUMERIC USE_PERLIO USE_PERL_ATOF USE_REENTRANT_API [download] ___ ¹ as I can find no mention in vec that the offset is limited to 32-bit on 64-bit builds, this could be considered a bug, too, even though it doesn't croak in this case. `$ perl -wE '$v=""; vec($v,232+42,1)=1; say "wrapped" if vec($v,42,1) +' wrapped` [download]	[reply] [d/l] [select]
Re^10: Perl 64-bit versions by BrowserUk (Patriarch) on Mar 13, 2012 at 18:53 UTC
Re^11: Perl 64-bit versions by Eliya (Vicar) on Mar 13, 2012 at 19:03 UTC
Some notes below your chosen depth have not been shown here
Re^9: Perl 64-bit versions by Tux (Canon) on Mar 13, 2012 at 17:51 UTC
That is the system perl: it is a 32bit perl (spot the missing 64int). Yet another reason not to use it. I never understood why people who make perl distributions on systems that perfectly support 64bit IV/UV's do not configure perl to use it (opposed to systems that are either 32bitall or 64bitall). I bet both older HP-UX and Windows fall into the either/or category. Enjoy, Have FUN! H.Merijn	[reply]
Re^10: Perl 64-bit versions by BrowserUk (Patriarch) on Mar 13, 2012 at 17:54 UTC