Pike-devel December 2016

pike-devel@lists.lysator.liu.se

7 participants
18 discussions

C99, dynamic arrays, and branch rosuav/gtk2-drag-drop
by Chris Angelico 12 Dec '16

12 Dec '16

I've noticed a number of commits going through that remove C99isms for the sake of Windows builds. Does that imply that the code must be exclusively C89, or are there some C99isms that are acceptable? The only one left now is a dynamic array: GtkTargetEntry drag_targets[targ->size]; Will this cause problems? If so, what's the preferred idiom - alloca? I'd like to merge this branch into 8.1 soon, if there are no objections. I've been using it locally with no problems. ChrisA

2 1

Pike 8.0 release 6
by Peter Bortas 11 Dec '16

11 Dec '16

Pike 8.0 release 6 (build 8.0.370) is now out. Source: https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370-win32-oldli… Changes since Pike 8.0.358 (release 5) ---------------------------------------------------------------------- New features ------------ o Calendar Updated Calendar to use timezonedata from tzdata2016j. o Nettle Added version(). o Refdoc Updated to new Pike site layout. Bug fixes --------- o JSON Fixed a bug in the unicode handling of Standards.JSON.decode(), which treated codepoints slightly below the surrogate range as invalid. o pike -x pmar_install Works again and properly verifies PMAR checksums. o ::_indices(), ::_values(), ::_types(), ::`->(), ::`->=() Fixed several argument checking bugs in the magic_* functions. o Fixed some bugs in the pmar installer. o Msql Fixed some compilation issues. o Sql.pgsql Fixed broken reconnect behaviour when the database connection dies. Runtime ------- o Added workaround for incompatibility in MS Windows 10's Linux emulation layer. Regards, -- Peter Bortas

1 0

Release candidate 8.0.370
by Peter Bortas 07 Dec '16

07 Dec '16

Going out as release at the end of the week if nothing unexpected pops up. Pike 8.0.370 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.370/Pike-v8.0.370-win32-oldli… Changes since Pike 8.0.358 (release 5) ---------------------------------------------------------------------- New features ------------ o Calendar Updated Calendar to use timezonedata from tzdata2016j. o Nettle Added version(). o Refdoc Updated to new Pike site layout. Bug fixes --------- o JSON Fixed a bug in the unicode handling of Standards.JSON.decode(), which treated codepoints slightly below the surrogate range as invalid. o pike -x pmar_install Works again and properly verifies PMAR checksums. o ::_indices(), ::_values(), ::_types(), ::`->(), ::`->=() Fixed several argument checking bugs in the magic_* functions. o Fixed some bugs in the pmar installer. o Msql Fixed some compilation issues. o Sql.pgsql Fixed broken reconnect behaviour when the database connection dies. Runtime ------- o Added workaround for incompatibility in MS Windows 10's Linux emulation layer.

1 0

Release Tuesday
by Peter Bortas 07 Dec '16

07 Dec '16

Tomorrow is the first Tuesday in the month, so time for a release attempt. Have another look at what you checked in since the last release, make sure it still looks good and there appropriate entries in CHANGES. Regards, -- Peter Bortas

2 4

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

Callbacks in CMOD/C and error handling
by Pontus Östlund 03 Dec '16

03 Dec '16

So, I'm working on this libsass CMOD glue (a totally new world for me) and have a question: From the CMOD a callback in the Pike layer is called. If the Pike layer callback throws an error, how do I detect that in the CMOD? As it is now the error is thrown in the Pike layer and the backtrace is output to the console, but the C code after the callback still continues. How do I prevent this? 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>

2 2

Arg.pmod changes incomplete?
by Stephen R. van den Berg 03 Dec '16

03 Dec '16

Pike 8.1 make doc results in: /var/src/roxen/81pike/lib/modules/Arg.pmod:623:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:623:Got : void | int. /var/src/roxen/81pike/lib/modules/Arg.pmod:632:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:632:Got : mixed. /var/src/roxen/81pike/lib/modules/Arg.pmod:641:Too many arguments to unknown function (expected 1 arguments). /var/src/roxen/81pike/lib/modules/Arg.pmod:641:Got : mixed. /var/src/roxen/81pike/lib/modules/Arg.pmod:754:Placeholder already has storage! /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:25:Undefined identifier Arg. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:25:Illegal program pointer. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Must return a value for a non-void function. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Expected: mixed. /var/src/roxen/81pike/lib/modules/Tools.pmod/Standalone.pmod/join_autodoc.pike:132:Got : void. Pike: Failed to load tool join_autodoc: Compilation failed. -- Stephen.

3 2

Segfault generating src/post_modules/GL/auto.c on PowerPC
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 01 Dec '16

01 Dec '16

>Are you saying that the compiler incorrectly optimized out the frame >pointer or that incorrect code led the compiler to believe that it >could optimize out the frame pointer? I'm saying that the machine code generator relies on the frame pointer (or similar construct) being present to implement the *_JUMP opcodes.

1 0

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 December 2016