public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/110612] New: text-art: four clang warnings
Date: Mon, 10 Jul 2023 14:24:03 +0000	[thread overview]
Message-ID: <bug-110612-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110612
           Summary: text-art: four clang warnings
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For the text-art directory, here is the list of warnings produced
by a build of gcc trunk by clang:

../../trunk.year/gcc/text-art/table.cc:561:15: warning: comparison of integers
of different signs: 'int' and 'size_type' (aka 'unsigned long')
[-Wsign-compare]
../../trunk.year/gcc/text-art/table.cc:573:15: warning: comparison of integers
of different signs: 'int' and 'size_type' (aka 'unsigned long')
[-Wsign-compare]
../../trunk.year/gcc/text-art/table.h:235:16: warning: private field 'm_table'
is not used [-Wunused-private-field]
../../trunk.year/gcc/text-art/widget.h:151:8: warning:
'update_child_alloc_rects' overrides a member function but is not marked
'override' [-Winconsistent-missing-override]

These might be worth fixing.

             reply	other threads:[~2023-07-10 14:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 14:24 dcb314 at hotmail dot com [this message]
2023-07-20  9:28 ` [Bug middle-end/110612] " dcb314 at hotmail dot com
2023-07-21  0:29 ` cvs-commit at gcc dot gnu.org
2023-07-21  0:39 ` dmalcolm at gcc dot gnu.org
2023-07-21  7:13 ` dcb314 at hotmail dot com

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-110612-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).