public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ghazi@caip.rutgers.edu To: gcc-gnats@gcc.gnu.org Cc: roger@eyesopen.com Subject: target/10348: sparc64-sun-solaris2.7 testsuite failure in execute/20020720-1.c with -fpic/-fPIC Date: Tue, 08 Apr 2003 14:56:00 -0000 [thread overview] Message-ID: <20030408145341.18271.qmail@sources.redhat.com> (raw) >Number: 10348 >Category: target >Synopsis: sparc64-sun-solaris2.7 testsuite failure in execute/20020720-1.c with -fpic/-fPIC >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: pessimizes-code >Submitter-Id: net >Arrival-Date: Tue Apr 08 14:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Kaveh Ghazi >Release: gcc version 3.3 20030408 (prerelease) >Organization: >Environment: sparc64-sun-solaris2.7 >Description: As noted here: http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00483.html I'm getting testsuite failures in execute/20020720-1.c on sparc64-sun-solaris2.7 at -O1 and above when adding -fpic or -fPIC to the testsuite pass. The logfile shows that the function `link_error' is still called, i.e. the call is not being optimized away like it should. >How-To-Repeat: Target sparc64-sun-solaris2.7 and compile 20020720-1.i with: cc1 -fpreprocessed 20020720-1.i -quiet -dumpbase 20020720-1.c -auxbase 20020720-1 -O -version -fpic -o 20020720-1.s If you grep for `link_error' in the .s file you'll see it's still being called. If you take out -fpic, the optimization succeeds. # 1 "20020720-1.c" # 1 "<built-in>" # 1 "<command line>" # 1 "20020720-1.c" extern void abort (void); extern double fabs (double); extern void link_error (void); void foo (double x) { double p, q; p = fabs (x); q = 0.0; if (p < q) link_error (); } int main() { foo (1.0); return 0; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-08 14:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-08 14:56 ghazi [this message] 2003-04-10 8:36 Eric Botcazou 2003-04-10 14:16 Roger Sayle
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=20030408145341.18271.qmail@sources.redhat.com \ --to=ghazi@caip.rutgers.edu \ --cc=gcc-gnats@gcc.gnu.org \ --cc=roger@eyesopen.com \ /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: linkBe 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).