public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54486] [4.6/4.7/4.8 Regression] Spurious printf format warning mentions nonexistent type 'sizetype'
Date: Wed, 05 Sep 2012 07:13:00 -0000	[thread overview]
Message-ID: <bug-54486-4-kFUdZeiiAk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54486-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |middle-end
   Target Milestone|4.8.0                       |4.6.4
            Summary|Spurious printf format      |[4.6/4.7/4.8 Regression]
                   |warning mentions            |Spurious printf format
                   |nonexistent type 'sizetype' |warning mentions
                   |                            |nonexistent type 'sizetype'

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-09-05 07:12:53 UTC ---
Likely caused by http://gcc.gnu.org/viewcvs?view=revision&revision=163994
(too lazy to narrow it down from r163926 - r164000 range).


  parent reply	other threads:[~2012-09-05  7:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  0:28 [Bug c/54486] New: " Keith.S.Thompson at gmail dot com
2012-09-05  6:05 ` [Bug c/54486] " polacek at redhat dot com
2012-09-05  6:13 ` pinskia at gcc dot gnu.org
2012-09-05  6:18 ` jakub at gcc dot gnu.org
2012-09-05  7:13 ` jakub at gcc dot gnu.org [this message]
2012-09-05 16:28 ` [Bug middle-end/54486] [4.6/4.7/4.8 Regression] " jakub at gcc dot gnu.org
2012-09-05 16:30 ` jakub at gcc dot gnu.org
2012-09-07 10:50 ` [Bug middle-end/54486] [4.6 " rguenth at gcc dot gnu.org
2013-04-03 18:19 ` 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-54486-4-kFUdZeiiAk@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: 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).