7502af89fc
This will enable removal of a hack from the wasm backend in a future change. This feels unnecessarily clunky. I would assume something was automatically parsing this and propagating it in the C++ case, but I can't seem to find it. In particular it feels wrong that I need to parse out the individual values, given they are listed in the options.td file. We should also be parsing and forwarding every flag that corresponds to something else in TargetOptions, which requires auditing.
9 lines
298 B
LLVM
9 lines
298 B
LLVM
; RUN: not %clang_cc1 -triple wasm32 -exception-model=arst -S %s 2>&1 | FileCheck -check-prefix=INVALID-VALUE %s
|
|
|
|
; Make sure invalid values are rejected for -exception-model when the
|
|
; input is IR.
|
|
|
|
; INVALID-VALUE: error: invalid value 'arst' in '-exception-model=arst'
|
|
|
|
target triple = "wasm32"
|