This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug objc++/35967] Local variables interpreted as volatile following a @try block
- From: "pinskia at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Apr 2008 00:17:50 -0000
- Subject: [Bug objc++/35967] Local variables interpreted as volatile following a @try block
- References: <bug-35967-16075@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from pinskia at gmail dot com 2008-04-18 00:17 -------
Subject: Re: Local variables interpreted as volatile following a @try block
On Thu, Apr 17, 2008 at 4:41 PM, ymeroz at earthlink dot net
<gcc-bugzilla@gcc.gnu.org> wrote:
> This is a language syntax issue, as I see it. Variable type can not change by
> itself in mid-scope in C++ or Obj-C. This is not an issue of runtime
> implementation.
It is a little of both really. The way the runtime implements @throw
is via setjmp/longjmp and the compiler has to change them to volatile
variables. I told Apple not to do this but I guess they never
understood how exceptions are used.
Thanks,
Andrew Pinski
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35967