public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/25443] -fpic/-fPIC failure in gcc.dg/tree-ssa/loop-3.c
Date: Sat, 13 Jan 2007 01:02:00 -0000 [thread overview]
Message-ID: <20070113010156.2681.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25443-578@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ghazi at gcc dot gnu dot org 2007-01-13 01:01 -------
(In reply to comment #4)
> so the test fails, but the generated code is correct and optimal. I suggest
> adding -fno-pic to the test, does that look OK?
I no longer have access to the x86 boxes I was using for testing last year. So
I can't test any fix. But anyway, if I recall correctly adding -fno-pic won't
help because stuff in RUNTESTFLAGS is added *after* the dg-options flags. So
pic will still be turned on if the user selects it. Instead do something like
what's in gcc.dg/sibcall-6.c, namely:
/* { dg-skip-if "" { { i?86-*-* x86_64-*-* } && ilp32 } { "-fpic" "-fPIC" } {
"" } } */
I don't think the check for ilp32 is wanted in this case though.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25443
next prev parent reply other threads:[~2007-01-13 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 15:02 [Bug middle-end/25443] New: " ghazi at gcc dot gnu dot org
2005-12-16 15:10 ` [Bug middle-end/25443] " ghazi at gcc dot gnu dot org
2005-12-25 1:30 ` pinskia at gcc dot gnu dot org
2006-01-29 21:01 ` pinskia at gcc dot gnu dot org
2007-01-12 20:13 ` dalej at apple dot com
2007-01-13 1:02 ` ghazi at gcc dot gnu dot org [this message]
2007-01-13 1:32 ` dalej at apple dot com
2007-01-13 5:02 ` ghazi at gcc dot gnu dot org
2007-01-15 23:41 ` dalej at apple dot com
2007-01-15 23:45 ` echristo at apple dot com
2007-01-15 23:48 ` dalej at apple 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=20070113010156.2681.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).