public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/28187] [4.1/4.2 Regression] '-O2 -fwrapv' exhausts memory. Date: Wed, 05 Jul 2006 15:20:00 -0000 [thread overview] Message-ID: <20060705152041.13253.qmail@sourceware.org> (raw) In-Reply-To: <bug-28187-7667@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from rguenth at gcc dot gnu dot org 2006-07-05 15:20 ------- Slightly more reduced (for 4.1.2 on i686, trunk doesn't fail here): extern void bar(int); void checkgroups(int last, int verbose) { int window = 0; int outstanding = 0; while (window < last || outstanding) { while (outstanding < 47 && window < last) { if (window < last) { outstanding++; if (verbose) bar(window); bar(window++); } } if (outstanding > 0) bar(0); } } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28187
next prev parent reply other threads:[~2006-07-05 15:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-28 12:46 [Bug other/28187] New: " pluto at agmk dot net 2006-06-28 13:22 ` [Bug other/28187] " pluto at agmk dot net 2006-06-28 21:16 ` [Bug tree-optimization/28187] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-07-05 13:48 ` rguenth at gcc dot gnu dot org 2006-07-05 15:06 ` rguenth at gcc dot gnu dot org 2006-07-05 15:12 ` rguenth at gcc dot gnu dot org 2006-07-05 15:20 ` rguenth at gcc dot gnu dot org [this message] 2006-07-05 16:09 ` rguenth at gcc dot gnu dot org 2006-07-06 6:45 ` patchapp at dberlin dot org 2006-07-07 12:32 ` rguenth at gcc dot gnu dot org 2006-07-07 12:34 ` rguenth at gcc dot gnu dot org 2006-07-12 9:26 ` rguenth at gcc dot gnu dot org 2006-07-12 9:26 ` rguenth at gcc dot gnu dot 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=20060705152041.13253.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: linkBe 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).