Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

nasm and alpha platform ?
by Xavier Beaudouin 23 Sep '03

23 Sep '03

Hello there, I've got this bug on FreeBSD/Alpha http://bento.freebsd.org/errorlogs/alpha-4-latest/pike74-7.4.25.log because pike still want to use nasm on Image module on non x86 platform. Is there any workaround for that? Or do I have to manualy patch the autoconf script to avoid that ? /Xavier

1 0

wish: string with other quoting then \
by Mirar ＠ Pike developers forum 23 Sep '03

23 Sep '03

If it didn't need " quoted either, it would be quite useful for Pike programs writing Pike programs or HTML or the like...

10 47

xenofarm target problem with 7.5 build
by Alexander Demenshin 22 Sep '03

22 Sep '03

Hi, There is a slight problem with xenofarm client. I tried to specify multiple options in project config, got error, and finally hunted: rm -rf xenofarm_result mkdir xenofarm_result CCACHE_LOGFILE="`pwd`/xenofarm_result/ccache.log.txt" \ MAKE="`if [ "xmake" = "x" ]; then echo "${MAKE-make}"; else echo "make"; fi`" MAKE_FLAGS=""CONFIGUREARGS=--without-machine-code"\ "BUILDDIR=build/`uname -s -r -m|sed \"s/ /-/g\"|tr \"[A-Z]\" \"[a-z]\"|tr \"/()\" \"___\"`"" \ /bin/sh bin/xenofarm.sh /bin/sh: command substitution: line 1: syntax error near unexpected token `(' /bin/sh: command substitution: line 1: `uname -s -r -m|sed \"s/ /-/g\"|tr \"[A-Z]\" \"[a-z]\"|tr \"/()\" \"___\"' FORMAT 2 BEGIN build BEGIN compile make: *** [xenofarm] Interrupt In this case, when only one argument is specified, there is a problem already. In case if several arguments are specified, it just stop since second argument will be interpreted as command name. As you can see, construct MAKE_FLAGS=""CONFIGUREARGS=--without-machine-code" ^^^^ is a bit incorrect. Regards, /Al

2 1

Re: wish: string with other quoting then \
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 21 Sep '03

21 Sep '03

Of course, #" should still support \ as an escape character because doing otherwise would break backwards compatibility. Other #*:s should not though. Makes it slightly unorthogonal, I'm afraid...

1 0

Win32 SMP
by Peter Bortas ＠ Pike developers forum 20 Sep '03

20 Sep '03

7.4.28 have a problem with Win32 and multiple processors. I'm going to try (again) to make a binary search for when the problem was introduced, but if someone has any ideas feel free to share. This is where it breaks when trying to run the installer: http://peter.bortas.org/pikedev/smpcrash.JPG

3 12

pikefarm's configinfo.txt
by Alexander Demenshin 20 Sep '03

20 Sep '03

Is there any reason why svalue/int/float sizes are omitted in configinfo.txt which appears on pikefarm? Regards, /Al

2 1

Re: Adding PCRE to Pike
by Johan Sundstr�m, Lysator ＠ Pike developers forum 20 Sep '03

20 Sep '03

http://www.bagley.org/~doug/shootout/bench/regexmatch/?cpu / Johan Sundström, Lysator Previous text: >2003-09-19 15:30: >Subject: Re: Adding PCRE to Pike >-------------------------------------------------------------------- >where did you see that? > >greetings, martin. > > > / Brevbäraren >

3 3

Re: Adding PCRE to Pike
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 19 Sep '03

19 Sep '03

I've done a bit of testing myself. The figures one gets depend a lot on the kind of testing, but this is a fairly straightforward case when searching for a submatch that doesn't exist in a large string: Pike: 0.00017900 s Perl: 0.00074000 s Emacs 20: 0.04566600 s Emacs 21: 0.05563044 s TRE: 0.07000000 s GNU Regex: 0.16000000 s The shortcoming in Pikes Regexp is the lack of features, not the speed. / Martin Stjernholm, Roxen IS Previous text: >2003-09-19 15:30: >Subject: Re: Adding PCRE to Pike >-------------------------------------------------------------------- >where did you see that? > >greetings, martin. > > > / Brevbäraren >

2 2

Adding PCRE to Pike
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 19 Sep '03

19 Sep '03

Open question: What problems are there to add PCRE to Pike? Sure it'd be nice to have a regexp package that groks wide strings but since Regexp isn't better in that regard there's nothing to lose.

9 19

time() and optimization again
by Alexander Demenshin 19 Sep '03

19 Sep '03

Hi, Long time ago I posted a message about wrong optimization with time() (and perhaps something else). Nobody replied, and the problem is still present in recent CVS (7.4.27). So here it is again: --- snip --- Just found another bug(?) - the construction like: int ts = time() + 10; while (time() < ts) /* nothing */ ; is wrongly optimized - it doesn't work as expected, i.e. the loop is bypassed - so virtually there is no delay. When I change it to 'while ((n = time()) < ts);' or put something in body, it works. Checked against one day old CVS Pike 7.4 (7.4.17). NB: Is it related to time() only or? :) --- snip --- Also, there is a (slight) inconvenience with time() function. To retrieve current time with high precision I've to use time(2)+2.0, since only this syntax allow to retrieve time with microsecond precision. But, unfortunately, it adds 2 seconds to the result. Sure, extra float op is nothing (almost), but at least inconvenient and misleading. Would it be a good idea to add an extra option (say, negative argument) to return current time as float without using base (which is the case when argument is > 1)? And last about time() :) When Pike is compiled with default float size, its float result is absolutely unrealiable (even wrong) - because of very limited precision (just try: time() - (int)(time(2)+2), the difference will impress you). Yes, I know that there is gethrtime() etc., but I can't use it (directly) with call_out(), for instance (and gethrtime() involves MPI, which is quite slow comparing to floats, even double precision floats). Regards, /Al

9 32

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