public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, ktietz70@googlemail.com
Subject: Re: [RFA/gdb-7.2] Enable leading-mingw64-underscores by default.
Date: Thu, 08 Jul 2010 06:20:00 -0000	[thread overview]
Message-ID: <83r5je7b0c.fsf@gnu.org> (raw)
In-Reply-To: <1278530482-10575-1-git-send-email-brobecker@adacore.com>

> From: Joel Brobecker <brobecker@adacore.com>
> Cc: ktietz70@googlemail.com,	Joel Brobecker <brobecker@adacore.com>
> 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.

  reply	other threads:[~2010-07-08  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 19:21 Joel Brobecker
2010-07-08  6:20 ` Eli Zaretskii [this message]
2010-07-08 15:49   ` Joel Brobecker
2010-07-08 16:50     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r5je7b0c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ktietz70@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).