From: "Thomas Preud'homme" <thomas.preudhomme@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, ping6] Code size optimization for the fmul/fdiv and dmul/ddiv function in libgcc
Date: Wed, 14 Jan 2015 12:01:00 -0000 [thread overview]
Message-ID: <000101d02ff1$1c67c190$553744b0$@arm.com> (raw)
Ping?
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> owner@gcc.gnu.org] On Behalf Of Thomas Preud'homme
> Sent: Thursday, November 13, 2014 4:05 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Richard Earnshaw; Ramana Radhakrishnan
> Subject: RE: [PATCH 2/3, ARM, libgcc, ping5] Code size optimization for
> the fmul/fdiv and dmul/ddiv function in libgcc
>
> [Taking over Tony's patch]
>
> Ping?
>
> Best regards,
>
> Thomas
>
> > -----Original Message-----
> > From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-
> > owner@gcc.gnu.org] On Behalf Of Tony Wang
> > Sent: Thursday, August 21, 2014 7:15 AM
> > 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
>
>
>
next reply other threads:[~2015-01-14 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 12:01 Thomas Preud'homme [this message]
2015-01-14 15:05 ` Richard Earnshaw
2015-01-27 8:11 ` Thomas Preud'homme
2015-01-27 8:33 ` Thomas Preud'homme
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='000101d02ff1$1c67c190$553744b0$@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).