Pike-devel November 2016

pike-devel@lists.lysator.liu.se

9 participants
52 discussions

Bad function identifier on 8.1
by Stephen R. van den Berg 29 May '17

29 May '17

While trying to use Pike 8.1, I consistently get the following on stderr whenever I run pike: /usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod.o:-: Warning: Decode failed: Error while decoding program(/usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod:23): Bad function identifier offset for random_string:function(int(0..2147483647) : string(8bit)): 3 != 0 It's not immediately obvious to me how to fix this. Anyone? Or am I the only one seeing this? -- Stephen.

2 4

Protocols.SMTP.ClientHelper()->rfc2822date_time()
by Chris Angelico 25 Jan '17

25 Jan '17

What exactly is this function, and how does it differ from Calendar.Time.format_smtp()? The docs for the latter state that it's "as seen in Date: headers in mails", which seems to be the same purpose. They appear to give the same output. Should the ClientHelper function have a docs reference to format_smtp? Is there a reason to use ClientHelper instead? ChrisA

2 1

Optimised map
by Martin Karlgren 09 Jan '17

09 Jan '17

Hi, Having realised the benefits of functional programming, I’ve been quite annoyed by the rumour of how expensive function calls are in Pike. I decided to look into f_map and could see how much seemingly unnecessary work it does when it calls apply_svalue once for each entry in the array – it should be possible to reuse the pike_frame if it’s about to be thrown away after the function call (if it has other refs on the other hand, it can’t be reused – it’s probably used as a scope in some other frame). I’ve pushed my optimised variant in marty/optimised_map – it seems to work quite well and provides a major speedup. In fact, it’s a bit faster than the corresponding foreach variant. I haven’t verified correctness in various corner cases, and some input on whether it’s correct to do the things init_frame_reuse_context does only once before multiple function calls would be nice too. The *_reuse_context stuff in interpret.c should be applicable wherever the same svalue is applied repeatedly with the same number of arguments (I haven’t looked for it outside of f_map really). What do you all think? Good idea or did I overlook something? Without optimisation: map: 1.660797 array index: 1.335115 array append: 1.17917 With optimisation: map: 0.877659 array index: 1.351158 array append: 1.189812 Test program: int main() { array base = allocate(10000000, 1); float gmap = gauge { array res = map (base, lambda(int i) { return i + 2; }); }; float garrayindex = gauge { array res = allocate(sizeof(base)); foreach (base; int idx; int i) { res[i] = i + 2; } }; float garrayappend = gauge { array res = ({}); foreach (base, int i) { res += ({ i + 2 }); } }; werror ("map: %O\n", gmap); werror ("array index: %O\n", garrayindex); werror ("array append: %O\n", garrayappend); } /Marty

4 12

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 06 Dec '16

06 Dec '16

I noticed that Debian package builds of both 7.8(.866-7) and 8.0(.358-1) have recently started failing on the powerpc architecture. https://buildd.debian.org/status/fetch.php?pkg=pike8.0&arch=powerpc&ver=8.0… /«PKGBUILDDIR»/build/linux-3.16.0-4-powerpc64-ppc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/«PKGBUILDDIR»/build/linux-3.16.0-4-powerpc64-ppc/master.pike /«PKGBUILDDIR»/src/post_modules/GL/gen.pike /«PKGBUILDDIR»/src/post_modules/GL/auto.c.in > auto.c.tmp Segmentation fault This doesn't happen when pike is compiled with -O0, and 7.8.866-6 built fine (the only difference is that -7 is built with MariaDB libraries instead of MySQL), so I assume a compiler bug, but perhaps someone can help figuring out what's triggering it. The backtrace is perhaps not terribly helpful (from 8.0.358): (gdb) bt full #0 jump_opcode_F_MARK_CALL_LFUN_AND_POP (arg1=272) at /home/zino/hack/pike8-rel/pike/src/interpret_functions.h:2418 addr = <optimized out> jumpaddr = <optimized out> #1 0xf7ceeb4c in ?? () No symbol table info available. #2 0x20462184 in mega_apply_low (args=args@entry=0, arg1=arg1@entry=0x206b6370, arg2=<optimized out>) at ./src/interpret.c:2721 saved_jmpbuf = <optimized out> uwp = {previous = 0xfffedc38, frame_pointer = 0x0, func = 0x204516a0 <restore_catching_eval_jmpbuf>, arg = 0x0} #3 0x204e4714 in call_pike_initializers (o=0x206b6370, args=args@entry=0) at ./src/object.c:338 p = 0x206b6370 #4 0x204e7b9c in get_master () at ./src/object.c:702 f = <optimized out> uwp = {previous = 0x0, frame_pointer = 0x0, func = 0x204e5b50 <get_master_cleanup>, arg = 0x0} inside = 1 #5 0x204e7f04 in debug_master () at ./src/object.c:720 o = <optimized out> #6 0x204d55cc in load_pike_master () at ./src/pike_embed.c:397 m = <optimized out> #7 0x2044724c in main (argc=6, argv=0xfffef534) at ./src/main.c:676 m = <optimized out> back = {previous = 0x0, recovery = {{__jmpbuf = {-1376152737, 0, 1917001823, 0 <repeats 13 times>, -134352256, -73784, 4, 543427968, -67736, 570426500, 0 <repeats 40 times>, -1, 0 <repeats 49 times>}, __mask_was_saved = 0, __saved_mask = {__val = {0 <repeats 32 times>}}}}, frame_pointer = 0x0, stack_pointer = 0, mark_sp = 0, severity = 40, onerror = 0xfffedbdc} e = <optimized out> num = <optimized out> p = 0xfffef767 ""

3 16

Refdoc
by Pontus Östlund 29 Nov '16

29 Nov '16

Hi guys! I saw the refdoc on the Pike site is somewhat broken. The plan is to port the new refdoc layout in 8.1 to 8.0, and I'm working on that as we speak. But in order to make that work I need to add the standalone Tools.Standalone.pike_to_html tool since that is used to highlight example code in the refdoc. Is that ok? Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

5 11

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 29 Nov '16

29 Nov '16

For reference, Gentoo considers gcc 4.9.4 stable for all arches except x86 (where 4.9.3 is the latest stable). Anything beyond that is considered unstable.

1 0

EV_OOBAND etc. undefined in backend.cmod on Debian GNU/kFreeBSD
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Nov '16

28 Nov '16

Sorry, I forgot that the build log doesn't show that bug but a earlier one caused by some clock problem causing src/configure to have a modification time in the future.

1 0

EV_OOBAND etc. undefined in backend.cmod on Debian GNU/kFreeBSD
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Nov '16

28 Nov '16

Build on kfreebsd fails due to multiple undefined symbols; see https://buildd.debian.org/status/fetch.php?pkg=pike8.0&arch=kfreebsd-amd64&… It seems 6b9645e2708c53e92db4f752490f0d168280db10 introduced a bug among the #ifs in backend.cmod. At then line 2425, now line 2908, it did -#elif defined(BACKEND_USES_POLL) +#endif /* HAVE_SYS_DEVPOLL_H || HAVE_SYS_EPOLL_H */ + +#ifdef HAVE_POLL but then later we have #endif /* HAVE_POLL */ and then #elif defined(BACKEND_USES_KQUEUE) which doesn't match up with the other #ifdef BACKEND_USES_* conditionals any longer, so the KQUEUE part incorrectly gets omitted.

1 0

Buffer mode for SSL.File?
by H William Welliver III 25 Nov '16

25 Nov '16

Any plans to add buffer mode support to SSL.File? I just discovered this in Stdio.File and think it would be very nice if it were available here as well...

3 2

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1
by Chris Angelico 23 Nov '16

23 Nov '16

On Thu, Nov 24, 2016 at 12:40 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>In Python, it's done with a prefix - u"asdf" is a Unicode string, and >>b"asdf" is a byte string. > > Since nominally strings are Unicode (with the extended ISO 10646 > range) strings now, I think "asdf" can be left as the syntax for that, > and we only need a new syntax for the byte string ("buffer") type. We > can also look at Java, which has byte[] as the type for byte strings, > requiring literals like {'a','s','d','f'}, but I would like to see > something a bit more convenient to use. :-) Agreed. In Python 3.0+, that's how it is - an unadorned string is Unicode, and b"asdf" is a byte string. (Python 2.7 has it the other way - an unadorned string is bytes, and u"asdf" for Unicode - and because of that, you're allowed to put the prefixes on both types of string. But Pike needn't do that.) ChrisA

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel November 2016