From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH -mm] DC395x SCSI driver: Shut up uninitialized variable build warning Date: Sun, 02 Sep 2007 16:43:28 -0400 Message-ID: <46DB2070.9010608@garzik.org> References: <46DB1BDF.4090100@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:52344 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750816AbXIBUna (ORCPT ); Sun, 2 Sep 2007 16:43:30 -0400 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Satyam Sharma Cc: Linux Kernel Mailing List , James Bottomley , Oliver Neukum , linux-scsi@vger.kernel.org, Andrew Morton , Ingo Molnar Satyam Sharma wrote: > I'll post the info as a reply to the first mail in this series. I have > fairly recent gcc (4.1.1) and I don't see us dropping support for it in > the next few years. What's important is not support lifetime, but whether or not the warning persists through version 4.1.2, 4.1.3, etc. We don't want to add markers for compiler quirks that come and go. The current markers tend to exist for a class of problems that gcc fundamentally has a tough time "seeing." Different optimizer behaviors from compiler version to compiler version are just noise[1]. Jeff [1] sometimes quite literally, in the case of compiler warnings.