Greg Stark <st...@mit.edu> writes: > Some Google(tm)ing does turn up plenty of other people complaining about > similar behaviour. This report seems to have the most enlightening response: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54561
Yeah, I saw that before too. I got an interesting response from Jakub J. just now as well: https://bugzilla.redhat.com/show_bug.cgi?id=1185673 It sounds like the appearance of the warning is contingent on code generation decisions, making it even less likely to ever be useful to us in its current form. > Perhaps Clang has a more useful warning? Clang, at least the version on my Mac, doesn't warn either with the settings we normally use, and it doesn't have -Wclobber at all. I tried turning on -Weverything, and it still didn't complain. (It did generate incorrect code though, so it's no better than gcc in that respect.) regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
