[Bug middle-end/36550] Wrong may be used uninitialized warning (conditional PHIs)

2009-02-12 Thread corinl at gmx dot de
--- Comment #9 from corinl at gmx dot de 2009-02-12 21:53 --- I do not really understand problem 5 for the case when the only dependancy for the code-path check is a local variable. In this case the value cannot be change by any other code than existing between the two checks, so

[Bug c++/39133] wrong optimization produces output of false warning

2009-02-11 Thread corinl at gmx dot de
--- Comment #3 from corinl at gmx dot de 2009-02-12 07:26 --- Thanks for the info. Unluckily I just found the bug reported first now for sure: Code: // setuid/setgid only affect the current thread #define FS_PERMS_SET(_uid, _gid) \ bool check_permissions_local

[Bug c++/39133] wrong optimization produces output of false warning

2009-02-11 Thread corinl at gmx dot de
--- Comment #4 from corinl at gmx dot de 2009-02-12 07:37 --- here's the copy from the precompiled header file (.ii), may be it helps: (check_permissions_local removed, it was just for test..same error as before) uid_t fs_perms_uid_orig; gid_t fs_perms_gid_orig; if (check_permissions

[Bug c++/39133] New: wrong optimization produces output of false warning

2009-02-08 Thread corinl at gmx dot de
dot org ReportedBy: corinl at gmx dot de GCC build triplet: 4.2.3-2ubuntu7 GCC host triplet: x86_64 GCC target triplet: x86_64 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39133

[Bug c++/39133] wrong optimization produces output of false warning

2009-02-08 Thread corinl at gmx dot de
--- Comment #1 from corinl at gmx dot de 2009-02-08 22:07 --- Oh sorry, I just see that buf could be used uninitialized for sure (if xl==NULL). but well, shouldn't this warning then be issued all the times? so the bug is now reversed - missing warning instead of false warning