From: vsp 1729 <vsp1729@gmail.com>
To: gcc@gnu.org
Subject: unsubscribe
Date: Thu, 6 May 2021 16:08:38 +0530 [thread overview]
Message-ID: <CAEhPm70kOkVedw84rKWqvJ2A8iRBU0UC7rwm=vXWyiXG+n0+UQ@mail.gmail.com> (raw)
unsubscribe
On Friday, April 30, 2021, Xun Li via llvm-dev <llvm-dev@lists.llvm.org>
wrote:
> Hi,
>
> I noticed that when compiling lambda functions, the generated function
> names use different conventions than GCC.
> Example: https://godbolt.org/z/5qvqKqEe6
> The lambda in Clang is named "_Z3barIZ3foovE3$_0EvT_", while the one
> in GCC is named "_Z3barIZ3foovEUlvE_EvT_". Their demangled names are
> also different ("void bar<foo()::$_0>(foo()::$_0)" vs "void
> bar<foo()::{lambda()#1}>(foo()::{lambda()#1})").
> Lambdas are not covered by the ABI so this is OK.
> However there are use-cases where I find it very inconvenient when
> they generate different names. For example, if we are to compare the
> performance difference of the same software compiled under Clang and
> GCC, the perf stack traces will look very different because of the
> naming differences, making it hard to compare.
> Is there any particular reason that Clang uses a different naming
> convention for lambdas, and would there be push-backs if we were to
> make it consistent with GCC?
> Thanks.
>
> --
> Xun
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
next reply other threads:[~2021-05-06 10:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 10:38 vsp 1729 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 3:58 unsubscribe Anna Ceguerra
2022-05-06 8:48 GCC 12.1 Released Richard Biener
2022-05-06 11:21 ` unsubscribe Peter Quinger
2022-04-21 19:36 unsubscribe Dubuc, Paul
2022-04-21 9:12 GCC 11.3 Released Richard Biener
2022-04-21 11:34 ` unsubscribe David Valtorta
2022-04-21 12:35 ` unsubscribe Jonathan Wakely
2021-07-22 16:25 Unsubscribe Ayers, Joseph
2021-06-01 14:05 unsubscribe Dubuc, Paul
2003-09-30 11:42 unsubscribe Gyan Ranjan Singh, Noida
2003-07-21 7:37 unsubscribe HwanYoung,Lee
1999-02-20 17:00 UNSUBSCRIBE killer
1999-02-28 22:53 ` UNSUBSCRIBE killer
1999-02-12 2:54 unsubscribe erik.eriksson
1999-02-28 22:53 ` unsubscribe erik.eriksson
1999-02-02 16:11 UNSUBSCRIBE killer
1999-02-28 22:53 ` UNSUBSCRIBE killer
1999-01-29 9:06 unsubscribe GRAVE Xavier
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='CAEhPm70kOkVedw84rKWqvJ2A8iRBU0UC7rwm=vXWyiXG+n0+UQ@mail.gmail.com' \
--to=vsp1729@gmail.com \
--cc=gcc@gnu.org \
/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).