Inverted arguments in scanf()

Question

I was (quickly) writing some code and accidently inverted the arguments in scanf():

char i[] = "ABC1\t";
scanf(i, "%s");

Compiling with gcc -Werror -Wall -Wextra doesn't complain about this one bit. Obviously, this code doesn't work, but why didn't gcc inform me that I inverted the arguments? Can't it detect that i is not a format string, or that the second argument was not a store-able type?

EDIT
Thanks for the insight all, Looks like I found the answer, there was a twist on the -Wformat flag that makes this "catchable" (posted it below for reference)

Answer 1

Ha! I found it. Hitting gcc with the -Wformat=2 flag caught it.

Posting the info for reference of others:

Here's the list of flags I found

-Wformat Check calls to printf and scanf, etc., to make sure that the arguments supplied have types appropriate to the format string specified...

I had assumed -Wall had -Wformat in it, which it does, but the really important part about what I just found:

-Wformat is included in -Wall. For more control over some aspects of format checking, the options -Wformat-y2k, -Wno-format-extra-args, -Wno-format-zero-length, -Wformat-nonliteral, -Wformat-security, and -Wformat=2 are available, but are not included in -Wall.

Answer 2

I suppose it shouldn't.

int scanf ( const char * format, ... );

i was normally converted to a const char*, all the rest parameters are just "ellipsis" and cannot be checked at compile time.