public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Thomas Preud'homme" <thomas.preudhomme@arm.com>
To: "Thomas Preud'homme" <Thomas.Preudhomme@arm.com>,
	"Richard Earnshaw" <Richard.Earnshaw@arm.com>,
	<gcc-patches@gcc.gnu.org>
Cc: "Ramana Radhakrishnan" <Ramana.Radhakrishnan@arm.com>
Subject: RE: [PATCH 2/3, ARM, libgcc, ping6] Code size optimization for the fmul/fdiv and dmul/ddiv function in libgcc
Date: Tue, 27 Jan 2015 08:33:00 -0000	[thread overview]
Message-ID: <001401d039f3$70c306d0$52491470$@arm.com> (raw)
In-Reply-To: <001201d039f1$3b73c9d0$b25b5d70$@arm.com>

> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Thomas Preud'homme
> 
> >
> > Secondly, in a shared library environment you need to ensure that
> these
> > names remain private to the instance linked into the library, so that
> > you don't end up going through the PLT for each branch between
> blocks.
> 
> Right. I'll post something for this shortly.

My apologies, this is also already the case since these are local symbols.

The first bleq Lml_s in aeabi_dmul is encoded as 0x0b00006f which is the
address of the code that starts at Lml_s label just below. I cannot see any
Lml entry in the plt.

Best regards,

Thomas 




  reply	other threads:[~2015-01-27  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 12:01 Thomas Preud'homme
2015-01-14 15:05 ` Richard Earnshaw
2015-01-27  8:11   ` Thomas Preud'homme
2015-01-27  8:33     ` Thomas Preud'homme [this message]
2015-04-30  7:43     ` Thomas Preud'homme

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='001401d039f3$70c306d0$52491470$@arm.com' \
    --to=thomas.preudhomme@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@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).