public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30171] non-portable va_list abuse should be diagnostic
Date: Sun, 24 Dec 2006 04:50:00 -0000	[thread overview]
Message-ID: <20061224045011.16453.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30171-9416@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from pinskia at gcc dot gnu dot org  2006-12-24 04:50 -------
Confirmed.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
           Keywords|                            |diagnostic
   Last reconfirmed|0000-00-00 00:00:00         |2006-12-24 04:50:11
               date|                            |
            Summary|non-portable va_list abuse  |non-portable va_list abuse
                   |is permitted on i386        |should be diagnostic


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30171


  parent reply	other threads:[~2006-12-24  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 11:19 [Bug c/30171] New: non-portable va_list abuse is permitted on i386 dwmw2 at infradead dot org
2006-12-12 17:32 ` [Bug c/30171] " pinskia at gcc dot gnu dot org
2006-12-12 17:33 ` dwmw2 at infradead dot org
2006-12-24  4:50 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-30171-4@http.gcc.gnu.org/bugzilla/>
2021-12-12  4:27 ` [Bug c/30171] non-portable va_list abuse should be diagnostic egallager at gcc dot gnu.org
2021-12-12  4:31 ` egallager 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=20061224045011.16453.qmail@sourceware.org \
    --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: link
Be 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).