public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33187] Missed cmove opportunity
Date: Thu, 10 Jan 2008 14:08:00 -0000 [thread overview]
Message-ID: <20080110070108.24022.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33187-1649@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from ubizjak at gmail dot com 2008-01-10 07:01 -------
(In reply to comment #6)
> Uros, the testcase (gcc.target/i386/cmov7.c) fails on x86 with -fpic/-fPIC.
> Real bug, or skip with pic?
No, but insn RTX costs is slightly increased for -fpic. From ix86_rtx_cost():
--cut here--
case SYMBOL_REF:
if (TARGET_64BIT && !x86_64_immediate_operand (x, VOIDmode))
*total = 3;
else if (TARGET_64BIT && !x86_64_zext_immediate_operand (x, VOIDmode))
*total = 2;
else if (flag_pic && SYMBOLIC_CONST (x)
&& (!TARGET_64BIT
|| (!GET_CODE (x) != LABEL_REF
&& (GET_CODE (x) != SYMBOL_REF
|| !SYMBOL_REF_LOCAL_P (x)))))
*total = 1;
else
*total = 0;
return true;
--cut here--
Adding -mbranch-cost=5 to dg-options would remove this failure.
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|4.2.0 4.3.0 |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33187
next prev parent reply other threads:[~2008-01-10 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 10:34 [Bug middle-end/33187] New: " ubizjak at gmail dot com
2007-08-25 12:39 ` [Bug middle-end/33187] " ubizjak at gmail dot com
2007-08-25 13:25 ` rguenth at gcc dot gnu dot org
2007-08-27 20:23 ` ubizjak at gmail dot com
2007-09-04 10:07 ` uros at gcc dot gnu dot org
2007-09-04 10:10 ` ubizjak at gmail dot com
2008-01-09 18:44 ` ghazi at gcc dot gnu dot org
2008-01-10 14:08 ` ubizjak at gmail dot com [this message]
2008-01-11 4:38 ` ghazi at gcc dot gnu dot org
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=20080110070108.24022.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).