public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39170] provide an option to silence -Wconversion warnings for bit-fields
Date: Sat, 06 Mar 2010 12:19:00 -0000	[thread overview]
Message-ID: <20100306121844.15389.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39170-17296@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from manu at gcc dot gnu dot org  2010-03-06 12:18 -------
(In reply to comment #10)
> However, with so many lines of legacy code out there using bit-filed that have
> been proven to work, it doesn't make sense to revisit/modify them.  Would it be
> possible for gcc to provide a -Wbitfield-conversion flag in new releases and
> make 39170 an enhancement (preferably high priority)?

Seriously, I am not the "maintainer" of GCC diagnostics or even Wconversion.
Anyone can contribute!

Yes, it may be possible to provide such an option. I am not against such an
option and even if I were I cannot stop you from implementing it and getting it
approved by GCC maintainers. I don't know how much work it would be to
implement it, and out of kindness I might invest some of my free time to try to
do it for GCC 4.6. But even if I might try, that won't happen before summer
almost for sure, and then GCC 4.6 won't be available before late next year.


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|WAITING                     |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-03-06 12:18:44
               date|                            |
            Summary|cannot silence -Wconversion |provide an option to silence
                   |warnings for bit-fields     |-Wconversion warnings for
                   |                            |bit-fields


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39170


  parent reply	other threads:[~2010-03-06 12:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 17:34 [Bug c++/39170] New: -Wconversion useless tom at atoptech dot com
2009-02-12 17:39 ` [Bug c/39170] " pinskia at gcc dot gnu dot org
2009-02-12 18:10 ` tom at atoptech dot com
2009-03-08  3:30 ` [Bug c/39170] cannot silence -Wconversion warnings for bit-fields manu at gcc dot gnu dot org
2009-03-10 17:40 ` tom at atoptech dot com
2009-03-10 19:16 ` manu at gcc dot gnu dot org
2009-03-10 20:34 ` tom at atoptech dot com
2010-01-13 13:40 ` faure at kde dot org
2010-02-18 20:50 ` Zachary_Deretsky at mentor dot com
2010-03-06  0:20 ` Zachary_Deretsky at mentor dot com
2010-03-06  1:37 ` jengliang at gmail dot com
2010-03-06 12:19 ` manu at gcc dot gnu dot org [this message]
     [not found] <bug-39170-4@http.gcc.gnu.org/bugzilla/>
2013-01-04 17:32 ` [Bug c/39170] provide an option to " tom at atoptech dot com
2013-01-04 17:53 ` manu at gcc dot gnu.org
2015-03-06 18:53 ` egall at gwmail dot gwu.edu
2015-03-06 20:10 ` manu at gcc dot gnu.org
2020-05-20 21:56 ` 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=20100306121844.15389.qmail@sourceware.org \
    --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).