public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/4] libgloss: convert a few more arches to automake
Date: Mon, 9 Jan 2023 11:51:53 +0100	[thread overview]
Message-ID: <Y7vxyYJNX8C0Br1c@calimero.vinschen.de> (raw)
In-Reply-To: <20221221015809.4154-1-vapier@gentoo.org>

On Dec 20 20:58, Mike Frysinger wrote:
> This speeds the build up and simplifies the source rules.  It also
> gets us to ~20% arch conversion (9/49), so hopefully it will make
> it easier for new ports to use (more examples), and encourage some
> existing ones to convert.
> 
> Mostly I wanted to burn down aarch64 & arm, but I did arc & d30v
> too since they were small & easy.
> 
> Verified that `make install` produces the same set of files with
> the same contents (at the disassembly level).
> 
> Mike Frysinger (4):
>   libgloss: merge aarch64 into top-level Makefile
>   libgloss: merge arm into top-level Makefile
>   libgloss: merge arc into top-level Makefile
>   libgloss: merge d30v into top-level Makefile

LGTM.


Thanks,
Corinna


      parent reply	other threads:[~2023-01-09 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21  1:58 Mike Frysinger
2022-12-21  1:58 ` [PATCH 1/4] libgloss: merge aarch64 into top-level Makefile Mike Frysinger
2022-12-21  1:58 ` [PATCH 2/4] libgloss: merge arm " Mike Frysinger
2022-12-21  1:58 ` [PATCH 3/4] libgloss: merge arc " Mike Frysinger
2022-12-21  1:58 ` [PATCH 4/4] libgloss: merge d30v " Mike Frysinger
2023-01-09 10:51 ` Corinna Vinschen [this message]

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=Y7vxyYJNX8C0Br1c@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --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).