public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Explorer09 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/114496] New: Documentation: "Non-Bugs" page should update/mention something about -Wsign-conversion
Date: Wed, 27 Mar 2024 08:12:07 +0000	[thread overview]
Message-ID: <bug-114496-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114496
           Summary: Documentation: "Non-Bugs" page should update/mention
                    something about -Wsign-conversion
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Explorer09 at gmail dot com
  Target Milestone: ---

Section 14.8 of GCC manual
"Certain Changes We Don’t Want to Make"
(https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Non-bugs.html)

This item:

> Warning about assigning a signed value to an unsigned variable.
> Such assignments must be very common; warning about them would cause more annoyance than good.

Perhaps GCC should clarify this a bit. GCC now has the "-Wsign-conversion"
option that warns about similar signed-to-unsigned conversions. So what feature
in particular did GCC choose not to implement? The difference between this
"non-bug" item and the existing "-Wsign-conversion" is what I wish to see.

             reply	other threads:[~2024-03-27  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  8:12 Explorer09 at gmail dot com [this message]
2024-03-27  8:18 ` [Bug other/114496] " pinskia at gcc dot gnu.org
2024-03-27  8:25 ` pinskia at gcc dot gnu.org
2024-03-27 15:40 ` egallager 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-114496-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).