[Bug c/52534] gcc doesn't detect incorrect expression in call to va_start

2024-04-09 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 --- Comment #5 from Jakub Jelinek --- Note, if we warn, we shouldn't warn for C23 or later, because one can pass anything there, like 3 arguments, or that (unsigned int)n_args, or just one, etc. And __builtin_va_start (ap, 0) is what is used reg

[Bug c/52534] gcc doesn't detect incorrect expression in call to va_start

2024-04-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 --- Comment #4 from Andrew Pinski --- Interesting clang accepts it also.

[Bug c/52534] gcc doesn't detect incorrect expression in call to va_start

2012-03-15 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #3 f

[Bug c/52534] gcc doesn't detect incorrect expression in call to va_start

2012-03-15 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 --- Comment #2 from Andrew Pinski 2012-03-15 09:41:38 UTC --- /* Strip off all nops for the sake of the comparison. This is not quite the same as STRIP_NOPS. It does more. We must also strip off INDIRECT_EXPR for C++ ref

[Bug c/52534] gcc doesn't detect incorrect expression in call to va_start

2012-03-12 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 Richard Guenther changed: What|Removed |Added Keywords||accepts-invalid Status|UNC