From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 886 invoked by alias); 8 Jul 2010 06:20:01 -0000 Received: (qmail 874 invoked by uid 22791); 8 Jul 2010 06:20:01 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_JMF_BR,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 08 Jul 2010 06:19:53 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0L58008006W5C500@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Thu, 08 Jul 2010 09:19:44 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.120.144]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L58003RI6WRAVG0@a-mtaout22.012.net.il>; Thu, 08 Jul 2010 09:19:42 +0300 (IDT) Date: Thu, 08 Jul 2010 06:20:00 -0000 From: Eli Zaretskii Subject: Re: [RFA/gdb-7.2] Enable leading-mingw64-underscores by default. In-reply-to: <1278530482-10575-1-git-send-email-brobecker@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org, ktietz70@googlemail.com Reply-to: Eli Zaretskii Message-id: <83r5je7b0c.fsf@gnu.org> References: <1278530482-10575-1-git-send-email-brobecker@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-07/txt/msg00145.txt.bz2 > From: Joel Brobecker > Cc: ktietz70@googlemail.com, Joel Brobecker > Date: Wed, 7 Jul 2010 12:21:22 -0700 > > There has been a recent ABI change made in GCC for x64-windows, and > the corresponding change was made in binutils/GCC at the same time. > This change must be synchronized between GCC & GDB, because they must > both follow the same convention. > > While this change was made, and backward-compatibility switch was > added: --enable-leading-mingw64-underscores. > > Until we have a GCC release containing that ABI change (scheduled for > GCC 4.5.1), I think it is more helpful for this GDB release to assume > the old ABI. Is this a build-time only option? Or can it be toggled at run time? If the former, I think it is a very bad idea to have the ABI fixed at build time, because most users of MinGW do not build their own GDB. At the time when 2 incompatible ABIs coexist, it is very important to have GDB that could adapt to either. If the latter, is this issue documented anywhere (I cannot find it)? If it is documented, why doesn't this patch include a suitable change for that documentation? If it isn't, please add it, and please include in the docs the symptoms of using the wrong ABI, which is when the user should set this option accordingly.