weird clang behavior

Hi,

Recently I filed a bug in gcc bugzilla about weird behavior when processing some code base I had to struggle with currently. Perhaps it may be interesting for clang community as well because clang behaves similar in one case.

More info here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59144

Any thoughts?

Regards,
Tomek