public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32367] [4.3 Regression] internal compiler error: in build_polynomial_chrec, at tree-chrec.h:113
Date: Sun, 17 Jun 2007 17:32:00 -0000 [thread overview]
Message-ID: <20070617173250.29692.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32367-1649@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from pinskia at gcc dot gnu dot org 2007-06-17 17:32 -------
> {{&BinomialCoefficients[0], +, 4}_1, +, {0, +, 4}_1}_1
> does not look good: the left part should be invariant in loop_1.
> It's most certainly the code in scev analysis that is in fault here.
> I'll have a look. Thanks for pointing me to the bug.
Ok, thanks. Just to let people know, {{&BinomialCoefficients[0], +, 4}_1, +,
{0, +, 4}_1}_1 was also showing up on the trunk before the pointer_plus was
merged in.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32367
next prev parent reply other threads:[~2007-06-17 17:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 16:57 [Bug c++/32367] New: " ubizjak at gmail dot com
2007-06-16 16:58 ` [Bug c++/32367] " ubizjak at gmail dot com
2007-06-16 17:21 ` [Bug tree-optimization/32367] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-06-16 20:03 ` pinskia at gcc dot gnu dot org
2007-06-16 20:32 ` pinskia at gcc dot gnu dot org
2007-06-16 20:41 ` pinskia at gcc dot gnu dot org
2007-06-16 20:56 ` pinskia at gcc dot gnu dot org
2007-06-16 21:16 ` pinskia at gcc dot gnu dot org
2007-06-16 21:41 ` pinskia at gcc dot gnu dot org
2007-06-17 13:38 ` spop at gcc dot gnu dot org
2007-06-17 17:32 ` pinskia at gcc dot gnu dot org [this message]
2007-06-17 19:13 ` spop at gcc dot gnu dot org
2007-06-17 19:17 ` spop at gcc dot gnu dot org
2007-06-19 18:36 ` spop at gcc dot gnu dot org
2007-06-25 1:54 ` 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=20070617173250.29692.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).