Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

Re: PRINTPTRDIFFT on pike 7.5
by Mirar ＠ Pike developers forum 19 Jan '04

19 Jan '04

As a kludge, yes. I think the *right* fix would be to test against a non-typed pointer diff in configure if ptrdiff_t isn't available. But those tests looked pretty tricky... / Mirar Previous text: >2004-01-19 11:34: >Subject: Re: PRINTPTRDIFFT on pike 7.5 >-------------------------------------------------------------------- >> That means Pike gets confused. Try adding this to global.h >> (before the last #endif): >> >> #ifndef PRINTPTRDIFFT >> #define PTRINTPTRDIFFT "" >> #endif > > >It works. :) > >Maybe we can add this into global.h in case of this came again ? > >/Xavier > > > > / Brevbäraren >

2 1

Re: PRINTPTRDIFFT on pike 7.5
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 19 Jan '04

19 Jan '04

Adding that into global.h would be hiding the problem, which means that it won't be fixed. Bad idea. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-19 11:34: >Subject: Re: PRINTPTRDIFFT on pike 7.5 >-------------------------------------------------------------------- >> That means Pike gets confused. Try adding this to global.h >> (before the last #endif): >> >> #ifndef PRINTPTRDIFFT >> #define PTRINTPTRDIFFT "" >> #endif > > >It works. :) > >Maybe we can add this into global.h in case of this came again ? > >/Xavier > > > > / Brevbäraren >

1 0

PRINTPTRDIFFT on pike 7.5
by Xavier Beaudouin 17 Jan '04

17 Jan '04

Hello there, Seems that some code in new pike 7.5 use some special extension of Gcc (3.x I assume) : /usr/home/kiwi/Pike-v7.5.17/src/array.c:268: syntax error before `PRINTPTRDIFFT' /usr/home/kiwi/Pike-v7.5.17/src/array.c: In function `simple_set_index': /usr/home/kiwi/Pike-v7.5.17/src/array.c:321: syntax error before `PRINTPTRDIFFT' /usr/home/kiwi/Pike-v7.5.17/src/array.c: In function `array_get_item_ptr': /usr/home/kiwi/Pike-v7.5.17/src/array.c:1295: syntax error before `PRINTPTRDIFFT' The code that blown is : index_error(0,0,0,&tmp,ind, "Index %"PRINTPIKEINT"d is out of array range " "%"PRINTPTRDIFFT"d..%"PRINTPTRDIFFT"d.\n", p, -a->size, a->size-1); The %"PRINTPTRDIFFT" part is not handled by my GCC (gcc 2.95.4 20020320 [FreeBSD]). Removing the "PRINTPTRDIFFT solve the problem since FreeBSD 4.8 / 4.9 are stable OS and gcc 2.95.x are on lots of OS. BTW: I am in the process to add a pikefarm there to show Pike developpers the problems. /Xavier

3 6

file limits
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 17 Jan '04

17 Jan '04

It's not that graceful when limit is hit. > string f=""; > for(int i; i<1024*1024; i++) { f+="int i"+i+";\n"; } Ok. > compile(f); Program received signal SIGSEGV, Segmentation fault. 0x080eee50 in low_add_to_identifiers (state=0x83a7768, ARG= {name = 0x85abdd0, type = 0x82b9570, identifier_flags = 0 '\0', run_time_type = 251 'û', opt_flags = 0, func = {c_fun = 0x40ff8, offset = 266232}}) at /home/nilsson/Pike/7.5/src/program_areas.h:19 19 FOO(unsigned INT16,struct identifier, struct identifier, identifiers) / Martin Nilsson (saturator) Previous text: >2004-01-15 20:14: >Subject: file limits >-------------------------------------------------------------------- >If there is one, it's not less then 65536, I hope. >It might be that the source code files are limited to 4Gb. > >Ie, report when you hit the limits and I'm sure someone will fix it. :) > > / Mirar >

8 51

file limits
by Mirar ＠ Pike developers forum 16 Jan '04

16 Jan '04

Considering it never finalizes the program...

1 0

SSLFile
by Mirar ＠ Pike developers forum 16 Jan '04

16 Jan '04

Researching a bit I think the warnings are from the latest "65535" test.

2 2

SSLFile
by Mirar ＠ Pike developers forum 16 Jan '04

16 Jan '04

Also, funny warnings: | In file included from /home/mirar/pike/src/program.c:1214: | program_areas.h: In function `low_add_to_program': | program_areas.h:11: warning: left shift count >= width of type | program_areas.h:11: warning: comparison between signed and unsigned | program_areas.h:11: warning: left shift count >= width of type | program_areas.h:11: warning: comparison between signed and unsigned | program_areas.h:11: warning: left shift count >= width of type | program_areas.h:11: warning: signed and unsigned type in conditional expression | program_areas.h: In function `low_add_to_relocations': | program_areas.h:12: warning: left shift count >= width of type | program_areas.h:12: warning: comparison between signed and unsigned | program_areas.h:12: warning: left shift count >= width of type | program_areas.h:12: warning: comparison between signed and unsigned | program_areas.h:12: warning: left shift count >= width of type | program_areas.h:12: warning: signed and unsigned type in conditional expression | program_areas.h: In function `low_add_to_linenumbers': | program_areas.h:13: warning: left shift count >= width of type | program_areas.h:13: warning: comparison between signed and unsigned | program_areas.h:13: warning: left shift count >= width of type | program_areas.h:13: warning: comparison between signed and unsigned | program_areas.h:13: warning: left shift count >= width of type | program_areas.h:13: warning: signed and unsigned type in conditional expression Dunny when they showed up... / Mirar Previous text: >2004-01-16 22:17: >Subject: SSLFile >-------------------------------------------------------------------- >>> SSLPort.pike:65:Index 'SSLFile' not present in module 'SSL'. > >What's up? xenofarm is totally yellow ^^ > > / Mirar >

1 0

Constant expression evaluation
by Alexander Demenshin 16 Jan '04

16 Jan '04

Hi, What about optimizations of constant expressions in Pike? Say, something like "x = 1 + 2 * 3" will be evaluated during compile time or runtime? I tested a simple case "x = 1/0" and got runtime error, which makes me doubt that constant expressions will be reduced at compile time... Regards, /Al

2 1

Nettle and nettle_* identifiers
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 16 Jan '04

16 Jan '04

Regarding a recent checkin: > * 2004-01-15 17:26:41 (grendel) > Pike/7.5/src/post_modules/Nettle/configure.in, (+2/-2) (18 lines) > > nice. nettle 1.7 had md5_init, 1.8 has nettle_md5_init, you can't > win. Isn't there some #define to set to have nettle not prefix its identifiers with nettle_ (if that is what it would take to win)?

2 1

core.txt
by Mirar ＠ Pike developers forum 13 Jan '04

13 Jan '04

Pike/xenofarm finally created a core file that is almost readable, for the random error I get from the benchmarks: http://pike.ida.liu.se/generated/pikefarm/7.5/1654_342/core.txt Would it be possible to get it to get a Pike backtrace too, to check which arguments the division had that got that got it to crash so rudily?

2 3

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