From: Derrick McKee <derrick.mckee@gmail.com>
To: libc-help@sourceware.org
Subject: Multiple symbols at the same location
Date: Sat, 25 Aug 2018 21:51:00 -0000 [thread overview]
Message-ID: <CAJoBWHzkFcvXtLR_B5ZQ-4GHvXpv4tQniky3TOTokXjyhu2D3w@mail.gmail.com> (raw)
Hi,
I am a PhD. student, and in my research I noticed that there are
several versions of memmove and memcpy that are included in statically
compiled binaries. I understand that this is done for optimization
purposes (and if that is not the case, let me know!). However, some
versions of memmove and memcpy are located in different places in
.text, while others have their symbols located at the same location in
.text. For example, __memcpy_avx512_unaligned and
__memmove_avx512_unaligned have the same address, however
__memcpy_ssse3 and __memmove_ssse3 are placed at different addresses.
I assume that this is also done for optimization purposes.
Can someone give me an explanation as to why it makes sense to
separate one group of memory copying functions into two symbols, while
for others the same code is used? Thanks!
--
Derrick McKee
Phone: (703) 957-9362
Email: derrick.mckee@gmail.com
next reply other threads:[~2018-08-25 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 21:51 Derrick McKee [this message]
2018-08-27 13:09 ` Adhemerval Zanella
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=CAJoBWHzkFcvXtLR_B5ZQ-4GHvXpv4tQniky3TOTokXjyhu2D3w@mail.gmail.com \
--to=derrick.mckee@gmail.com \
--cc=libc-help@sourceware.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).