I wrote: > As to the point of whether it actually helps or not ... > on gcc 4.4.7 (RHEL 6), it makes things *WORSE*. We go from about half of > the dispatches getting routed through a common location, to *all* of them > (except one; for some odd reason the first EEO_NEXT in EEOP_NULLIF > survives as a separate jump). This seems like a bug, but there it is.
So after a bit of googling, this is a very longstanding complaint: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39284 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71785 (hm, think I know the second submitter) I'm not sure we should be relying on a gcc bug fix that's barely four months old. Even assuming it fixes the issue without new regressions, most people are not going to have it anytime soon. My feeling at this point is that we might be better off disabling the computed-goto case by default. At the very least, we're going to need a version check that restricts it to latest gcc. 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
