public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/37326] [4.4 Regression] gcc.dg/tree-ssa/ssa-store-ccp-3.c scan-tree-dump-times optimized "conststaticvariable" 1
Date: Mon, 17 Nov 2008 22:59:00 -0000	[thread overview]
Message-ID: <20081117225816.18244.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37326-276@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from sje at cup dot hp dot com  2008-11-17 22:58 -------
hppa64 is setting __PIC__ because it sets flag_pic and generates PIC code by
default but it sets flag_pic to 2 in override_options after we have already
checked its value in decode_options and used its value to set flag_shlib.  The
optimization in this test is determined by flag_shlib.  We need to either set
flag_shlib in override_options when we set flag_pic (making hppa64 a true PIC
platform) or not set flag_pic for PA64 even though it is generating PIC code or
xfail the test.

IA64 HP-UX does not set flag_pic even though the code is PIC, that is why it
does not fail.  Setting flag_shlib could make some code slower by preventing
inlining so as to allow functions to be overridden which you have to do if the
code is in a shared library.

David, do you have a prefered fix?


-- 

sje at cup dot hp dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sje at cup dot hp dot com
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-11-17 22:58:16
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37326


  parent reply	other threads:[~2008-11-17 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 20:24 [Bug testsuite/37326] New: AIL: " danglin at gcc dot gnu dot org
2008-09-02 11:35 ` [Bug testsuite/37326] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-10-22  3:06 ` mmitchel at gcc dot gnu dot org
2008-11-17 22:59 ` sje at cup dot hp dot com [this message]
2008-11-18  0:56 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-18 17:12 ` sje at cup dot hp dot com
2008-11-18 19:28 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-18 23:19 ` [Bug testsuite/37326] " jakub at gcc dot gnu dot org
2008-11-19 14:52 ` dave at hiauly1 dot hia dot nrc dot ca
2008-12-09 17:00 ` sje at gcc dot gnu dot org
2008-12-09 17:07 ` sje at cup dot hp dot com

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=20081117225816.18244.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).