public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/6326: gcc compile illegal code Date: Thu, 12 Sep 2002 17:26:00 -0000 [thread overview] Message-ID: <20020913002600.23300.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6326; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: <gdr@gcc.gnu.org>, <act.kronoz@activenetwork.it>, <gcc-bugs@gcc.gnu.org>, <ptrebuc@sophia.inria.fr>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c/6326: gcc compile illegal code Date: Fri, 13 Sep 2002 01:20:38 +0100 (BST) On 10 Sep 2002 gdr@gcc.gnu.org wrote: > Synopsis: gcc compile illegal code > > State-Changed-From-To: closed->open > State-Changed-By: gdr > State-Changed-When: Tue Sep 10 16:33:59 2002 > State-Changed-Why: > Closed by mistake. > Andrew Pinski's analysis is not applicable since the part he > is reading concerns function declaration that is not a definition > and we're precisely in a case where that is irrelevant. > > Furthermore, Neil's analysis alos isn't applicable. The PR is incorrect and based on a misunderstanding of C. I gave my analysis in <http://gcc.gnu.org/ml/gcc-patches/2002-05/msg00046.html>. -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2002-09-13 0:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-12 17:26 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-13 3:56 Gabriel Dos Reis 2002-09-13 3:56 gdr 2002-09-10 16:34 gdr 2002-07-13 2:17 neil 2002-07-12 20:06 Andrew Pinski
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=20020913002600.23300.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --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).