------- Comment #2 from abarbati at iaanus dot com 2008-06-26 11:39 ------- After a more careful reading of 5/5, 5.16/4 and 7.1.6.2/4, I believe that gcc is correctly handling the int& case, that is the expected output should be:
FivE FRivE FivE Only the int&& case is thus incorrect, according to my interpretation. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36628