
A significant number of our tests in C accidentally use functions without prototypes. This patch converts the function signatures to have a prototype for the situations where the test is not specific to K&R C declarations. e.g., void func(); becomes void func(void); This is the fifth batch of tests being updated (there are a significant number of other tests left to be updated). Note, the behavior of -ast-print is broken. It prints functions with a prototype (void) as if they have no prototype () in C. Some tests need to disable strict prototype checking when recompiling the results of an -ast-print invocation.
17 lines
827 B
C
17 lines
827 B
C
// RUN: %clang_cc1 -triple i686-pc-win32 -fms-extensions -fsyntax-only -verify %s
|
|
|
|
#pragma fenv_access (on)
|
|
#pragma fenv_access (off)
|
|
|
|
#pragma fenv_access // expected-warning{{missing '(' after '#pragma fenv_access'}}
|
|
#pragma fenv_access foo // expected-warning{{missing '(' after '#pragma fenv_access'}}
|
|
#pragma fenv_access on // expected-warning{{missing '(' after '#pragma fenv_access'}}
|
|
#pragma fenv_access ( // expected-warning{{incorrect use of '#pragma fenv_access}}
|
|
#pragma fenv_access (on // expected-warning{{missing ')' after '#pragma fenv_access'}}
|
|
#pragma fenv_access (on) foo // expected-warning{{extra tokens at end of '#pragma fenv_access'}}
|
|
|
|
void f(void) {
|
|
(void)0;
|
|
#pragma fenv_access (on) // expected-error{{'#pragma fenv_access' can only appear at file scope or at the start of a compound statement}}
|
|
}
|