From: Mike Frysinger <vapier@gentoo.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org
Subject: Re: [patch] handle unaligned arm abs relocs
Date: Mon, 19 Dec 2011 18:27:00 -0000 [thread overview]
Message-ID: <201112191326.59465.vapier@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1112191738400.28997@digraph.polyomino.org.uk>
[-- Attachment #1: Type: Text/Plain, Size: 1149 bytes --]
On Monday 19 December 2011 12:45:30 Joseph S. Myers wrote:
> On Mon, 12 Dec 2011, Mike Frysinger wrote:
> > + /* Support relocations on mis-aligned offsets. */
> > + memcpy (&reloc_value, reloc_addr_arg, sizeof (reloc_value));
> > + reloc_value += value;
> > + memcpy (reloc_addr_arg, &reloc_value, sizeof (reloc_value));
>
> It seems from the discussion that it would be useful to see exactly what
> code ends up getting generated for these memcpy calls. Is it a function
> call or inlined? What about all the other memcpy calls in the dynamic
> linker? For calls to memcpy that really are function calls, do they end
> up going through the PLT, or do they end up as direct calls to the copy of
> memcpy in the dynamic linker (given that it's linked with a version script
> that hides memcpy along with all the other libc functions it uses, so it
> shouldn't be necessary for calls to go through the PLT)?
i was in the process of implementing Richard's suggestion for using a struct
and gcc attributes. but i'm hitting unrelated arm build failures which i'm
trying to resolve before moving on ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-19 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 0:20 Mike Frysinger
2011-12-14 22:05 ` Carlos O'Donell
2011-12-14 22:29 ` Mike Frysinger
2011-12-14 22:44 ` Carlos O'Donell
2011-12-15 17:48 ` Richard Henderson
2011-12-19 17:45 ` Joseph S. Myers
2011-12-19 18:27 ` Mike Frysinger [this message]
2011-12-19 19:57 ` Joseph S. Myers
2012-08-12 5:50 ` [PATCH v2] arm: handle unaligned ABS relocs Mike Frysinger
2012-08-12 13:01 ` Joseph S. Myers
2012-08-12 14:35 ` Mike Frysinger
2012-08-12 15:55 ` Joseph S. Myers
2012-08-12 18:51 ` Mike Frysinger
2012-08-12 13:26 ` Carlos O'Donell
2012-08-12 14:05 ` Andreas Schwab
2012-08-12 15:57 ` Joseph S. Myers
2012-08-14 21:49 ` Roland McGrath
2012-08-15 1:38 ` Mike Frysinger
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=201112191326.59465.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@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).