From: Bernhard H. <ber...@ot...> - 2001-03-28 11:33:22
|
compiled with --stack-auto: - definition of _func_c_1_1 is missing - movx access of external memory char func () { static char c; return c; } Bernhard P.S.: today without void ;-) |
From: Johan K. <joh...@id...> - 2001-03-28 12:22:17
|
----- Original Message ----- From: Bernhard Held <ber...@ot...> To: <sdc...@li...> Sent: Wednesday, March 28, 2001 1:33 PM Subject: [sdcc-devel]BUG: local & static variable and --stack-auto > compiled with --stack-auto: > - definition of _func_c_1_1 is missing > - movx access of external memory > > char func () > { > static char c; > return c; > } > > Bernhard > > P.S.: today without void ;-) Yes, but in this case even more meaningless than void :) It does nothing so it returns nothing. But you are right, this bad kind of programming should be trapped somewhere, instead of generating wrong code. I will keep this as a teaser in my in-box. Stay away from --stack-auto and --int-long-reent or --float-reent for a while. It is extremely unstable but I am working on it right now. Johan |
From: Johan K. <joh...@id...> - 2001-04-07 20:24:27
|
All my tests pass in all different combinations I could imagine. So I think --stack-auto and --int-long-reent etc is stable again. Please let me know. Johan ----- Original Message ----- From: Johan Knol <joh...@id...> To: <sdc...@li...> Sent: Wednesday, March 28, 2001 2:22 PM Subject: Re: [sdcc-devel]BUG: local & static variable and --stack-auto > ----- Original Message ----- > From: Bernhard Held <ber...@ot...> > To: <sdc...@li...> > Sent: Wednesday, March 28, 2001 1:33 PM > Subject: [sdcc-devel]BUG: local & static variable and --stack-auto > > > > compiled with --stack-auto: > > - definition of _func_c_1_1 is missing > > - movx access of external memory > > > > char func () > > { > > static char c; > > return c; > > } > > > > Bernhard > > > > P.S.: today without void ;-) > > Yes, but in this case even more meaningless than void :) It does nothing so > it returns nothing. But you are right, this bad kind of programming should > be trapped somewhere, instead of generating wrong code. > > I will keep this as a teaser in my in-box. > > Stay away from --stack-auto and --int-long-reent or --float-reent for a > while. It is extremely unstable but I am working on it right now. > > Johan > > > > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > http://lists.sourceforge.net/lists/listinfo/sdcc-devel > |