[ Date Prev][ Date Next][ Thread Prev][ Thread Next][ Date Index][ Thread Index]
Re: [vsipl++] compiler warnings
- To: VSIPL++ Developers List <vsipl++@xxxxxxxxxxxxxxxx>
- Subject: Re: [vsipl++] compiler warnings
- From: Stefan Seefeld <stefan@xxxxxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 10:56:28 -0500
Jules Bergmann wrote:
+#if 0
How should we set this? Via a configure check or based on compiler
version macros?
How about:
#if __ghs__
I believe I introduced the two offending return statements specifically
to make icc happy. Thus I'd suggest to replace the #if 0 by something
like #if __icc__. I'll look into it as soon as I have access to icc
again.
We should add a comment with our current knowledge of compiler state:
// GCC: doesn't care
// Intel C++: complains about unreachable returns
// GreenHills: complains about missing unreachable returns
Indeed. I'll take care of this as soon as I can confirm that it was icc
which requires the macro to be set.
Regards,
Stefan
|