--- Comment #5 from manu at gcc dot gnu dot org 2007-11-13 23:20 ---
Stephan, please, try with
my_func( "format string: %s", (char *)__FILE__ )
Otherwise, you can use -Wno-write-strings to avoid the warning or
-Wno-error=write-strings to get the warning as a warning even when using
-W
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-11-13 22:54 ---
(In reply to comment #3)
> So? Is the warning warranted?
Yes because va_list is not a first class type and never was and is very ABI
dependent.
> Can be worked-around?
Well no, because va_list's type is ABI depende
--- Comment #3 from manu at gcc dot gnu dot org 2007-11-13 05:19 ---
(In reply to comment #2)
> va_list on the target you are using just happens to be a char* and not a
> seperate type.
>
So? Is the warning warranted? Can be worked-around? Should GCC detect this case
and not warn?
--
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-09-29 18:04 ---
va_list on the target you are using just happens to be a char* and not a
seperate type.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33588
--- Comment #1 from stephan at s11n dot net 2007-09-29 16:31 ---
Created an attachment (id=14266)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14266&action=view)
Demonstrates the problem.
Demonstrates this seeming bug, including the discrepancy between client-defined
varargs func
