Menu
▾
▴
[sdcc-devel] [ sdcc-Bugs-1486853 ] LR: valdiag tests fail with mcs51-large
|
From: SourceForge.net <no...@so...> - 2006-07-01 21:03:25
|
Bugs item #1486853, was opened at 2006-05-11 22:28 Message generated for change (Comment added) made by bernhardheld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1486853&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Live range problems >Group: fixed >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bernhard Held (bernhardheld) Assigned to: Bernhard Held (bernhardheld) Summary: LR: valdiag tests fail with mcs51-large Initial Comment: SDCC rev. #4166 valdiag tests bug-895992.c and bug-971834.c fail. ---------------------------------------------------------------------- >Comment By: Bernhard Held (bernhardheld) Date: 2006-07-01 23:03 Message: Logged In: YES user_id=203539 Fixed in src/SDCClrange.c, SDCC #4252 ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-06-19 11:17 Message: Logged In: YES user_id=888171 Thanks, I guess I wasn't really aware what valdiag was for in the first place. It is supposed to check if SDCC generates the correct warnings and errors. In this case, the generated code is correct, but for -- model-large the warnings are not issued. ---------------------------------------------------------------------- Comment By: Bernhard Held (bernhardheld) Date: 2006-06-18 21:46 Message: Logged In: YES user_id=203539 > What exactly do you mean by fail? I mean this: > Summary for 'mcs51-large': 5 failures, 221 tests, 101 test cases, 0 bytes, 0 ticks > Please verify my assumption. The bug is still there. ---------------------------------------------------------------------- Comment By: Maarten Brock (maartenbrock) Date: 2006-06-14 14:21 Message: Logged In: YES user_id=888171 Bernhard, What exactly do you mean by fail? They now generate a proper warning, but compile ok. I guess my fix for bug 1294475 also fixed this. Please verify my assumption. Maarten ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1486853&group_id=599 |