public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7888: wrong code produced by GCC 3.1 Date: Mon, 16 Sep 2002 00:56:00 -0000 [thread overview] Message-ID: <20020916075601.6674.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7888; it has been noted by GNATS. From: Nathan Sidwell <nathan@codesourcery.com> To: Andrew Pinski <pinskia@physics.uc.edu> Cc: Raul Tabasso <tabasso@tabasoft.it>, nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c/7888: wrong code produced by GCC 3.1 Date: Mon, 16 Sep 2002 08:53:43 +0100 Andrew Pinski wrote: > I could not reproduce your error: I am using gcc version: `Apple > Computer, Inc. GCC version 1161, based on gcc version 3.1 20020420 > (prerelease)' > Also `Apple Computer, Inc. GCC version 1200, based on gcc version 3.3 > 20020824 (experimental)' (apple's Darwin -Head code). > And `gcc version 3.3 20020911 (experimental)' (fsf cvs code). I suggest you report the problem to Apple. This is not an FSF release, and it appears that the current fsf tree does not have the bug. nathan -- Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC 'But that's a lie.' - 'Yes it is. What's your point?' nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2002-09-16 7:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-16 0:56 Nathan Sidwell [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-15 17:56 Andrew Pinski 2002-09-13 2:56 Raul Tabasso 2002-09-12 5:42 nathan 2002-09-12 2:36 Raul Tabasso 2002-09-11 9:01 nathan 2002-09-11 8:06 tabasso
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=20020916075601.6674.qmail@sources.redhat.com \ --to=nathan@codesourcery.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).