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/6028: libcall handling breaks 173.applu with -Os on ia64
Date: Thu, 21 Mar 2002 18:06:00 -0000 [thread overview]
Message-ID: <20020322020528.30592.qmail@sources.redhat.com> (raw)
>Number: 6028
>Category: optimization
>Synopsis: libcall handling breaks 173.applu with -Os on ia64
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Thu Mar 21 18:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Janis Johnson
>Release: gcc version 3.1 20020321 (prerelease)
>Organization:
>Environment:
Itanium, Red Hat Linux release 7.1.94 (Roswell)
>Description:
The SPEC CPU2000 test 173.applu gets incorrect results when
compiled with -Os on ia64-unknown-linux-gnu with the 3.1
prerelease compiler.
This is a regression from GCC 3.0.4 that begins with this
change:
Sun Dec 23 00:49:37 CET 2001 Jan Hubicka <jh@suse.cz>
* calls.c (ECF_LIBCALL_BLOCK): New constant.
(emit_call_1, initialize_argument_information,
precompute_arguments, expand_call,
emit_library_call_value_1): Use ECF_LIBCALL_BLOCK
instead of ECF_PURE | ECF_CONST. Honnor LCT_CONST/LCT_PURE.
I have not yet put together a test case to include with
this PR, but I can continue to work on that if necessary.
The subroutine that is compiled incorrectly with -Os is
jaclf.f, which has three nested DO loops with lots of math,
four calls to __divdf3, and no other calls. This test
passes with all other optimization options I've tried.
I used SPEC's test (small) input.
>How-To-Repeat:
Build and run 173.applu from SPEC CPU2000 with -Os.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-22 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 18:06 janis187 [this message]
2003-02-19 10:55 ebotcazou
2003-05-09 18:06 Dara Hazeghi
2003-05-16 23:36 Janis Johnson
2003-05-17 6:52 giovannibajo
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=20020322020528.30592.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).