public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jim Bray <jb@as220.org> To: ebotcazou@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9888: [3.2 regression] -mcpu=k6 -Os produces out of range loop instructions Date: Wed, 12 Mar 2003 16:16:00 -0000 [thread overview] Message-ID: <20030312161600.16016.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9888; it has been noted by GNATS. From: Jim Bray <jb@as220.org> To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Eric Botcazou <ebotcazou@libertysurf.fr> Subject: Re: optimization/9888: [3.2 regression] -mcpu=k6 -Os produces out of range loop instructions Date: 12 Mar 2003 11:09:22 -0500 Dang reply-to... I didn't mean for this to go out to the whole wide world. Sorry... but if anyone out there in the World knows why I'm getting this anoncvs lock, please let me know. Thanks, Jim On Wed, 2003-03-12 at 10:48, Jim Bray wrote: > Hi Eric, > > Looks like this is in the 3.2-branch, not 3.2.2-release. Please > correct me if I'm wrong. > > At present I can't get either one. I'm still getting: > > cvs server: Updating gcc > cvs server: [10:47:02] waiting for anoncvs's lock in /cvsroot/gcc/gcc > > I haven't seen that before, and don't know what is going on there. > I'll try again later and hope it clears. I'd like to build and test > whatever branch/release you checked in to, and then advise Martin the > Gentoo GCC guy to pick it up. > > Thanks, > > Jim > > > > > > On Wed, 2003-03-12 at 05:10, ebotcazou@gcc.gnu.org wrote: > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9888 -- Jim
next reply other threads:[~2003-03-12 16:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 16:16 Jim Bray [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 16:06 Eric Botcazou 2003-03-12 15:56 Jim Bray 2003-03-12 10:12 ebotcazou 2003-03-05 10:23 ebotcazou 2003-03-04 8:41 ebotcazou
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=20030312161600.16016.qmail@sources.redhat.com \ --to=jb@as220.org \ --cc=ebotcazou@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).