[Webkit-unassigned] [Bug 33056] Implement NO_RETURN for MSVC

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jan 5 01:51:45 PST 2010


--- Comment #18 from Patrick R. Gansterer <paroga at paroga.com>  2010-01-05 01:51:43 PST ---
Sorry for the buildbreak! That wasn't my intention. Sorry!

Here is a small sum up:
If you implement the __declspec(noreturn) MSVC will complain on functions with
returntyp other than void (e.g. functionQuit). If you remove the NO_RETURN
macro from such functions the GCC will throw "warning: function might be
possible candidate for attribute ‘noreturn’". If you use exit() not at the end
of a function MSVC on Win32 will throw "warning C4702: unreachable code", but
on WinCE it complains about a missing return statement if exit() is the last
It's always fun to compile with MSVC, because it has different behaviour on
every platform!

Does it make sense to implement the NO_RETURN macro for MSVC?

In the moment only functionQuit in jsc.cpp (bug 32939), is a blocker to compile
jsc directly from trunk.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list