From: Johan K. <joh...@id...> - 2003-02-28 11:20:21
Attachments:
parse.c
|
As mentioned earlier I noticed a big difference in code generated on linux and cygwin, where it should be identical (apart from the timestamp). There are bugs I can't fix because weird things happen, so I want this cleared first. I do think this is an important issue, you don't want to know how much time I spend tracing this, without success so far. Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c parse.c --dumpall" on mingwin solaris borland msvc and osx with the current cvs. Untill those (or at least some of them) are posted, I would like cvs to be freezed to make them comparable. When I come back from a weekend off, I expect them to be in my mailbox on tuesday morning :). Thank you, Johan |
From: Bernhard H. <Ber...@be...> - 2003-02-28 11:46:19
|
> Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c > parse.c --dumpall" on mingwin solaris borland msvc and osx with the current > cvs. Untill those (or at least some of them) are posted, I would like cvs to > be freezed to make them comparable. I'll generate mingwin and osx 10.1 Bernhard |
From: Kevin V. <kv...@lu...> - 2003-02-28 17:48:14
Attachments:
parse.dumprange
|
On 28-Feb-2003 Johan Knol wrote: > Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c > parse.c --dumpall" on mingwin solaris borland msvc and osx with the > current > cvs. SPARC Solaris output attached. I'll keep out of CVS until you give the all-clear. (I've also been observing some bizarre weirdness. I was hoping the buffer overflow pogrom would fix it, but no such luck yet). Peace, Kevin |
From: Jesus Calvino-F. <Je...@ec...> - 2003-02-28 19:49:46
Attachments:
dumprange.zip
|
Hi Johan, Here there are two files generated with exactly the same msvc build of sdcc.exe, one in windows xp, the other in windows 98: parse.dumprange.win98 and parse.dumrange.winxp, which unfortunatelly are different... Jesus At 12:20 PM 2/28/03 +0100, Johan Knol wrote: >As mentioned earlier I noticed a big difference in code generated on linux >and cygwin, where it should be identical (apart from the timestamp). There >are bugs I can't fix because weird things happen, so I want this cleared >first. I do think this is an important issue, you don't want to know how >much time I spend tracing this, without success so far. > >Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c >parse.c --dumpall" on mingwin solaris borland msvc and osx with the current >cvs. Untill those (or at least some of them) are posted, I would like cvs to >be freezed to make them comparable. > >When I come back from a weekend off, I expect them to be in my mailbox on >tuesday morning :). > >Thank you, >Johan |
From: Borut R. <bor...@si...> - 2003-03-02 18:05:44
|
Hi John, The result of BORLAND C++ build on Windows 2000 is same as parse.dumrange.winxp, sent by Jesus. I run the Win2000 build on Win98, and result was again the same. I don't have the compiler installed on Win98, but if you really need the BORLAND C++ build on Win98 platform and nobody else can provide it, I will install it... Jose: do you have the same version of MSVC compiler on WinXP and Win98? The same service pack? P.S.: I hope I'm not too late ;-) Borut -----Original Message----- From: sdc...@li... [mailto:sdc...@li...]On Behalf Of Jesus Calvino-Fraga Sent: Friday, February 28, 2003 8:49 PM To: Johan Knol; sdc...@li... Subject: Re: [sdcc-devel] Freeze cvs please Hi Johan, Here there are two files generated with exactly the same msvc build of sdcc.exe, one in windows xp, the other in windows 98: parse.dumprange.win98 and parse.dumrange.winxp, which unfortunatelly are different... Jesus At 12:20 PM 2/28/03 +0100, Johan Knol wrote: >As mentioned earlier I noticed a big difference in code generated on linux >and cygwin, where it should be identical (apart from the timestamp). There >are bugs I can't fix because weird things happen, so I want this cleared >first. I do think this is an important issue, you don't want to know how >much time I spend tracing this, without success so far. > >Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c >parse.c --dumpall" on mingwin solaris borland msvc and osx with the current >cvs. Untill those (or at least some of them) are posted, I would like cvs to >be freezed to make them comparable. > >When I come back from a weekend off, I expect them to be in my mailbox on >tuesday morning :). > >Thank you, >Johan |
From: Jesus Calvino-F. <Je...@ec...> - 2003-03-02 19:32:23
|
Hi Borut, I used MSVC 6.0 SP5 in both machines. But it doesn't matter if I use either the executables built with Win98 or WinXP, I get the same results when compiling 'parse.c' in Win98. Jesus P.S. Who are John and Jose? At 07:05 PM 3/2/2003 +0100, Borut Razem wrote: >Hi John, > >The result of BORLAND C++ build on Windows 2000 is same >as parse.dumrange.winxp, sent by Jesus. >I run the Win2000 build on Win98, and result was again the same. > >I don't have the compiler installed on Win98, but if you >really need the BORLAND C++ build on Win98 platform and >nobody else can provide it, I will install it... > >Jose: do you have the same version of MSVC compiler on >WinXP and Win98? The same service pack? > >P.S.: I hope I'm not too late ;-) > >Borut > >-----Original Message----- >From: sdc...@li... >[mailto:sdc...@li...]On Behalf Of Jesus >Calvino-Fraga >Sent: Friday, February 28, 2003 8:49 PM >To: Johan Knol; sdc...@li... >Subject: Re: [sdcc-devel] Freeze cvs please > > >Hi Johan, > >Here there are two files generated with exactly the same msvc build of >sdcc.exe, one in windows xp, the other in windows 98: parse.dumprange.win98 >and parse.dumrange.winxp, which unfortunatelly are different... > >Jesus > >At 12:20 PM 2/28/03 +0100, Johan Knol wrote: > >As mentioned earlier I noticed a big difference in code generated on linux > >and cygwin, where it should be identical (apart from the timestamp). There > >are bugs I can't fix because weird things happen, so I want this cleared > >first. I do think this is an important issue, you don't want to know how > >much time I spend tracing this, without success so far. > > > >Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c > >parse.c --dumpall" on mingwin solaris borland msvc and osx with the current > >cvs. Untill those (or at least some of them) are posted, I would like cvs >to > >be freezed to make them comparable. > > > >When I come back from a weekend off, I expect them to be in my mailbox on > >tuesday morning :). > > > >Thank you, > >Johan > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >sdcc-devel mailing list >sdc...@li... >https://lists.sourceforge.net/lists/listinfo/sdcc-devel |
From: Borut R. <bor...@si...> - 2003-03-02 21:34:26
|
Hi Jesus, as I wrote, I get the same on both platforms with BORLANDC sdcc compiled on Win2000. I'll try also with MSVC, to see, if I'll get the same results as you. But all this story sounds very strange to me... >P.S. Who are John and Jose? It seems that I have a bad day, concerning names. John should be Johan and Jose should be Jesus :-(( Forgive me both. Borut -----Original Message----- From: sdc...@li... [mailto:sdc...@li...]On Behalf Of Jesus Calvino-Fraga Sent: Sunday, March 02, 2003 8:32 PM To: bor...@si...; Johan Knol; sdc...@li... Subject: RE: [sdcc-devel] Freeze cvs please Hi Borut, I used MSVC 6.0 SP5 in both machines. But it doesn't matter if I use either the executables built with Win98 or WinXP, I get the same results when compiling 'parse.c' in Win98. Jesus P.S. Who are John and Jose? At 07:05 PM 3/2/2003 +0100, Borut Razem wrote: >Hi John, > >The result of BORLAND C++ build on Windows 2000 is same >as parse.dumrange.winxp, sent by Jesus. >I run the Win2000 build on Win98, and result was again the same. > >I don't have the compiler installed on Win98, but if you >really need the BORLAND C++ build on Win98 platform and >nobody else can provide it, I will install it... > >Jose: do you have the same version of MSVC compiler on >WinXP and Win98? The same service pack? > >P.S.: I hope I'm not too late ;-) > >Borut > >-----Original Message----- >From: sdc...@li... >[mailto:sdc...@li...]On Behalf Of Jesus >Calvino-Fraga >Sent: Friday, February 28, 2003 8:49 PM >To: Johan Knol; sdc...@li... >Subject: Re: [sdcc-devel] Freeze cvs please > > >Hi Johan, > >Here there are two files generated with exactly the same msvc build of >sdcc.exe, one in windows xp, the other in windows 98: parse.dumprange.win98 >and parse.dumrange.winxp, which unfortunatelly are different... > >Jesus > >At 12:20 PM 2/28/03 +0100, Johan Knol wrote: > >As mentioned earlier I noticed a big difference in code generated on linux > >and cygwin, where it should be identical (apart from the timestamp). There > >are bugs I can't fix because weird things happen, so I want this cleared > >first. I do think this is an important issue, you don't want to know how > >much time I spend tracing this, without success so far. > > > >Attached is parse.c, I need a parse.dumprange, build with just "sdcc -c > >parse.c --dumpall" on mingwin solaris borland msvc and osx with the current > >cvs. Untill those (or at least some of them) are posted, I would like cvs >to > >be freezed to make them comparable. > > > >When I come back from a weekend off, I expect them to be in my mailbox on > >tuesday morning :). > > > >Thank you, > >Johan > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >sdcc-devel mailing list >sdc...@li... >https://lists.sourceforge.net/lists/listinfo/sdcc-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ sdcc-devel mailing list sdc...@li... https://lists.sourceforge.net/lists/listinfo/sdcc-devel |
From: Johan K. <joh...@id...> - 2003-03-04 20:02:04
|
There is now enough material for comparison, thank you all for your corporation and patience. I'm interested in the effect of the OP_SYMBOL and OP_VALUE abuse catch. I did something like that lately for OP_DEFS and OP_USES which helped to solve at least two bugs. But I don't think this is the clue to this problem, since the abuse should be equal on all platforms. I'll work on the parse.dumprange-s asap. Johan |
From: Frieder F. <fri...@we...> - 2003-03-01 19:17:33
Attachments:
parse.dumprange.bz2
|
Hi Johan, the code generated for the decrement "note--;" doesn't seem right to me. The value is not written back. "octave--;" some lines above generates code as expected. (Compiled without the inc_dec.patch I posted) ;parse.c:81: note--; ; genMinus ; genMinusDec mov a,_note dec a ; genAssign mov r1,a ; genAssign ;parse.c:82: break; ljmp 00137$ ;parse.c:40: octave--; ; genMinus ; genMinusDec dec _octave ;parse.c:41: break; ljmp 00155$ Is this a known issue? > cat /proc/version Linux version 2.4.19-4GB (root@Pentium.suse.de) (gcc version 3.2) #1 Fri Sep 13 13:14:56 UTC 2002 Regards, Frieder PS: Yes, it would be nice if the default replies would go to the list. |
From: Johan K. <joh...@id...> - 2003-03-07 20:37:24
|
----- Original Message ----- From: "Frieder Ferlemann" <fri...@we...> > the code generated for the decrement "note--;" doesn't seem > right to me. The value is not written back. > "octave--;" some lines above generates code as expected. In fact the note++ a few lines above does also. The note-- is the last usage of note in it's block which ends in a GOTO (the break) and is therefore not inserted into the loop but instead made part of the loop, with all it's liverange problems. This really helped a lot, I'm getting close to my liverange hunt prey.... Johan PS: No change in the parse.c weirdness yet. |
From: Borut R. <bor...@si...> - 2003-03-03 20:58:57
Attachments:
dumprange.zip
|
Hello, I tried the MSVC build and I found out an interesting thing: - if I run the sdcc executable stand-alone (not from debugger), I get same results as Jesus in parse.dumprange.winxp. Results are equal on Win2000 and Win98 platform. They are equal by using the release build or debug build. - if I run the sdcc executable from Visual Studio debugger, I get different results, which are attached to this mail. I suspect that the problem is caused by some non initialized variable: the debugger probably initializes memory in different way then stand-alone executable. Jesus: did you run sdcc from the debugger or stand-alone? Did you run it in the same mode on both WinXP and Win98? Borut |
From: Jesus Calvino-F. <Je...@ec...> - 2003-03-03 23:12:56
|
Release, stand-alone. At 09:58 PM 3/3/2003 +0100, Borut Razem wrote: >Jesus: did you run sdcc from the debugger or stand-alone? >Did you run it in the same mode on both WinXP and Win98? > >Borut |