public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107314] New: New -Wsign-compare since r13-3360-g3b3083a598ca3f4b
Date: Wed, 19 Oct 2022 07:11:02 +0000	[thread overview]
Message-ID: <bug-107314-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107314
           Summary: New -Wsign-compare since r13-3360-g3b3083a598ca3f4b
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jsm28 at gcc dot gnu.org
  Target Milestone: ---

Reduced from grub package:

$ cat http.i
int port;

enum {
  HTTP_PORT, 
  HTTP_MAX_CHUNK_SIZE = 0x80000000
}
http_establish_file() {
  return 0 ? port : HTTP_PORT;
}

$ gcc http.i -c -Werror=sign-compare -O2
http.i: In function ‘http_establish_file’:
http.i:8:14: error: operand of ‘?:’ changes signedness from ‘int’ to ‘enum
<anonymous>’ due to unsignedness of other operand [-Werror=sign-compare]
    8 |   return 0 ? port : HTTP_PORT;
      |              ^~~~
cc1: some warnings being treated as errors

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  7:11 marxin at gcc dot gnu.org [this message]
2022-10-19  7:25 ` [Bug c/107314] [13 Regression] " rguenth at gcc dot gnu.org
2022-10-19 16:58 ` joseph at codesourcery dot com
2022-10-20 15:48 ` marxin at gcc dot gnu.org
2022-10-20 15:52 ` pinskia at gcc dot gnu.org
2022-10-20 17:05 ` jsm28 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-107314-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).