public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51712] -Wtype-limits should not trigger for types of implementation-defined signedness
Date: Tue, 16 Oct 2012 08:43:00 -0000	[thread overview]
Message-ID: <bug-51712-4-qjm2CpjC8t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51712-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #14 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-10-16 08:43:28 UTC ---
(In reply to comment #13)
> If the -fno-short-enums option is needed here, isn't that a bug?

Agreed. This is just hiding the bug for the testsuite but not fixing it for
users.

This is one patch fixing this:
http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00383.html

but a better fix is mentioned in the comments: 

http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00972.html

Implementing any of those options will fix this bug and add the infrastructure
needed to fix similar bugs.


  parent reply	other threads:[~2012-10-16  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30  9:19 [Bug c/51712] New: " jrnieder at gmail dot com
2012-03-26 10:45 ` [Bug c/51712] " manu at gcc dot gnu.org
2012-03-26 20:19 ` jrnieder at gmail dot com
2012-04-17 17:52 ` manu at gcc dot gnu.org
2012-04-17 18:19 ` jrnieder at gmail dot com
2012-04-17 22:10 ` manu at gcc dot gnu.org
2012-04-23 21:12 ` joseph at codesourcery dot com
2012-04-26 12:00 ` manu at gcc dot gnu.org
2012-05-03 22:38 ` manu at gcc dot gnu.org
2012-05-03 23:13 ` manu at gcc dot gnu.org
2012-10-16  7:56 ` jrnieder at gmail dot com
2012-10-16  8:43 ` manu at gcc dot gnu.org [this message]
2012-10-29 13:25 ` manu 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-51712-4-qjm2CpjC8t@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).