public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65040] [5 Regression] gcc-5 -Wformat broken
Date: Thu, 12 Feb 2015 11:12:00 -0000	[thread overview]
Message-ID: <bug-65040-4-e9MRB81B6S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65040-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65040

Mark Wielaard <mark at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at gcc dot gnu.org

--- Comment #5 from Mark Wielaard <mark at gcc dot gnu.org> ---
Note that this also triggers for code that looks just fine to the user:

#include <stdio.h>
#include <inttypes.h>

int
main (int argc, char **argv)
{
  uint8_t u = 16;
  printf ("u = %02" PRIx8 "\n", u);
  return 0;
}

m.c: In function ‘main’:
m.c:8:11: warning: format ‘%x’ expects argument of type ‘unsigned int’, but
argument 2 has type ‘int’ [-Wformat=]
   printf ("u = %02" PRIx8 "\n", u);
           ^

Which is somewhat surprising since the user explicitly matched the type and
format specifier.

This is caused by the definition of the PRIx format specifiers all mapping back
to "x" in inttypes.h

/* lowercase hexadecimal notation.  */
# define PRIx8          "x"
# define PRIx16         "x"
# define PRIx32         "x"
>From gcc-bugs-return-477000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 12 11:15:10 2015
Return-Path: <gcc-bugs-return-477000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30230 invoked by alias); 12 Feb 2015 11:15:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30161 invoked by uid 48); 12 Feb 2015 11:15:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65039] [5 Regression] g++ 5 segmentation fault when compiling with -O2 optimization
Date: Thu, 12 Feb 2015 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65039-4-1a1sZXTd3w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65039-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65039-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-02/txt/msg01333.txt.bz2
Content-length: 232

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide039

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I reproduced this with an out-of-date trunk build, but using today's trunk it
compiles OK, so seems to be fixed.


  parent reply	other threads:[~2015-02-12 11:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 10:10 [Bug c/65040] New: " rguenth at gcc dot gnu.org
2015-02-12 10:10 ` [Bug c/65040] " rguenth at gcc dot gnu.org
2015-02-12 10:37 ` mpolacek at gcc dot gnu.org
2015-02-12 10:46 ` mpolacek at gcc dot gnu.org
2015-02-12 11:05 ` jakub at gcc dot gnu.org
2015-02-12 11:07 ` jakub at gcc dot gnu.org
2015-02-12 11:12 ` mark at gcc dot gnu.org [this message]
2015-02-12 11:33 ` fche at redhat dot com
2015-02-13  7:56 ` mpolacek at gcc dot gnu.org
2015-02-13  7:57 ` mpolacek at gcc dot gnu.org
2015-02-14  9:58 ` jirislaby at gmail dot com
2015-02-14 10:31 ` mpolacek at gcc dot gnu.org
2015-02-14 11:21 ` jirislaby at gmail dot com
2015-02-14 11:21 ` jakub at gcc dot gnu.org
2015-02-16 11:17 ` mpolacek at gcc dot gnu.org
2015-02-24  9:40 ` rguenth at gcc dot gnu.org
2015-02-24  9:57 ` rguenth at gcc dot gnu.org
2015-02-24 10:14 ` mpolacek at gcc dot gnu.org
2015-02-24 10:16 ` jakub at gcc dot gnu.org
2015-02-24 10:22 ` rguenth at gcc dot gnu.org
2015-02-27 15:02 ` mpolacek at gcc dot gnu.org
2015-02-27 15:03 ` mpolacek 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-65040-4-e9MRB81B6S@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).