public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6330: tiny C++ prog broken under -O1 Date: Mon, 22 Apr 2002 09:36:00 -0000 [thread overview] Message-ID: <20020422163601.17197.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6330; it has been noted by GNATS. From: Richard Henderson <rth@redhat.com> To: David Hanney <dh@digitalbrain.com> Cc: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/6330: tiny C++ prog broken under -O1 Date: Mon, 22 Apr 2002 09:34:33 -0700 On Mon, Apr 22, 2002 at 10:02:00AM +0100, David Hanney wrote: > .. would a compiler warning be useful here? Yes. There's already an open PR about this. r~
next reply other threads:[~2002-04-22 16:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-22 9:36 Richard Henderson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-22 2:06 David Hanney 2002-04-17 17:41 rth 2002-04-17 2:16 dh
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=20020422163601.17197.qmail@sources.redhat.com \ --to=rth@redhat.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).