public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dyatchkov@mcst.ru
To: gcc-gnats@gcc.gnu.org
Subject: optimization/8110: GCC 3.2: wrong code optimization with -O2
Date: Tue, 01 Oct 2002 09:26:00 -0000	[thread overview]
Message-ID: <20021001161806.3626.qmail@sources.redhat.com> (raw)


>Number:         8110
>Category:       optimization
>Synopsis:       GCC 3.2: wrong code optimization with -O2
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 01 09:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Ilia Dyatchkov
>Release:        3.2
>Organization:
>Environment:
System: SunOS 5.8 (Solaris 8)
Architecture: sparc
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: /home/username/src/gcc-3.2/configure --prefix=/home/username/usr --disable-multilib --enable-languages=c,c++,f77 --norecursion
>Description:
cc1 in spec's CINT2000 176.gcc aborts when it made by gcc 3.2 with -O2 (or higher) option. The test works correctly when we use gcc with lower optimization. The test also works after compiling by gcc 2.95.2  with -Os.
It aborts at the end of expand_expr function (in expr.c) because temp=0 (in what way?).
>How-To-Repeat:
Configure SPEC CPU2000 with following settings

ext		= compsys
tune		= base
iterations	= 1
size		= test
OPTIMIZE	= -O2 // or higher

and run runspec.

Or you can make $(SPEC)/benchspec/CINT2000/176.gcc/src/ and then run (spec)cc1 for compiling $(SPEC)/benchspec/CINT2000/176.gcc/data/train/input/cp-decl.i.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-10-01 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  9:26 dyatchkov [this message]
2002-10-01 14:19 rth

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=20021001161806.3626.qmail@sources.redhat.com \
    --to=dyatchkov@mcst.ru \
    --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).