public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13681] New: [tree-ssa] ICE in get_expr_operands with out-of-bounds access
Date: Wed, 14 Jan 2004 15:37:00 -0000	[thread overview]
Message-ID: <20040114153700.13681.bangerth@dealii.org> (raw)

Seems like tree-ssa is getting too good at optimizing :-) 
 
Here's an out-of-bounds access that ICEs tree-ssa: 
---------------------------- 
struct X { 
    double values[1]; 
 
    double & foo (const unsigned int index) 
      { return values[index]; } 
}; 
 
void foo() { 
  double d; 
  X h1; 
  h1.foo(1) = d; 
} 
------------------------- 
Note that if I call h1.foo(0), then everything is fine, since we 
stay inside the bounds of the values array. However, with the code 
as shown, we get 
 
deal.II/base> c++ -c -O2 x.cc 
x.cc: In function `void foo()': 
x.cc:8: internal compiler error: in get_expr_operands, at 
tree-ssa-operands.c:918 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
 
This is with yesterday's tree-ssa branch. I hope it will be reasonable 
simple to fix, since this is the last ICE I presently get with tree-ssa, 
and if it is fixed I'll switch on a nightly tester for tree-ssa that 
compiles our library. I can then also finally try to run the generated 
code and find all those code-gen bugs :-) 
 
Thanks 
  W.

-- 
           Summary: [tree-ssa] ICE in get_expr_operands with out-of-bounds
                    access
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: critical
          Priority: P2
         Component: optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bangerth at dealii dot org
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13681


             reply	other threads:[~2004-01-14 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 15:37 bangerth at dealii dot org [this message]
2004-01-14 22:38 ` [Bug optimization/13681] " pinskia at gcc dot gnu dot org
2004-01-15 22:17 ` bangerth at dealii dot org
2004-01-16 10:06 ` steven at gcc dot gnu dot org
2004-01-16 12:13 ` steven at gcc dot gnu dot org
2004-01-16 12:48 ` steven at gcc dot gnu dot org
2004-01-21 22:17 ` rth at gcc dot gnu dot org
2004-01-21 22:37 ` bangerth at dealii dot org
2004-01-22  0:05 ` rth at redhat dot com
2004-01-22  0:10 ` bangerth at dealii dot org
2004-01-22  1:58 ` cvs-commit at gcc dot gnu dot org
2004-01-22  2:16 ` rth 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=20040114153700.13681.bangerth@dealii.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).