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/23929] [4.1 Regression] segfault in expand_simple_operations, tree-ssa-loop-niter.c:637
Date: Mon, 19 Sep 2005 21:14:00 -0000 [thread overview]
Message-ID: <20050919211429.3589.qmail@sourceware.org> (raw)
In-Reply-To: <20050917194257.23929.marcus@jet.franken.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-19 21:14 -------
(In reply to comment #10)
> it is even more obvious it was a latent bug from looking at what we looking at when we are scanning
> over the operands:
> lineD.1272[318 - (<unnamed type>) ivtmp.37D.1332_3]
>
> Where this is an ARRAY_REF and a couple of the ARRAY_REFs can be NULL.
s/couple/couple of the operands/
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23929
next prev parent reply other threads:[~2005-09-19 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 19:43 [Bug c/23929] New: " marcus at jet dot franken dot de
2005-09-17 19:44 ` [Bug c/23929] " marcus at jet dot franken dot de
2005-09-17 19:45 ` [Bug tree-optimization/23929] " pinskia at gcc dot gnu dot org
2005-09-17 19:53 ` [Bug tree-optimization/23929] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-17 22:47 ` pinskia at gcc dot gnu dot org
2005-09-17 22:48 ` pinskia at gcc dot gnu dot org
2005-09-17 22:51 ` pinskia at gcc dot gnu dot org
2005-09-18 11:23 ` steven at gcc dot gnu dot org
2005-09-19 18:22 ` janis at gcc dot gnu dot org
2005-09-19 18:53 ` Andrew Pinski
2005-09-19 18:53 ` pinskia at physics dot uc dot edu
2005-09-19 21:08 ` janis187 at us dot ibm dot com
2005-09-19 21:12 ` pinskia at gcc dot gnu dot org
2005-09-19 21:14 ` pinskia at gcc dot gnu dot org [this message]
2005-09-20 12:48 ` jakub at gcc dot gnu dot org
2005-09-20 19:11 ` cvs-commit at gcc dot gnu dot org
2005-09-20 19:18 ` 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=20050919211429.3589.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).