[WebAssembly] Add test expectations for gcc C++ tests (gcc/testsuite/g++.dg)

[ncw]

llvm/trunk/lib/Target/WebAssembly/known_gcc_test_failures.txt

101

This one uses computed goto as well (address-of-label), surely it shouldn't get as far as the WasmObjectWriter if it's using unsupported frontend features?

[ncw]

If those are all the failures, we're not doing so badly!

[dschuff]

These are just the compile failures :) There's also https://github.com/WebAssembly/waterfall/pull/316/files#diff-a6006086cef2fc4f685647d1fe006766

llvm/trunk/lib/Target/WebAssembly/known_gcc_test_failures.txt

 20041214-1.c O0
 20071210-1.c
 20071220-1.c wasm-s,O0
 920501-4.c
 920501-5.c
 comp-goto-1.c
 980526-1.c
 990208-1.c
+label13.C O0
+label13a.C O0
+label3.C
+pr42462.C O0
 
 # WebAssembly hasn't implemented (will never?) __builtin_return_address
 20010122-1.c
 20030323-1.c
 20030811-1.c
 pr17377.c
 
 # Error: invalid output constraint '=t' in asm.

 20070919-1.c
 align-nest.c
 pr41935.c
 920302-1.c
 920501-3.c
 920728-1.c
 pr28865.c
 widechar-2.c
+attr-alias-1.C
+attr-alias-2.C
+attr-ifunc-1.C
+attr-ifunc-2.C
+attr-ifunc-3.C
+attr-ifunc-4.C
+complit12.C
+va-arg-pack-1.C
+va-arg-pack-len-1.C
+builtin-line1.C
+builtin-location.C
+devirt-6.C  # bad main signature
+devirt-13.C  # bad main signature
+devirt-14.C  # bad main signature
+devirt-21.C  # bad main signature
+devirt-23.C  # bad main signature
 
 # Untriaged: Assertion failure in WasmObjectWriter::applyRelocations
 20071220-2.c wasm-o,O0
+
+# Untriaged C++ failures
+spec5.C
+addr1.C
+ef_test.C
+friend18.C
+member2.C
+new39.C
+new40.C
+nrv8.C
+offsetof9.C
+opaque-1.C
+pr19650.C
+pr37146-1.C
+pr46149.C
+pr59470.C
+rtti2.C
+self1.C
+thread_local3.C
+thread_local3g.C
+thread_local4.C
+thread_local4g.C
+thread_local5.C
+thread_local5g.C
+type-generic-1.C
+vbase8-10.C
+vbase8-21.C
+vbase8-22.C
+vbase8-4.C
+vector1.C