[TestRvalueReferences] Fix an expectation.

[sivachandra]

Summary

If 'i' is an rvalue reference to an 'int', evaluating it with the
'expression' command will return an 'int' value and not an 'int &&'.
Before this patch, an 'int &&' type was expected.

Enabled the test for clang and gcc as all parts of the test now pass
when the testcase is compiled with them.

[sivachandra]

ping?
Does this qualify as obvious?

lldb/trunk/test/lang/cpp/rvalue-references/TestRvalueReferences.py

class RvalueReferencesTestCase(TestBase):
     @expectedFailureClang("rdar://problem/11479676")
     @dsym_test
     def test_with_dsym_and_run_command(self):
         """Test that rvalues are supported in the C++ expression parser"""
         self.buildDsym()
         self.static_method_commands()
 
     #rdar://problem/11479676
-    @expectedFailureClang("rdar://problem/11479676 pr16762: Expression evaluation of an rvalue-reference does not show the correct type.")
-    @expectedFailureGcc("GCC (4.7) does not emit correct DWARF tags for rvalue-references")
     @expectedFailureIcc("ICC (13.1, 14-beta) do not emit DW_TAG_rvalue_reference_type.")
     @dwarf_test
     def test_with_dwarf_and_run_command(self):
         """Test that rvalues are supported in the C++ expression parser"""
         self.buildDwarf()
         self.static_method_commands()
 
     def setUp(self):
def static_method_commands(self):
 
         # Note that clang as of r187480 doesn't emit DW_TAG_const_type, unlike gcc 4.8.1
         # With gcc 4.8.1, lldb reports the type as (int &&const)
         self.expect("frame variable i",
                     startstr = "(int &&",
                     substrs = ["i = 0x", "&i = 3"])
 
         self.expect("expression -- i",
-                    startstr = "(int &&",
+                    startstr = "(int) ",
                     substrs = ["3"])
 
         self.expect("breakpoint delete 1")
 
         self.runCmd("process continue")
         
         self.expect("expression -- foo(2)")