public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/19224] [4.0 regression] Endless loop compiling simple file: Bug in tree-scalar-evolution.c (instantiate_parameters_1)? Date: Sun, 02 Jan 2005 12:05:00 -0000 [thread overview] Message-ID: <20050102120526.23583.qmail@sourceware.org> (raw) In-Reply-To: <20050102074446.19224.aj@gcc.gnu.org> ------- Additional Comments From aj at gcc dot gnu dot org 2005-01-02 12:05 ------- I've reduced the testcase to the following loop: int add_long(long tl1, long tl2, long tloop_cnt, long *res) { int n; long l1, l2, l; l1 = tl1; l2 = tl2; l = 0; for (n = tloop_cnt; n > 0; n--) { l += l1; l1 += l2; l1 += l2; l2 += l; l2 += l; l += l1; l += l1; l1 += l2; l1 += l2; l2 += l; l2 += l; l += l1; } *res = l; return (0); } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19224
next prev parent reply other threads:[~2005-01-02 12:05 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-02 7:44 [Bug tree-optimization/19224] New: " aj at gcc dot gnu dot org 2005-01-02 7:45 ` [Bug tree-optimization/19224] " aj at gcc dot gnu dot org 2005-01-02 11:53 ` [Bug tree-optimization/19224] [4.0 regression] " steven at gcc dot gnu dot org 2005-01-02 12:05 ` aj at gcc dot gnu dot org [this message] 2005-01-02 12:13 ` rakdver at gcc dot gnu dot org 2005-01-02 15:57 ` pinskia at gcc dot gnu dot org 2005-01-02 18:48 ` rakdver at gcc dot gnu dot org 2005-01-02 18:55 ` rakdver at gcc dot gnu dot org 2005-01-02 20:37 ` sebastian dot pop at cri dot ensmp dot fr 2005-01-02 20:56 ` rakdver at atrey dot karlin dot mff dot cuni dot cz 2005-01-02 21:46 ` sebastian dot pop at cri dot ensmp dot fr 2005-01-02 23:15 ` sebastian dot pop at cri dot ensmp dot fr 2005-01-02 23:19 ` rakdver at gcc dot gnu dot org 2005-01-09 8:22 ` cvs-commit at gcc dot gnu dot org 2005-01-09 15:56 ` 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=20050102120526.23583.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).