public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tony Wang" <tony.wang@arm.com>
To: <gcc-patches@gcc.gnu.org>
Cc: "Richard Earnshaw" <Richard.Earnshaw@arm.com>,
	"Ramana Radhakrishnan" <Ramana.Radhakrishnan@arm.com>
Subject: RE: [PATCH 2/3,ARM,libgcc]Code size optimization for the fmul/fdiv and dmul/ddiv function in libgcc
Date: Thu, 28 Aug 2014 06:02:00 -0000	[thread overview]
Message-ID: <000401cfc285$94242770$bc6c7650$@arm.com> (raw)
In-Reply-To: 

Ping?

> -----Original Message-----
> From: Tony Wang [mailto:tony.wang@arm.com]
> Sent: Thursday, August 21, 2014 2:15 PM
> To: 'gcc-patches@gcc.gnu.org'
> Subject: [PATCH 2/3,ARM,libgcc]Code size optimization for the fmul/fdiv and dmul/ddiv function in libgcc
> 
> Step 2: Mark all the symbols around the fragment boundaries as function symbols, so as to generate veneer
> when the two section is too far away from each other. Also, I have both manually and using some test cases
to
> verify that IP and PSR are not alive at such point.
> 
> gcc/libgcc/ChangeLog:
> 2014-8-21   Tony Wang <tony.wang@arm.com>
> 
>         * config/arm/ieee754-sf.S: Expose symbols around fragment boundaries as function symbols.
>         * config/arm/ieee754-df.S: Same with above
> 
> BR,
> Tony


             reply	other threads:[~2014-08-28  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  6:02 Tony Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-26  2:11 Tony Wang
2014-09-16  3:00 Tony Wang
2014-09-04  2:16 Tony Wang
2014-08-21  6:14 Tony Wang

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='000401cfc285$94242770$bc6c7650$@arm.com' \
    --to=tony.wang@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).