From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Tom Tromey'" <tromey@redhat.com>,
"'Iain Buclaw'" <ibuclaw@gdcproject.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Add d_main_name to dlang.c
Date: Tue, 19 Nov 2013 21:05:00 -0000 [thread overview]
Message-ID: <00f101cee56a$2c206e20$84614a60$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <874n78mge2.fsf@fleche.redhat.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé : mardi 19 novembre 2013 15:49
> À : Iain Buclaw
> Cc : gdb-patches@sourceware.org
> Objet : Re: [PATCH] Add d_main_name to dlang.c
>
> >>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
>
> Iain> By the way, it is more preferable to use the mangled name of the
> D
> Iain> main function (_Dmain), or the pretty debug de-mangled name?
> Both
> Iain> work just as well in achieving the job.
>
> I don't think it matters.
I thought that in general, using the mangled name
would allow to find main even if you do not generate
any debug information, as long as you do not remove the
assembler symbols from the executable.
This seems like a valid reason to prefer mangled name
over demangled, no?
Pierre
next prev parent reply other threads:[~2013-11-19 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 1:53 Iain Buclaw
2013-11-19 16:09 ` Tom Tromey
2013-11-19 17:50 ` Iain Buclaw
2013-11-19 18:06 ` Tom Tromey
2013-11-19 21:05 ` Pierre Muller [this message]
[not found] ` <39451.43601527$1384894769@news.gmane.org>
2013-11-19 21:08 ` Tom Tromey
2014-01-03 18:18 ` Iain Buclaw
2014-01-07 9:53 ` Iain Buclaw
2014-01-07 10:44 ` Joel Brobecker
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='00f101cee56a$2c206e20$84614a60$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--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