public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/107234] New: Format error in m2pp.cc (m2pp_integer_cst)
Date: Wed, 12 Oct 2022 12:11:41 +0000	[thread overview]
Message-ID: <bug-107234-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107234
           Summary: Format error in m2pp.cc (m2pp_integer_cst)
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: modula2
          Assignee: gaius at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
  Target Milestone: ---
            Target: *-*-solaris2.11

Created attachment 53695
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53695&action=edit
Proposed patch

Building the current devel/modula-2 branch on Solaris 11.3 fails:

/vol/gcc/src/hg/master/modula-2/gcc/m2/m2pp.cc: In function 'void
m2pp_integer_cst(pretty*, tree)':
/vol/gcc/src/hg/master/modula-2/gcc/m2/m2pp.cc:2067:26: warning: format '%lu'
expects argument of type 'long unsigned int', but argument 4 has type 'long
long unsigned int' [-Wformat=]
 2067 |   snprintf (val, 100, "%lud", TREE_INT_CST_LOW (t));
      |                        ~~^
      |                          |
      |                          long unsigned int
      |                        %llu

This should use HOST_WIDE_INT_PRINT_UNSIGNED instead of hardcoding a specific
format.

             reply	other threads:[~2022-10-12 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 12:11 ro at gcc dot gnu.org [this message]
2022-10-12 12:11 ` [Bug modula2/107234] " ro at gcc dot gnu.org
2023-02-06 16:38 ` gaius at gcc dot gnu.org
2023-02-06 18:50 ` cvs-commit at gcc dot gnu.org
2023-02-06 18:51 ` gaius 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-107234-4@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).