public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-779] libgcc: pru: Place mpyll into its own section
Date: Thu, 13 May 2021 20:12:45 +0000 (GMT)	[thread overview]
Message-ID: <20210513201245.27D2D385802A@sourceware.org> (raw)

https://gcc.gnu.org/g:8aa8a2af8fdc2e0939c0d803bd45b45d251e1a3f

commit r12-779-g8aa8a2af8fdc2e0939c0d803bd45b45d251e1a3f
Author: Dimitar Dimitrov <dimitar@dinux.eu>
Date:   Sun Mar 21 16:38:51 2021 +0200

    libgcc: pru: Place mpyll into its own section
    
    This should help LD's --gc-sections feature to reduce final ELF size.
    
    libgcc/ChangeLog:
    
            * config/pru/mpyll.S (__pruabi_mpyll): Place into own section.
    
    Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>

Diff:
---
 libgcc/config/pru/mpyll.S | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libgcc/config/pru/mpyll.S b/libgcc/config/pru/mpyll.S
index 1aa12a63b2c..cd093bb6b72 100644
--- a/libgcc/config/pru/mpyll.S
+++ b/libgcc/config/pru/mpyll.S
@@ -29,6 +29,8 @@
 
 #include "pru-asm.h"
 
+	.section .text.__pruabi_mpyll, "ax"
+
 	.global	SYM(__pruabi_mpyll)
 	FUNC(__pruabi_mpyll)
 SYM(__pruabi_mpyll):


                 reply	other threads:[~2021-05-13 20:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210513201245.27D2D385802A@sourceware.org \
    --to=dimitar@gcc.gnu.org \
    --cc=gcc-cvs@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).