Dear Clang developers,
I recently ran into what appears to be a bug in Clang 3.0 and documented it here:
Does anyone have any input to this issue?
Clang 3.0 is really old. Check with the latest released version (3.2)
-- Sean Silva
I just checked with 3.2 and unfortunately receive the same errors.
Is 3.2 still too old? I can spend some time and build from the current trunk if necessary.
The error is still emitted at r176001 (yesterday's trunk) fwiw.
This is a GCC bug, not a Clang bug. I’ve explained more on stackoverflow.
Thanks Richard, you are absolutely correct!