On 14/01/15 11:56, Thomas Preud'homme wrote: > Ping? > Sorry, not ok. These symbols pollute the global namespace, yet do not use reserved names.
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. R. >> -----Original Message----- >> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches- >> ow...@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-ow...@gcc.gnu.org [mailto:gcc-patches- >>> ow...@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.w...@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 >> >> >> > > >
