Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

C-function contract
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 07 May '15

07 May '15

In some of the recent meetings we have discussed the ABI contract for pike functions. Since apply already cleans up the stack (the top is the return value, and the rest is discarded), it would make sense to change the contract so that C functions don't have to care what is on the stack beside the return value. However, the drawback is that you can no longer just call these functions (typically f_*) from other C-code if you intend to use anthing more than the top of the stack. E.g. f_a(); f_b(); f_aggregate(2); You would have to save the stack position and do a stack_pop_n_elems_keep_top() after each call. Do we still think this change is a good one?

2 1

Possible parenthesization problem?
by Chris Angelico 07 May '15

07 May '15

Poking around in signal_handler.c out of curiosity, I came across this: while(UNLIKELY(close(control_pipe[0])) < 0 && UNLIKELY(errno==EINTR)); while(UNLIKELY(close(control_pipe[1])) < 0 && UNLIKELY(errno==EINTR)); (lines 3580-3581) The UNLIKELY marker normally applies to an entire condition, not just to the integer that's about to be compared to zero. Should this become: while(UNLIKELY(close(control_pipe[0]) < 0) && UNLIKELY(errno==EINTR)); while(UNLIKELY(close(control_pipe[1]) < 0) && UNLIKELY(errno==EINTR)); or is there something I'm not understanding about the nature of UNLIKELY()? ChrisA

2 4

8.0 dmalloc doesn't build
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 17 Apr '15

17 Apr '15

Trying to compile Pike 8.0 --with-dmalloc gives me this: make[4]: Entering directory `/home/nilsson/pike/dmalloc/post_modules/GL' /home/nilsson/pike/dmalloc/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/nilsson/pike/dmalloc/master.pike /home/nilsson/pike/src/post_modules/GL/gen.pike /home/nilsson/pike/src/post_modules/GL/auto.c.in > auto.c.tmp Segmentation fault make[4]: *** [auto.c] Error 139 I don't know this code at all. Program received signal SIGSEGV, Segmentation fault. read_int (offset=1) at /home/nilsson/pike/src/docode.c:180 180 { (gdb) bt #0 read_int (offset=1) at /home/nilsson/pike/src/docode.c:180 #1 0x080ef9f7 in do_code_block (n=0x975bee8) at /home/nilsson/pike/src/docode.c:2896 #2 0x082829f8 in dooptcode (name=0x964b340, n=0x975bee8, type=0x9621090, modifiers=1) at /home/nilsson/pike/src/las.c:5282 #3 0x0806031f in yyparse () at language.yacc:920 #4 0x081d635c in run_pass2 (c=0x968f730) at /home/nilsson/pike/src/program.c:9146 #5 0x081d6c48 in f_compilation_compile (args=0) at /home/nilsson/pike/src/program.c:9658 #6 0x08097cc3 in lower_mega_apply (args=0, o=0x94885f4, fun=<value optimized out>) at /home/nilsson/pike/src/interpret.c:2172 #7 0x080981bb in mega_apply_low (args=0, arg1=0x94885f4, arg2=1) at /home/nilsson/pike/src/interpret.c:2719 #8 0x081ad551 in f_compilation_env_compile (args=1) at /home/nilsson/pike/src/program.c:8672 #9 0x08097cc3 in lower_mega_apply (args=1, o=0x94885bc, fun=<value optimized out>) at /home/nilsson/pike/src/interpret.c:2172 #10 0x080981bb in mega_apply_low (args=1, arg1=0x94885bc, arg2=1) at /home/nilsson/pike/src/interpret.c:2719 #11 0x082890b2 in f_compile (args=1) at /home/nilsson/pike/src/builtin_functions.c:4636 #12 0x081875a4 in get_master () at /home/nilsson/pike/src/object.c:634 #13 0x08160a7c in load_pike_master () at /home/nilsson/pike/src/pike_embed.c:399 #14 0x0805a503 in main (argc=6, argv=0xbffff594) at /home/nilsson/pike/src/main.c:676

1 0

Address sanitizer
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 13 Apr '15

13 Apr '15

Could we use -fsanitize=address to remove most of the debug malloc code?

2 1

Pikefarm revived.
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Apr '15

13 Apr '15

FYI: I've spent the last few days updating Pikefarm to current Xenofarm and to monitoring git and the current branches of Pike. It now seems to work again. Caveat: The put binary in Xenofarm does not support redirects, so the resulturl needs to be updated to pike.lysator.liu.se.

2 1

SSL curve ciphers
by Chris Angelico 06 Apr '15

06 Apr '15

See branch: rosuav/curve_crypto_guard Is there a simpler way to cope with crypto absences than all the #if'ing everywhere? It's easy to create a Pike that won't build on systems that lack one or other. ChrisA

3 2

config error
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 31 Mar '15

31 Mar '15

I feel like I've run into this before. Any better way of solving it than a cleaning the source tree? ./config.status --recheck running CONFIG_SHELL=/bin/bash -norc /bin/bash -norc /home/nilsson/pike/src/configure --no-create --no-recursion ./config.status: line 530: /bin/bash -norc: No such file or directory ./config.status: line 530: exec: /bin/bash -norc: cannot execute: No such file or directory make[2]: *** [config.status] Error 126 make[1]: *** [_make_in_builddir] Error 2 make: *** [compile] Error 2

2 1

autoconfig autoheader not found
by robert papadopoulos 29 Mar '15

29 Mar '15

In attempting to build Pike 8.0 I was met with a slew of errors. I used the make command as specified. the errors begin... cd src && ./run_autoconfig . ./run_autoconfig: 1: ./run_autoconfig: autoconf: not found ./run_autoconfig: 70: [: Illegal number: Warning: Using autoconf < 2.50. Don't do this if you want to make export. followed by a hundred or so lines of ./run_autoconfig: 139: ./run_autoconfig: autoheader: not found ./run_autoconfig: 143: ./run_autoconfig: Running autoconf in . with variations on the path. I was successfully able to build Pike 7.8 and play around with it using the same method. Can any body provide any advice to get me up and running? I'm running Linux Mint 17 Qiana 32 bit XFCE.

2 2

errors in makecheck pike 8.0
by robert papadopoulos 29 Mar '15

29 Mar '15

So, I had to do a little research on autoconf, but I'm back for more. I used version 2.58 and recieved the following errors/skippages. I'm assuming a lack of fortran is the reason for the skipped gimmicks, but I am stumped by the rest. Mr Welliver, thank you for your help in the last email for getting me one step further than I previously was. ## ------------- ## ## Test results. ## (from make check)... ## ------------- ## ERROR: 172 tests were run, 4 failed unexpectedly. Executables (autoheader, autoupdate...). 3: autom4te cache FAILED (tools.at:131) 4: autoconf --trace: user macros FAILED (tools.at:180) M4sugar. 13: [m4_warn] FAILED (m4sugar.at:59) 14: [m4_require: circular dependencies] FAILED (m4sugar.at:107) 40: Configuring subdirectories skipped (torture.at:562) 41: Deep Package skipped (torture.at:658) 66: GNU Fortran 77 skipped (fortran.at:33) 67: GNU Fortran skipped (fortran.at:61) Testing autoconf/fortran macros. 68: AC_F77_MAIN skipped (acfortran.at:12) 69: AC_F77_WRAPPERS skipped (acfortran.at:13) 70: AC_FC_MAIN skipped (acfortran.at:14) 71: AC_FC_WRAPPERS skipped (acfortran.at:15) 72: AC_PROG_F77_C_O skipped (acfortran.at:16) 73: AC_PROG_FC_C_O skipped (acfortran.at:17) Also, autoconf documentation tells me that it should be installing pike to my bin, but it has yet to make it there. I can of course run pike from its home directory...but where's the fun in that? Hope this email finds all who receive it well. Linux Mint XFCE 32 bit OS

2 1

8.0
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 21 Mar '15

21 Mar '15

> Would anyone object to releasing 8.0 from 8.0.38? Sounds good to me. I don't think I have any known major issues left to fix.

3 10

Jump to page:

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