https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51891
--- Comment #3 from Dimitris Papavasiliou ---
Created attachment 34329
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34329&action=edit
A patch that fixes the issue and provides a suitable testcase.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #10 from Dimitris Papavasiliou ---
I see, thanks for the advice. Just a clarification: you mean that I should CC
the personal email of the two objc maintainers as I find it from the page
below, correct?
http://gcc.gnu.org/svn/gcc/bra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #8 from Dimitris Papavasiliou ---
Is there anything more I can do to help with this? Does the process simply
take a lot of time or is there no interest in such a feature?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #7 from Dimitris Papavasiliou ---
I made a patch for this (as well as some other minor features) and submitted it
to the gcc-patches list but, since it was ignored there I'm also attaching it
here in case someone decides to look at it
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #6 from Dimitris Papavasiliou ---
Created attachment 30417
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30417&action=edit
Proposed patch adding switches controlling ivar scope in Objective-C.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #5 from Dimitris Papavasiliou
2013-01-20 11:09:57 UTC ---
Actually trying out -Wno-shadow indicates that it doesn't make any difference
in this case. The compiler keeps complaining about the instance variable being
hidden by t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #4 from Dimitris Papavasiliou
2013-01-19 22:29:10 UTC ---
I have considered -Wshadow and this is the way I think I'll go for now because
thinking up of variable names is hard enough without having to think of
synonyms on top.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
--- Comment #3 from Dimitris Papavasiliou
2013-01-19 22:27:30 UTC ---
Created attachment 29224
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29224
Testcase
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56044
Bug #: 56044
Summary: Add dialect option to gobjc to prevent instance
variables from posing as local variables inside
methods.
Classification: Unclassified
Prod
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54554
--- Comment #6 from Dimitris Papavasiliou
2013-01-04 14:50:32 UTC ---
Well this seems to be a core decision regarding the way GCC warnings work
(which probably has more far-reaching consequences) but just for the sake of
argument, I don't
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54554
--- Comment #4 from Dimitris Papavasiliou
2013-01-04 12:41:02 UTC ---
Still even without knowing that a "may be used uninitialized" warning can be
issued in any case.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51891
Dimitris Papavasiliou changed:
What|Removed |Added
CC||dpapavas at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54554
--- Comment #2 from Dimitris Papavasiliou
2012-09-12 10:19:20 UTC ---
Specifying -O does indeed produce a warning if i is not assigned a constant
value (for instance i = rand(); ). Omitting -O and specifying
-Wmaybe-uninitialized does not produc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54554
Bug #: 54554
Summary: Undetected use of uninitialized variable
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFIRMED
Severity: normal
Priority:
14 matches
Mail list logo