Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
	gdb-patches@sourceware.org, 	Tom Tromey <tromey@redhat.com>
Subject: Re: [RFA/commit/Win64] Remove new extra leading underscore in symbol 	name
Date: Thu, 24 Jun 2010 20:41:00 -0000	[thread overview]
Message-ID: <AANLkTin-9hljUnzNZY3aP7O7Zm7IIV5JryWLi8-00Hvk@mail.gmail.com> (raw)
In-Reply-To: <20100624203216.GK2595@adacore.com>

2010/6/24 Joel Brobecker <brobecker@adacore.com>:
>> Yes, by --enable-leading-mingw64-underscores just the default in bfd
>> is changed. So it could be a work-a-round for supporting binaries
>> having non-ABI name-decoration.
>
> I'm afraid that this is what we're going to have to do.  One thing
> we need to decide on, now, is whether 7.2 should build with the old
> behavior by default or not.  If there hasn't been a GCC release
> including the ABI change yet, then perhaps it's better for the users
> if we tweak 7.2 to expect the non-ABI name-decorations.
>
> --
> Joel
>

Well, maybe the way to go. From beginning of 4.5.1 new ABI (means that
one specified by MS for this target) will be default for gcc.

Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination


  reply	other threads:[~2010-06-24 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 22:25 Joel Brobecker
2010-06-18 17:40 ` Tom Tromey
2010-06-24 18:23   ` Joel Brobecker
2010-06-24 18:31     ` Tom Tromey
2010-06-24 18:42     ` Pedro Alves
2010-06-24 19:00       ` Joel Brobecker
2010-06-24 19:25         ` Pedro Alves
2010-06-24 20:12           ` Kai Tietz
2010-06-24 20:32             ` Joel Brobecker
2010-06-24 20:41               ` Kai Tietz [this message]
2010-06-25  8:33 ` Pierre Muller

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=AANLkTin-9hljUnzNZY3aP7O7Zm7IIV5JryWLi8-00Hvk@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@redhat.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