Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Lin Rongrong
To: Sent: Monday, October 17, 2011 8:31 AM Subject: Re: [Sdcc-user] Z80 code size and compile time > That looks like a bad pointer reference to me > > Segment Violation... > > dwg > > On Oct 16, 2011, at 11:49 AM, Philipp Klaus Krause wrote: > >> Am 16.10.2011 1

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Douglas Goodall
That looks like a bad pointer reference to me Segment Violation... dwg On Oct 16, 2011, at 11:49 AM, Philipp Klaus Krause wrote: > Am 16.10.2011 18:15, schrieb Lin Rongrong: >> While I am trying to locate the bug of this problem, I got the following: >> C:\SDCC\BIN\sdcc sips.c -mz80 -c --st

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Lin Rongrong
ilipp Klaus Krause" To: Sent: Monday, October 17, 2011 2:49 AM Subject: Re: [Sdcc-user] Z80 code size and compile time > Am 16.10.2011 18:15, schrieb Lin Rongrong: >> While I am trying to locate the bug of this problem, I got the following: >> C:\SDCC\BIN\sdcc sips.c -mz80 -c -

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Philipp Klaus Krause
Am 16.10.2011 18:15, schrieb Lin Rongrong: > While I am trying to locate the bug of this problem, I got the following: > C:\SDCC\BIN\sdcc sips.c -mz80 -c --std-c99 --max-allocs-per-node > 9521 --codeseg > CODE5 > Caught signal 11: SIGSEGV > Any idea of this singal 11? Looks like a candidate for a

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Lin Rongrong
ilipp Klaus Krause" To: Sent: Sunday, October 16, 2011 7:21 PM Subject: Re: [Sdcc-user] Z80 code size and compile time > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 16.10.2011 07:47, schrieb Lin Rongrong: >> Another bad news, something related with SIP compiled

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Philipp Klaus Krause
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.10.2011 07:47, schrieb Lin Rongrong: > Another bad news, something related with SIP compiled wrong > during --max-allocs-per-node increased from default 3000 to 1. > With default 3000, my software works ok so far, with 1, SIP calling out

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Philipp Klaus Krause
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.10.2011 07:18, schrieb Lin Rongrong: > Results tried with "--oldralloc": > code0 data code1 code2 code3 code4 code5 code6 code7 code > 1C8D 1A90 4661 525B 47A7 50A5 55D0 4354 5625 1BB0 // ar168g sip > 0.55.006 sdcc 3.0.1 > 1BFC 1A9

Re: [Sdcc-user] Z80 code size and compile time

2011-10-16 Thread Philipp Klaus Krause
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.10.2011 06:29, schrieb Lin Rongrong: > Philipp, > >I tested current build #6969, all fine so far. And I noticed that the > compile time was almost the same as 3.0.1 now, and the code size vary on > different code: > > code0 datacode1

Re: [Sdcc-user] Z80 code size and compile time

2011-10-15 Thread Lin Rongrong
Another bad news, something related with SIP compiled wrong during --max-allocs-per-node increased from default 3000 to 1. With default 3000, my software works ok so far, with 1, SIP calling out function is now broken. Woody http://palmmicro.com/woody/ - Original Message - Fro

Re: [Sdcc-user] Z80 code size and compile time

2011-10-15 Thread Lin Rongrong
Results tried with "--oldralloc": code0 data code1 code2 code3 code4 code5 code6 code7 code 1C8D 1A90 4661 525B 47A7 50A5 55D0 4354 5625 1BB0 // ar168g sip 0.55.006 sdcc 3.0.1 1BFC 1A90 476C 5042 489D 5213 5612 452D 57DC 1B7E // ar168g sip 0.55.008 sdcc 3.0.6 #6969 1BB4 1A

Re: [Sdcc-user] Z80 code size and compile time

2011-10-15 Thread Lin Rongrong
Just tried "--max-allocs-per-node 1", compiling time increase to about 8 minutes from 2 minutes. Code size results: code0 datacode1 code2 code3 code4 code5 code6 code7 code 1C8D 1A90 4661 525B 47A7 50A5 55D0 4354 5625 1BB0 // ar168g sip 0.55.006 sdcc 3.0.1 1BFC 1A90 476C 50