From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20325 invoked by alias); 13 Jun 2006 15:26:48 -0000 Received: (qmail 20317 invoked by uid 22791); 13 Jun 2006 15:26:47 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.12) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Jun 2006 15:26:42 +0000 Received: from lois.corp.google.com (lois.corp.google.com [172.24.0.50]) by smtp-out.google.com with ESMTP id k5DFQYXU016849; Tue, 13 Jun 2006 08:26:34 -0700 Received: from smtp.google.com (angband.corp.google.com [192.168.15.227]) by lois.corp.google.com with ESMTP id k5DFQUK4006634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Jun 2006 08:26:31 -0700 Received: from localhost.localdomain.google.com (200.sub-70-199-108.myvzw.com [70.199.108.200]) (authenticated bits=0) by smtp.google.com (8.13.6/8.13.6) with ESMTP id k5DFQNdU002760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Jun 2006 08:26:29 -0700 To: robbie.doggie@gmx.net Cc: gcc-help@gcc.gnu.org Subject: Re: Fwd: Re: Re: How to turn off a warning in a file References: <20060613130121.31120@gmx.net> From: Ian Lance Taylor Date: Tue, 13 Jun 2006 15:26:00 -0000 In-Reply-To: <20060613130121.31120@gmx.net> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2006-06/txt/msg00112.txt.bz2 robbie.doggie@gmx.net writes: > > | Is it possible to turn off this warning for these files? > > > > Append -Wno-virtual-dtor. > > Ok, but actually I'd like to keep it turned on for other files. In other compilers there's a possibility with #pragma. But I haven't found out whether that's possible with gcc, too. gcc does not support any sort of #pragma or _Pragma or attribute to disable specific warnings. However, there is some ongoing work to implement this in a future (post 4.2) release. Ian