public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: steven@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
sje@cup.hp.com
Subject: Re: c++/6685: [HPUX/IA64] g++ sets REG_POINTER for variables that contain offsets and not real pointers
Date: Mon, 12 May 2003 10:57:00 -0000 [thread overview]
Message-ID: <20030512105724.29268.qmail@sources.redhat.com> (raw)
Synopsis: [HPUX/IA64] g++ sets REG_POINTER for variables that contain offsets and not real pointers
State-Changed-From-To: open->feedback
State-Changed-By: steven
State-Changed-When: Mon May 12 10:57:23 2003
State-Changed-Why:
Dara has asked for feedback. Jason increased this PR's priority 9 months ago.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6685
next reply other threads:[~2003-05-12 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 10:57 steven [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 18:57 bangerth
2003-05-12 17:08 ehrhardt
2003-05-12 17:06 Steve Ellcey
2003-05-11 0:06 Dara Hazeghi
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=20030512105724.29268.qmail@sources.redhat.com \
--to=steven@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=sje@cup.hp.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: 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).