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

[Williams, Norman K]

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?

--
Kent Williams norman-k-williams at uiowa.edu






________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________