public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: janis187@us.ibm.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/5999: ICE for complex*16 divide with -ffast-math on ia64
Date: Mon, 18 Mar 2002 13:26:00 -0000	[thread overview]
Message-ID: <20020318211810.10800.qmail@sources.redhat.com> (raw)


>Number:         5999
>Category:       optimization
>Synopsis:       ICE for complex*16 divide with -ffast-math on ia64
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 18 13:26:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Janis Johnson
>Release:        gcc version 3.1 20020318 (prerelease)
>Organization:
>Environment:
Itanium; Red Hat Linux release 7.1.94 (Roswell)
>Description:
GCC 3.1 gets a segmentation violation compiling 301.apsi
and 168.wupwise from SPEC CPU2000 with "-O2 -ffast-math" on
ia64-unknown-linux-gnu.  In both cases this occurs for a
divide of a complex*16 variable when expand_expr passes a
NULL op0 to expand_binop, which in turn passes it to
protect_from_queue.

This is a regression from GCC 3.0.4, for which these two
benchmark programs build and run with no problems using
these options.
>How-To-Repeat:
Compile with attached test case with "g77 -O2 -ffast-math".
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="bug.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.f"

QyBHQ0MgMy4xIDIwMDIwMzE4IChwcmVyZWxlYXNlKSBzZWcgZmF1bHRzIGNvbXBpbGluZyB0aGlz
IHRlc3QgY2FzZQpDIHdpdGggLU8yIC1mZmFzdC1tYXRoLiAgVGhpcyBoYXBwZW5zIG9uIGlhNjQg
YnV0IG5vdCBvbiBpNjg2LgpDCiAgICAgIHN1YnJvdXRpbmUgYnVnICh4LCB5LCB6KQogICAgICBj
b21wbGV4KjE2IHgsIHksIHoKICAgICAgeCA9IHkgLyB6CiAgICAgIHJldHVybgogICAgICBlbmQK


             reply	other threads:[~2002-03-18 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 13:26 janis187 [this message]
2002-03-18 14:36 Toon Moene
2002-03-19  4:44 jakub
2002-03-20  1:34 jakub

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=20020318211810.10800.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --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).