public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Segher Boessenkool <segher@kernel•crashing.org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Quieten arch/powerpc in a allmodconfig build.
Date: Fri, 10 Apr 2009 16:51:10 -0500	[thread overview]
Message-ID: <49DFBF4E.60204@freescale.com> (raw)
In-Reply-To: <FECC6BB4-0505-4319-BCD5-81E8B1C825B5@kernel.crashing.org>

Segher Boessenkool wrote:
>> And further, there is no separation of warning classes into 
>> might-be-uninitialized and is-uninitialized-compiler-can-tell-for-sure.
> 
> Indeed.  Please file a bug report.

Done: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39731

-Scott

  reply	other threads:[~2009-04-10 21:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  4:36 [PATCH] Quieten arch/powerpc in a allmodconfig build Tony Breeds
2009-04-08  5:08 ` Michael Ellerman
2009-04-08  5:51   ` Tony Breeds
2009-04-08  6:13     ` Tony Breeds
2009-04-08  6:23       ` Michael Ellerman
2009-04-08  6:48     ` Michael Ellerman
2009-04-08  7:42       ` Geert Uytterhoeven
2009-04-08 18:47       ` Nathan Lynch
2009-04-09  0:01         ` Tony Breeds
2009-04-10  4:21           ` Nathan Lynch
2009-04-10 17:19             ` Segher Boessenkool
2009-04-09 22:46     ` Segher Boessenkool
2009-04-09 22:45       ` Tony Breeds
2009-04-09 23:11         ` Stephen Rothwell
2009-04-09 23:23           ` Segher Boessenkool
2009-04-10 18:03             ` Scott Wood
2009-04-10 18:35               ` Andreas Schwab
2009-04-10 18:43                 ` Scott Wood
2009-04-10 20:28                   ` Segher Boessenkool
2009-04-10 20:45               ` Segher Boessenkool
2009-04-10 21:51                 ` Scott Wood [this message]
2009-04-09 23:18         ` Segher Boessenkool

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=49DFBF4E.60204@freescale.com \
    --to=scottwood@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=segher@kernel$(echo .)crashing.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be 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