From: SourceForge.net <no...@so...> - 2003-07-09 11:10:16
|
Bugs item #768380, was opened at 2003-07-09 13:10 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 Category: C-Front End Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heinz Ulrich Stille (hustille) Assigned to: Nobody/Anonymous (nobody) Summary: optimizer ignores function side-effect Initial Comment: sdcc -v is: SDCC : mcs51/gbz80/z80/avr/ds390/pic14/pic16/TININative/xa51/ds400 2.3.5 (Jun 25 2003) (UNIX) The attached code fragment gives: st.c:31: warning: conditional flow changed by optimizer 'st.c(28)':so said EVELYN the modified DOG st.c:31: warning: unreachable code st.c(29) This is the "if (checksum) return;" in "rcv()". The optimizer obviously sees only the assignment at the start of the function and ignores the side effect of "rcvbyte()". This should only happen if rcvbyte was declared "const" (which sdcc doesn't support anyway). The error goes away if I change checksum to volatile, or if I delete the "if (err) return;" from the loop. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 |
From: SourceForge.net <no...@so...> - 2003-11-19 17:33:10
|
Bugs item #768380, was opened at 2003-07-09 06:10 Message generated for change (Settings changed) made by epetrich You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 Category: C-Front End Group: None Status: Open >Resolution: Accepted Priority: 5 Submitted By: Heinz Ulrich Stille (hustille) >Assigned to: Erik Petrich (epetrich) Summary: optimizer ignores function side-effect Initial Comment: sdcc -v is: SDCC : mcs51/gbz80/z80/avr/ds390/pic14/pic16/TININative/xa51/ds400 2.3.5 (Jun 25 2003) (UNIX) The attached code fragment gives: st.c:31: warning: conditional flow changed by optimizer 'st.c(28)':so said EVELYN the modified DOG st.c:31: warning: unreachable code st.c(29) This is the "if (checksum) return;" in "rcv()". The optimizer obviously sees only the assignment at the start of the function and ignores the side effect of "rcvbyte()". This should only happen if rcvbyte was declared "const" (which sdcc doesn't support anyway). The error goes away if I change checksum to volatile, or if I delete the "if (err) return;" from the loop. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 |
From: SourceForge.net <no...@so...> - 2003-11-25 12:02:42
|
Bugs item #768380, was opened at 2003-07-09 06:10 Message generated for change (Comment added) made by epetrich You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 Category: C-Front End >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Heinz Ulrich Stille (hustille) Assigned to: Erik Petrich (epetrich) Summary: optimizer ignores function side-effect Initial Comment: sdcc -v is: SDCC : mcs51/gbz80/z80/avr/ds390/pic14/pic16/TININative/xa51/ds400 2.3.5 (Jun 25 2003) (UNIX) The attached code fragment gives: st.c:31: warning: conditional flow changed by optimizer 'st.c(28)':so said EVELYN the modified DOG st.c:31: warning: unreachable code st.c(29) This is the "if (checksum) return;" in "rcv()". The optimizer obviously sees only the assignment at the start of the function and ignores the side effect of "rcvbyte()". This should only happen if rcvbyte was declared "const" (which sdcc doesn't support anyway). The error goes away if I change checksum to volatile, or if I delete the "if (err) return;" from the loop. ---------------------------------------------------------------------- >Comment By: Erik Petrich (epetrich) Date: 2003-11-24 23:00 Message: Logged In: YES user_id=635249 Fixed; see ChangeLog 1.514 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=768380&group_id=599 |