public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6685: [HPUX/IA64] g++ sets REG_POINTER for variables that contain offsets and not real pointers Date: Sun, 11 May 2003 00:06:00 -0000 [thread overview] Message-ID: <20030511000600.27755.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6685; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: gcc-gnats@gcc.gnu.org, sje@cup.hp.com Cc: Subject: Re: c++/6685: [HPUX/IA64] g++ sets REG_POINTER for variables that contain offsets and not real pointers Date: Sat, 10 May 2003 16:54:00 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=6685 Hello, what's the status of this bug? It was filed against gcc 3.1 which is now rather outdated. Is it by any chance fixed on 3.3 or mainline, or is it still present in current sources? Thanks, Dara
next reply other threads:[~2003-05-11 0:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-11 0:06 Dara Hazeghi [this message] 2003-05-12 10:57 steven 2003-05-12 17:06 Steve Ellcey 2003-05-12 17:08 ehrhardt 2003-05-12 18:57 bangerth
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=20030511000600.27755.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).