public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsturm@gcc.gnu.org To: ce@hoyos.ws, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsturm@gcc.gnu.org, mark@codesourcery.com, nobody@gcc.gnu.org Subject: Re: bootstrap/10656: [3.3 regression] libffi fails with native tools on sparc-solaris2.7 Date: Thu, 08 May 2003 13:46:00 -0000 [thread overview] Message-ID: <20030508134618.25773.qmail@sources.redhat.com> (raw) Synopsis: [3.3 regression] libffi fails with native tools on sparc-solaris2.7 Responsible-Changed-From-To: unassigned->jsturm Responsible-Changed-By: jsturm Responsible-Changed-When: Thu May 8 13:46:17 2003 Responsible-Changed-Why: This patch: http://gcc.gnu.org/ml/gcc-patches/2003-05/msg00648.html The reporter mentioned failures in ffitest, for which I'll open a new PR. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10656
next reply other threads:[~2003-05-08 13:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-08 13:46 jsturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-08 9:56 Christian Ehrhardt 2003-05-07 3:16 ce
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=20030508134618.25773.qmail@sources.redhat.com \ --to=jsturm@gcc.gnu.org \ --cc=ce@hoyos.ws \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=mark@codesourcery.com \ --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).