[Insight-developers] Another patch for ITK 3.2 branch -- ITK_NO_RETURN seen as harmful

[Sean McBride]

On Tue, 22 May 2012 16:53:58 +0000, Williams, Norman K said:

>This has thankfully gone away in ITK 4, but I ran into a problem with this
>in a build that had to work in ITK 3.2.1 branch:
>
>If you use GCC, the __attribute__ ((noreturn)) introduced by ITK_NO_RETURN
>does something, but it doesn't seem to matter if a class method with that
>attribute does actually return.
>
>If you use CLang (and I tried both 3.0 and 3.2 SVN trunk), returning from
>a class method with the noreturn attribute causes a segfault in
>_Unwind_resume.
>
>Can we get rid of ITK_NO_RETURN from 3.2 release branch?

See also my original clang bug:
<http://llvm.org/bugs/show_bug.cgi?id=9395>

And you may want to CC yourself on this one, and lobby for clang to warn in this case:
<http://llvm.org/bugs/show_bug.cgi?id=12200>

Cheers,

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada