Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Build of 7.8.866 getting stuck in a loop
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 22 Nov '16

22 Nov '16

>Here are two: >(gdb) bt >#0 0x000000000055d953 in advance () at ./src/peep.c:910 >#1 asm_opt () at ./src/peep.c:1081 >#2 assemble (store_linenumbers=store_linenumbers@entry=1) at ./src/peep.c:441 [...] >(gdb) cont >Continuing. >^C >Program received signal SIGINT, Interrupt. >0x000000000048a738 in low_make_buf_space (space=space@entry=0, buf=buf@entry=0x98f820 <instrbuf>) at ./src/dynamic_buffer.c:17 >17 ./src/dynamic_buffer.c: Filen eller katalogen finns inte. >(gdb) bt >#0 0x000000000048a738 in low_make_buf_space (space=space@entry=0, buf=buf@entry=0x98f820 <instrbuf>) at ./src/dynamic_buffer.c:17 >#1 0x00000000005571b4 in instr (offset=0) at ./src/peep.c:878 >#2 opcode (offset=0) at ./src/peep.c:884 >#3 low_asm_opt () at ./src/peep_engine.c:4560 >#4 0x000000000055d969 in asm_opt () at ./src/peep.c:1098 >#5 assemble (store_linenumbers=store_linenumbers@entry=1) at ./src/peep.c:441 [...] Looks like it's probably an infinite loop in the peep-hole optimizer. Recompile the pike binary configured --with-debug, and run the script by hand with -a3. Hopefully the looping peep-hole rules will be obvious then. /grubba

1 0

Build of 7.8.866 getting stuck in a loop
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 22 Nov '16

22 Nov '16

Nobody has any idea why the 7.8 build hangs but not the 8.0 build? Is it time to abandon pike7.8 already? Actually I'm not sure if there's any good reason to keep multiple versions in parallel in the same manner as Python; it was just packaged that way when I took over.

3 2

Added permessage-deflate support to WebSocket
by Stephen R. van den Berg 22 Nov '16

22 Nov '16

Added it to both 8.0 and 8.1. It's in use in my Socket.IO implementation, and so far it passes all tests. Since testing it involves using a webbrowser as counterpart, my tests are sadly not comprehensive. Arne, could you check the code and see if it meets your criteria on the proposed visible interfaces? There is a little bit of trickery involved in the rsv bits. In order to know if to decompress, we need to know the RSV1 bit on the *first* frame part of the larger frameset. -- Stephen.

4 11

nettle in fedora/centos does not include the secp192 and 224 curves
by Martin Bähr 22 Nov '16

22 Nov '16

hi, i just discovered that nettle in fedora/centos does not include the secp192 and 224 curves. this is not discovered during build, but instead just leads to a runtime error. (the installation succeeds despite the error) to make building pike work properly, the absence of these needs to be tested, so the code referencing them can be skipped. i verified that, removing the references to those curves makes pike run without error, though i am not sure if this should be a compile option or if automatic detection is better. greetings, martin.

3 2

Performance/memory usage difference?
by Stephen R. van den Berg 22 Nov '16

22 Nov '16

Given two solutions: 1.==================================================== class A { final int b; final C e; class C { final int D() { return b; } }; void create() { e = C(); }; }; or 2.: ================================================ class C { final array b; final array D() { return b; }; void create(array _b) { b = _b; }; }; class A { final array b; final C e; void create() { e = C(b); }; }; ==================================================== Assuming that there are (a lot) more other members and methods in both classes (which are accessed within the class, not cross-class), and further assuming that the A class is being instantiated a *lot*: What would the runtime impact of these two approaches considering CPU time and memory used? I would guess that solution 1 would be slightly more efficient, both memory and CPU-wise. Or am I overlooking something here where due to the nested stack frames of solution 1, the actual CPU or memory usage is higher than expected? -- Stephen.

4 3

Optimization
by Peter Bortas ＠ Pike developers forum 22 Nov '16

22 Nov '16

Change it to has_prefix?

1 0

BSON codings and multisets
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 22 Nov '16

22 Nov '16

I have done some work to connect to MongoDB using Pike and that requires the use of BSON. Unfortunately, MongoDB seems to think that BSON is an ordered document, i.e. the order of the indices in the encoded document matters. This is something that Pike doesn't support as we use mappings as input (which does not have a guaranteed order). I see two ways out of this; either we extend the BSON API in pike to allow for a sorted array to specify the indices in the order they should be added to the BSON document or we fix the multiset implementation so that it becomes more like what mast intended it to be and switch to that. (His intention was to make it more like an ordered mapping) Out of the two, option 1 is trivial and that is what I did for now. It is ugly as **** though and I'd much prefer option 2 but that seems to be a lot more complicated if you ask me. In the long run, I guess we should ask ourselves what the purpose of the current multiset implementation is. I can't really see any value in having the current implementation tbh, but I might be missing something. So, what do people think? Should we create an extended BSON API as a short (or maybe long-term) solution to get ordered BSON documents and what are the opinions on multisets?

1 0

Optimization
by Jonas Walld�n ＠ Pike developers forum 22 Nov '16

22 Nov '16

Just thinking of Nilsson's trick here: - if(has_value(str, "\0")) + if( String.range(str)[0]==0 ) I was about to suggest moving this optimization to f_has_value(), but I now see that it's already part of f_search() (called by f_has_value) for string/string cases so this is just an obfuscation.

1 0

Pike 8.0.294 beta
by Peter Bortas 22 Nov '16

22 Nov '16

Pike 8.0.294 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294-win32-oldli… -- Peter Bortas, NSC

2 1

CHANGES for next release
by Peter Bortas ＠ Pike developers forum 22 Nov '16

22 Nov '16

The entries added to CHANGES since 8.0.276 looks a bit sparse when compared to the actual commits. Should any of this get an entry?: http://pike-librarian.lysator.liu.se/index.xml?m=pike.git&starttag=&start=J…

1 0

Jump to page:

2026

2025

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