public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21513] [4.0/4.1 Regression] __builtin_expect getting in the way of uninitialized warnings Date: Mon, 31 Oct 2005 03:31:00 -0000 [thread overview] Message-ID: <20051031033136.9036.qmail@sourceware.org> (raw) In-Reply-To: <bug-21513-10614@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from mmitchel at gcc dot gnu dot org 2005-10-31 03:31 ------- This will never be release critical. -- mmitchel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21513
next prev parent reply other threads:[~2005-10-31 3:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-21513-10614@http.gcc.gnu.org/bugzilla/> 2005-10-13 1:48 ` pinskia at gcc dot gnu dot org 2005-10-31 3:31 ` mmitchel at gcc dot gnu dot org [this message] 2005-11-01 10:46 ` alexander_herrmann at yahoo dot com dot au 2005-12-17 10:27 ` [Bug tree-optimization/21513] [4.0/4.1/4.2 " bonzini at gnu dot org 2006-02-27 14:01 ` steven at gcc dot gnu dot org 2006-03-03 17:58 ` pinskia at gcc dot gnu dot org 2006-10-23 21:30 ` pinskia at gcc dot gnu dot org 2007-09-05 19:54 ` nemet at gcc dot gnu dot org 2005-05-11 13:53 [Bug c/21513] New: Obsolete uninizialized Warning message alexander_herrmann at yahoo dot com dot au 2005-05-11 14:06 ` [Bug tree-optimization/21513] [4.0/4.1 Regression] __builtin_expect getting in the way of uninitialized warnings pinskia at gcc dot gnu dot org 2005-05-28 18:00 ` pinskia at gcc dot gnu dot org 2005-08-22 12:26 ` pinskia at gcc dot gnu dot org
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=20051031033136.9036.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).