From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9220 invoked by alias); 26 Mar 2007 20:27:19 -0000 Received: (qmail 9055 invoked by uid 48); 26 Mar 2007 20:27:06 -0000 Date: Mon, 26 Mar 2007 20:27:00 -0000 Message-ID: <20070326202706.9054.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/31367] Should not warn about use of deprecated type in deprecated struct In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "david at luyer dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-03/txt/msg02499.txt.bz2 ------- Comment #2 from david at luyer dot net 2007-03-26 21:27 ------- Two other related cases which generate warnings. I'm not sure which is the correct syntax to mark a field deprecated, but both are currently generating warnings, and marking a field which uses a deprecated type as deprecated would be another case which should not generate a warning. ============================= typedef __attribute__((deprecated)) int foo; typedef struct bar { foo __attribute__((deprecated)) baz; } bop; ============================= typedef __attribute__((deprecated)) int foo; typedef struct bar { __attribute__((deprecated)) foo baz; } bop; -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31367