public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/38261] [4.4 Regression] gcc.dg/torture/ipa-pta-1.c & gcc.dg/tree-ssa/alias-2.c fail with -fpic/-fPIC
Date: Tue, 25 Nov 2008 16:38:00 -0000 [thread overview]
Message-ID: <20081125163714.27905.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38261-578@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from hjl dot tools at gmail dot com 2008-11-25 16:37 -------
Can you use ./contrib/gcc_update to update your gcc source tree
so that we can tell which revisions you are using? Thanks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38261
next prev parent reply other threads:[~2008-11-25 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 15:49 [Bug tree-optimization/38261] New: [4.4 regression] " ghazi at gcc dot gnu dot org
2008-11-25 16:33 ` [Bug tree-optimization/38261] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-11-25 16:38 ` hjl dot tools at gmail dot com [this message]
2008-11-27 17:01 ` ghazi at gcc dot gnu dot org
2008-11-28 10:05 ` jakub at gcc dot gnu dot org
2008-11-28 10:14 ` [Bug testsuite/38261] " jakub at gcc dot gnu dot org
2008-11-28 10:53 ` jakub 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=20081125163714.27905.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).