public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@dinux.eu>
To: newlib@sourceware.org
Subject: Re: [PATCH v3 2/2] libgloss: pru: Trim crt0-minrt.o
Date: Sat, 20 Jan 2024 09:01:00 +0200	[thread overview]
Message-ID: <ZatvrC_tGO6g6_AG@kendros> (raw)
In-Reply-To: <20240104171952.1409897-2-dimitar@dinux.eu>

On Thu, Jan 04, 2024 at 07:19:52PM +0200, Dimitar Dimitrov wrote:
> Strip a few more instructions from crt0-minrt.S:
>   - Remove "halt" and rely on the infinite loop after main()'s return.
>   - Remove main()'s argc and argv argument initialization.  Host loader
>     does not set them, and typical firmware does not use them, either.
>   - Remove the __dso_handle symbol.
> 
> This should be safe because the default crt0.S is fully standards
> compliant.  Whereas crt0-minrt.S has been documented from the beginning
> to intentionally miss features in order to reduce firmware size, while
> still enabling typical PRU firmware to operate.
> 
> Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
> ---
>  libgloss/pru/crt0-minrt.S | 15 +--------------
>  1 file changed, 1 insertion(+), 14 deletions(-)

Ping.

Regards,
Dimitar

  reply	other threads:[~2024-01-20  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 17:19 [PATCH v3 1/2] libgloss: merge pru into top-level Makefile Dimitar Dimitrov
2024-01-04 17:19 ` [PATCH v3 2/2] libgloss: pru: Trim crt0-minrt.o Dimitar Dimitrov
2024-01-20  7:01   ` Dimitar Dimitrov [this message]
2024-01-20 13:46     ` Mike Frysinger
2024-01-20 15:15       ` Dimitar Dimitrov
2024-01-20 18:57         ` Mike Frysinger
2024-01-22 10:04           ` Corinna Vinschen
2024-01-22 17:27             ` Mike Frysinger
2024-01-23  9:04               ` Corinna Vinschen
2024-01-23 15:55                 ` Jeff Johnston
2024-01-22 18:57             ` Jeff Johnston

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=ZatvrC_tGO6g6_AG@kendros \
    --to=dimitar@dinux.eu \
    --cc=newlib@sourceware.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).