I do not have GCC 4.2.4, but with GCC 4.2.2 I do not see those warnings.
On Thu, 23 Dec 2010, Steve Reinhardt wrote:
It could be an issue with gcc 4.2.4 not properly handling the "no return"
attribute in some cases... that being a bug that's fixed in 4.4 would
explain why it works for you. That's just speculation on my part though.
Does anyone else have any experience with this? Does the error go away on
4.2.4 if you put the dead 'return' statement back in the particular place
that it's complaining about?
Steve
On Thu, Dec 23, 2010 at 8:12 AM, Nilay Vaish <ni...@cs.wisc.edu> wrote:
Steve, you had commented that panic() and fatal() are marked as "no
return". Then, why should these warnings appear? And why would the compiler
be fine with ERROR_MSG?
--
Nilay
On Thu, 23 Dec 2010, Nilay Vaish wrote:
I am using GCC 4.4, I never see any of these warnings. Let me try with
4.2.4.
Nilay
On Thu, 23 Dec 2010, Steve Reinhardt wrote:
Did you try with debug, opt, and fast?
I see these errors a lot in the regressions:
/z/m5/regression/zizzer/m5/build/ALPHA_SE_MOESI_CMP_directory/mem/ruby/system/PerfectCacheMemory.hh:127:
warning: no return statement in function returning non-void
/z/m5/regression/zizzer/m5/build/ALPHA_SE_MOESI_CMP_directory/mem/ruby/system/PerfectCacheMemory.hh:170:
warning: no return statement in function returning non-void
cc1plus: warnings being treated as errors
If you're not seeing that with any of the builds, maybe you're using a
different gcc version... zizzer has 4.2.4.
Or maybe something's just messed up on zizzer... let me know if you think
those errors are bogus.
Steve
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
