public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Brad Lucier <lucier@math.purdue.edu> To: bkoz@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2568 Date: Fri, 25 May 2001 12:26:00 -0000 [thread overview] Message-ID: <20010525192602.20151.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2568; it has been noted by GNATS. From: Brad Lucier <lucier@math.purdue.edu> To: ro@TechFak.Uni-Bielefeld.DE (Rainer Orth) Cc: bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org, lucier@math.purdue.edu, David.Billinghurst@riotinto.com, neil@gcc.gnu.org, amacleod@cygnus.com (Andrew Macleod) Subject: Re: libstdc++/2568 Date: Fri, 25 May 2001 14:16:25 -0500 (EST) Rainer Orth wrote: > Applying Andrew's patch > > http://gcc.gnu.org/ml/gcc-patches/2001-04/msg01155.html > > allowed the bootstrap to complete, and the make check is now on it's way. Is this on the 3.0 branch or on the trunk (3.1)? I don't care if 3.0 bootstraps on sparcv9 because I don't believe that 64-bit support works on the branch because Jakub's subreg-byte patches have not been applied there, and I can't find any code that looks like this in c-lex.c on the trunk at all, i.e., I couldn't even apply this patch manually to the trunk. Brad
next reply other threads:[~2001-05-25 12:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-25 12:26 Brad Lucier [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-25 14:46 libstdc++/2568 Rainer Orth 2001-05-25 14:26 libstdc++/2568 Brad Lucier 2001-05-25 12:46 libstdc++/2568 Rainer Orth 2001-05-25 12:46 libstdc++/2568 Brad Lucier 2001-05-25 12:36 libstdc++/2568 Rainer Orth 2001-05-25 12:06 libstdc++/2568 Rainer Orth 2001-05-09 0:46 libstdc++/2568 Brad Lucier 2001-05-08 23:56 libstdc++/2568 bkoz
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=20010525192602.20151.qmail@sourceware.cygnus.com \ --to=lucier@math.purdue.edu \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@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).