public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belyshev at lubercy dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/17133] New: [3.5 Regression] wrong code with -ftree-loop-optimize Date: Sat, 21 Aug 2004 20:58:00 -0000 [thread overview] Message-ID: <20040821205808.17133.belyshev@lubercy.com> (raw) use '-O1' to repeat: ------------------------------------------------------------------------------ extern void abort (void); int foo = 0; void *bar = 0; unsigned int baz = 100; void *pure_alloc () { void *res; while (1) { res = (void *) ((((unsigned int) (foo + bar))) & ~1); foo += 2; if (foo < baz) return res; foo = 0; } } int main () { pure_alloc (); if (!foo) abort (); return 0; } ------------------------------------------------------------------------------ -- Summary: [3.5 Regression] wrong code with -ftree-loop-optimize Product: gcc Version: 3.5.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: belyshev at lubercy dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17133
next reply other threads:[~2004-08-21 20:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-21 20:58 belyshev at lubercy dot com [this message] 2004-08-21 21:13 ` [Bug tree-optimization/17133] [3.5 Regression] wrong code with -ftree-lim pinskia at gcc dot gnu dot org 2004-08-31 23:49 ` belyshev at lubercy dot com 2004-09-01 21:19 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-09-05 9:02 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2004-09-08 18:37 ` pinskia at gcc dot gnu dot org 2004-09-11 20:38 ` rakdver at gcc dot gnu dot org 2004-09-12 18:39 ` [Bug tree-optimization/17133] [4.0 " rakdver at gcc dot gnu dot org 2004-10-17 20:30 ` giovannibajo at libero dot it 2004-10-27 17:46 ` cvs-commit at gcc dot gnu dot org 2004-10-29 5:43 ` pinskia 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=20040821205808.17133.belyshev@lubercy.com \ --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).