public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38999] [4.4/4.5/4.6/4.7 Regression] Extra overflow warning in 32-bit HWI compiler
Date: Mon, 16 Jan 2012 13:30:00 -0000	[thread overview]
Message-ID: <bug-38999-4-lC9HSjHtJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38999-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
      Known to fail|                            |

--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16 13:22:28 UTC ---
Since 4.7 we have need_64bit_hwint=yes for the target the bug was reported
against.

But I'm confused.  Do we want two warnings here?

3.3.6 and 3.4.6 say:

/space/rguenther/install/gcc-3.3.6/bin/gcc -S -std=c99 t.c
t.c:10:13: warning: integer constant is so large that it is unsigned
t.c: In function `f':
t.c:10: warning: integer overflow in expression

while since 4.0.0 we say

t.c:10:13: warning: integer constant is so large that it is unsigned

I don't think we anywhere have a 'integer overflow in expression' warning
(not by default at least) that triggers during optimization.

So - is 4.7 fixed (because hwint 64 is default)?  I didn't really check
hwint32 builds of 4.x.


  parent reply	other threads:[~2012-01-16 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38999-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 14:06 ` [Bug middle-end/38999] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-16 13:30 ` rguenth at gcc dot gnu.org [this message]
2012-01-16 13:45 ` [Bug middle-end/38999] [4.4/4.5/4.6 " jakub at gcc dot gnu.org
2012-03-13 14:32 ` [Bug middle-end/38999] [4.5/4.6 " jakub at gcc dot gnu.org
2012-07-02 11:03 ` rguenth at gcc dot gnu.org
2013-04-12 16:17 ` [Bug middle-end/38999] [4.6 " jakub 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-38999-4-lC9HSjHtJ5@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).