public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at false dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/31602] Overflow warning causes GDB -Werror build failure
Date: Tue, 17 Apr 2007 12:26:00 -0000	[thread overview]
Message-ID: <20070417122609.1211.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31602-3264@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from drow at gcc dot gnu dot org  2007-04-17 13:26 -------
Subject: Re:   New: Overflow warning causes
        GDB -Werror build failure

On Tue, Apr 17, 2007 at 12:21:36PM -0000, drow at gcc dot gnu dot org wrote:
> GCC HEAD now warns about this testcase for mips-linux, reduced from
> gdb/value.c.

The warning also occurs once in top.c:

for (offset = num; offset < num + Hist_print && offset < hist_len; offset++)


-- 


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


  reply	other threads:[~2007-04-17 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 12:21 [Bug tree-optimization/31602] New: " drow at gcc dot gnu dot org
2007-04-17 12:26 ` drow at false dot org [this message]
2007-04-18 14:14 ` [Bug tree-optimization/31602] " ian at airs dot com
2007-04-20 15:17 ` ian at airs dot com
2007-04-20 19:04 ` drow at gcc dot gnu dot org
2007-04-24 20:45 ` ian at gcc dot gnu dot org
2007-04-24 21:54 ` ian at gcc dot gnu dot org
2007-04-24 22:27 ` ian at airs dot com

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=20070417122609.1211.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).