Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Hello
by Guillaume Collet 23 Jul '14

23 Jul '14

Hi, my name is Guillaume Collet, I'm a french bioinformatician interested in Pike. This message was just to introduce myself. I write C/C++ for for 10 years and I found Pike's features really interesting. That's why I'm here. Cheers, Guillaume.

4 7

Re: Float details
by Mirar ＠ Pike developers forum 09 Jul '14

09 Jul '14

Which serialization? Doesn't ASN.1 have a string format for floats if you want (third byte with value 3 followed by the string)?

2 1

Float details
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 04 Jul '14

04 Jul '14

So -0.0 is a thing. Should we fix any of these: > -0.0; (1) Result: -0.0 > equal(-0.0, 0.0); (2) Result: 1 > decode_value(encode_value(-0.0)); (3) Result: 0.0 > -0.0 < 0.0; (4) Result: 0

2 1

Build fail
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 27 Jun '14

27 Jun '14

Did you run ./run_autoconfig ? It seems configure thinks that its a good idea to rerun the main script in subdirectories that don't have their own configure scripts...

1 0

Re: Casting int to float broken in 8.0 on amd64 Linux
by Chris Angelico 25 Jun '14

25 Jun '14

On Tue, Jun 24, 2014 at 7:05 PM, Per Hedbor () @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Could you give this version of SET_SVAL a try, perhaps? > > #define SET_SVAL(SVAL, TYPE, SUBTYPE, FIELD, EXPR) do { \ > /* Set the type afterwards to avoid a clobbered \ > * svalue in case EXPR throws. */ \ > struct svalue * _sv_ptr=&( SVAL ); \ > _sv_ptr->u.FIELD = (EXPR); \ > *((ptrdiff_t*)&_sv_ptr->type) = TYPE_SUBTYPE(TYPE,SUBTYPE);\ > } while(0) Has exactly the same result. It's entirely possible I'm misdiagnosing this. To come to the conclusion I did, I took the current 8.0 branch, reverted that one commit, and then began applying it piece by piece. The change to configure.in didn't break anything, the change to svalue.h did. Within that, changing from INT16 to short had no effect (on my system, I believe INT16 compiles to short anyway); adding structures and unused defines, unsurprisingly, didn't break anything; and changing the definition of SET_SVAL induced the error message. That's all the info I have to offer. I'm starting up a completely fresh Pike clone to see if somehow I've accumulated cruft of some sort. If that behaves differently, I'll let you know. ChrisA

5 6

new 7.8 stable
by Bill Welliver 24 Jun '14

24 Jun '14

I've moved the latest 7.8 (7.8.866) build to the "all" directory and created a symbolic link to latest-stable. Please feel free to download and upload binaries if you're into such things. Do let me know if any problems are discovered... if all goes well I'll announce things on the main mailing list sometime tomorrow. Best, Bill

1 0

Casting int to float broken in 8.0 on amd64 Linux
by Chris Angelico 24 Jun '14

24 Jun '14

As of commit 7666f806, casting an int to a float fails: rosuav@sikorsky:~/pike$ bin/pike Pike v8.0 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > (float)1; Cast failed, wanted float, got int HilfeInput:1: HilfeInput()->___HilfeWrapper() This happens also on any arithmetic operation that mixes int and float, which does an equivalent cast implicitly. Fiddling around with the corresponding code suggests it may be connected to the GCC warning that also comes up: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] In SET_SVAL, two pointers to the same object with different types are used. I think this violates the C standard, which is why sometimes stuff isn't getting correctly written out - something's getting optimized away. Is there a way to do the same job with a union inside struct svalue, instead of the pointer casts? Or alternatively, can the compiler be told not to optimize this out? ChrisA

2 1

Re: Float details
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 22 Jun '14

22 Jun '14

In e.g. C you would use the signbit() function to find that out. It looks like the Pike sgn() function isn't usable for this purpose though.

1 0

Re: Float details
by Chris Angelico 21 Jun '14

21 Jun '14

On Sat, Jun 21, 2014 at 9:45 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > So -0.0 is a thing. Should we fix any of these: > >> -0.0; > (1) Result: -0.0 >> equal(-0.0, 0.0); > (2) Result: 1 >> -0.0 < 0.0; > (4) Result: 0 These look fine. IEEE 754 says that negative and positive zero are equal. >> decode_value(encode_value(-0.0)); > (3) Result: 0.0 This is the only one that could be called wrong. I doubt it's going to have tripped people up, so changing it or not changing it could be simply a matter of convenience. ChrisA

1 0

problem building 8.0 on sunos 11
by Bill Welliver 19 Jun '14

19 Jun '14

Well, technically it's SmartOS on intel... pike builds but any attempts to use the resulting binary generate the following error (such as when used by post_modules): /home/hww3/dev/rsynced/build/pike/src/pike_types.c:8451: Fatal error: Type mark stack overflow. No stack - no backtrace. I've tried a few random commits back through march and they all have the same problem, so it doesn't appear to be a very new problem. Anyone have any suggestions? Bill

1 0

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