public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ghazi@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ghazi@caip.rutgers.edu, nobody@gcc.gnu.org Subject: Re: c++/6119: sparc-sun-solaris2.7 gcc-3.1 extra g++ testsuite failure w/-fpic|-fPIC Date: Sun, 07 Apr 2002 20:15:00 -0000 [thread overview] Message-ID: <20020408031506.27752.qmail@sources.redhat.com> (raw) Synopsis: sparc-sun-solaris2.7 gcc-3.1 extra g++ testsuite failure w/-fpic|-fPIC State-Changed-From-To: open->closed State-Changed-By: ghazi State-Changed-When: Sun Apr 7 20:15:05 2002 State-Changed-Why: fixed http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6119
next reply other threads:[~2002-04-08 3:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-07 20:15 ghazi [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-31 15:36 ghazi
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=20020408031506.27752.qmail@sources.redhat.com \ --to=ghazi@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ghazi@caip.rutgers.edu \ --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).