public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: renau@cs.uiuc.edu
To: gcc-gnats@gcc.gnu.org
Subject: optimization/9037: [tree-ssa] -fssa-dce crashes with simple code
Date: Sun, 22 Dec 2002 09:56:00 -0000	[thread overview]
Message-ID: <20021222175256.22740.qmail@sources.redhat.com> (raw)


>Number:         9037
>Category:       optimization
>Synopsis:       [tree-ssa] -fssa-dce crashes with simple code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Dec 22 09:56:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     renau@cs.uiuc.edu
>Release:        GNU C version 3.5-tree-ssa 20021217 (experimental) (i686-pc-linux-gnu)
>Organization:
>Environment:

>Description:
This is a bug in the tree-ssa branch (experimental). When I activate the -fssa -fssa-dce with -O1 (it does not happen without optimization -O0) gcc crashes.

 The output:

 ./cc1 -fpreprocessed pp.i -quiet -dumpbase pp.c -auxbase pp -O1 -version -fssa -fssa-dce -o pp.s
GNU C version 3.5-tree-ssa 20021217 (experimental) (i686-pc-linux-gnu)
        compiled by GNU C version 3.2 (Mandrake Linux 9.0 3.2-1mdk).
/home/renau/tmp/pp.c: In function `vadd':
/home/renau/tmp/pp.c:8: internal compiler error: RTL flag check: INSN_DEAD_CODE_P used with unexpected rtx code `note' in mark_all_insn_unnecessary, at ssa-dce.c:452
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
ne
>How-To-Repeat:
./xgcc -v -save-temps -O1 -B. -fssa -fssa-dce -S ~/tmp/pp.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="pp.i"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="pp.i"

IyAxICIvaG9tZS9yZW5hdS90bXAvcHAuYyIKIyAxICI8YnVpbHQtaW4+IgojIDEgIjxjb21tYW5k
IGxpbmU+IgojIDEgIi9ob21lL3JlbmF1L3RtcC9wcC5jIgoKCmludCB2YWRkKGludCAqQywgaW50
ICpBLCBpbnQgKkIpCnsKICAgICAgICBpbnQgaTsKCiAgICAgICAgZm9yKGk9MDtpPDEwMDtpKysp
IHsKICAgICAgICAgICAgICAgIENbaV0gPSBBW2ldICsgQltpXTsKICAgICAgICB9Cn0K


                 reply	other threads:[~2002-12-22 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021222175256.22740.qmail@sources.redhat.com \
    --to=renau@cs.uiuc.edu \
    --cc=gcc-gnats@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).