public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52534] gcc doesn't detect incorrect expression in call to va_start Date: Thu, 15 Mar 2012 09:49:00 -0000 [thread overview] Message-ID: <bug-52534-4-1Esa6KDpE4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52534-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52534 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 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++ reference parameters. */ while (CONVERT_EXPR_P (arg) || TREE_CODE (arg) == INDIRECT_REF) arg = TREE_OPERAND (arg, 0); Why are we stripping off the NOPS here. This is in fold_builtin_next_arg (builtins.c).
next prev parent reply other threads:[~2012-03-15 9:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-08 21:14 [Bug c/52534] New: " mib.bugzilla at gmail dot com 2012-03-12 14:10 ` [Bug c/52534] " rguenth at gcc dot gnu.org 2012-03-15 9:49 ` pinskia at gcc dot gnu.org [this message] 2012-03-15 10:04 ` jakub at gcc dot gnu.org 2024-04-09 6:41 ` pinskia at gcc dot gnu.org 2024-04-09 11:06 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-52534-4-1Esa6KDpE4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).