Pike-devel December 2002

pike-devel@lists.lysator.liu.se

5 participants
68 discussions

lurigt
by Mirar ＠ Pike developers forum 12 Dec '02

12 Dec '02

Rekursion verkar lite lurigt i en normal Pike. Jag körde tested jag gjorde tidigare på min valgrind-deoptimerade pike och min normala: test 1) 2) Pike start overhead........ 0.000s 0.000s Ackermann.................. 1.172s 0.576s Array & String Juggling.... 0.693s 0.636s Compile.................... 1.393s 1.010s Compile & Exec............. 1.383s 1.018s Matrix multiplication...... 0.968s 0.407s Loops Nested............... 0.762s 0.292s Loops Recursed............. 1.090s 1.625s <- Varför är den normala *så* långsam där? Det lurigaste är att Ackermann inte alls är lika långsam.

1 0

gcc 3.2
by Mirar ＠ Pike developers forum 11 Dec '02

11 Dec '02

Now gcc 3.2 bit me and allowed code before declaration. Any flags you can add to CFLAGS to not allow that sort of evilness?

10 44

Removed need for cflags_make_conf kludge.
by Mirar ＠ Pike developers forum 11 Dec '02

11 Dec '02

Never mind, I solved it using the optimize/cflags split loop to only use the first mentioned -O, -march and -mcpu.

1 0

Removed need for cflags_make_conf kludge.
by Mirar ＠ Pike developers forum 11 Dec '02

11 Dec '02

Without the "kludge", I get CFLAGS (misc)... -march=athlon-xp -mcpu=athlon-xp -mcpu=i686 ^^^^^^^^^ ^^^^

1 0

Removed need for cflags_make_conf kludge.
by Mirar ＠ Pike developers forum 11 Dec '02

11 Dec '02

Or did you find some magical way of skipping CPU optimizations without it?

1 0

Removed need for cflags_make_conf kludge.
by Mirar ＠ Pike developers forum 11 Dec '02

11 Dec '02

Would you mind putting it back again? 1) make.conf should be used per default if existant 2) warnings should be there even if make.conf is used Forcing use of --enable-make-conf does not solve 2) in any way. make.conf should not be seen as a replacement for using CFLAGS=.

1 0

tiff 4.2
by Mirar ＠ Pike developers forum 10 Dec '02

10 Dec '02

What's wrong with tifflib 4.2? My system comes with it (gentoo), and it installs a dozen utilities using it. Compiling with it gives funny errors: | > Image.TIFF.encode(Image.Image(10,10)); | TIFFWriteScanline returned error on line 0 | object_program(_Image_TIFF): | _Image_TIFF->encode(Image.Image( 10 x 10 /* 0.3Kb */)) | HilfeInput:1: HilfeInput()->___HilfeWrapper() Anyone investigated?

3 3

Windows
by Martin Nilsson (hehe Torgny) ＠ Pike (-) developers forum 10 Dec '02

10 Dec '02

Apart from JPEG not working on Windows, how does it look? Is there an installer made?

2 2

Package guidelines
by Martin Nilsson (hehe Torgny) ＠ Pike (-) developers forum 09 Dec '02

09 Dec '02

I've added some information for package builders in packaging/README. What should be added? What should be changed?

1 0

`| and order on arrays
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 08 Dec '02

08 Dec '02

I thought `| should keep the order when used on arrays: Pike v7.3 release 62 running Hilfe v3.5 (Incremental Pike Frontend) > ({1,2,3}) | ({2,4,1,17}); (1) Result: ({ /* 5 elements */ 3, 2, 4, 1, 17 }) Looks like it keeps the order in the second array, but the remaining elements in the first are swapped in this case. I furthermore expected the elements in the first array to remain unchanged with precedence over those in the second, since that makes it behave more consistently when used as |=, in which case all the elements in the left operand would remain on the same indices. Wasn't this discussed and supposedly fixed some time ago (half a year or so)?

3 11

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 2002