From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10762 invoked by alias); 13 Feb 2006 19:06:15 -0000 Received: (qmail 10741 invoked by uid 48); 13 Feb 2006 19:06:11 -0000 Date: Mon, 13 Feb 2006 19:06:00 -0000 Message-ID: <20060213190611.10740.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/26264] Extraneous warning with __builtin_stdarg_start and optimization In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "James dot Juran at baesystems dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-02/txt/msg01361.txt.bz2 List-Id: ------- Comment #5 from James dot Juran at baesystems dot com 2006-02-13 19:06 ------- Yes, that does seem to be the case based on the ChangeLog I quoted. And of course the easy workaround for a developer is just to use __builtin_va_start instead. But is the deprecation of __builtin_stdarg_start documented anywhere? As I noted in the PR, I looked and couldn't find any mention of its deprecation. Thank you for the very quick patch though. Either applying this patch or getting rid of __builtin_stdarg_start entirely (with appropriate documentation) would seem to be preferable to the current behavior. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26264