9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [Patch] APE changes (2019 Lufia patches)
Date: Wed, 24 Feb 2021 18:15:09 -0800	[thread overview]
Message-ID: <B7D5933418BF8E107C9CDF7AEBE64625@eigenstate.org> (raw)
In-Reply-To: <0e170f2c1818fb21b795c2151e52adaf.squirrel@mx.sdf.org>

Quoth bsdsm@sdf.org:
> Hello,
> 
> This patch is a pared down version of the changes that Lufia made back in
> 2019; the essential changes from 'add funcs and types to APE' and all of
> 'add #include_next directive'. An unmodified diff of the former pull
> request can be found here[1] for comparison.
> 
> This has only been tested on an amd64 build. Works cleanly with tree as of
> Feb 20, 2021 changes.
> 
> 
> [1]: https://patch-diff.githubusercontent.com/raw/lufia/plan9/pull/5.diff
> 
> 
> 
> diff -r bfe93397b157 386/include/ape/_apetypes.h
> --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
> +++ b/386/include/ape/_apetypes.h	Fri Feb 12 10:59:32 2021 -0700
> @@ -0,0 +1,7 @@
> +#if !defined(__BYTE_ORDER) && defined(__LITTLE_ENDIAN)
> +#define	__BYTE_ORDER	__LITTLE_ENDIAN
> +#endif
> +
> +#if !defined(BYTE_ORDER) && defined(LITTLE_ENDIAN)
> +#define	BYTE_ORDER	LITTLE_ENDIAN
> +#endif
> diff -r bfe93397b157 amd64/include/ape/_apetypes.h
> --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
> +++ b/amd64/include/ape/_apetypes.h	Fri Feb 12 10:59:32 2021 -0700
> @@ -0,0 +1,11 @@
> +#ifndef _BITS64
> +#define _BITS64
> +#endif
> +
> +#if !defined(__BYTE_ORDER) && defined(__LITTLE_ENDIAN)
> +#define	__BYTE_ORDER	__LITTLE_ENDIAN
> +#endif
> +
> +#if !defined(BYTE_ORDER) && defined(LITTLE_ENDIAN)
> +#define	BYTE_ORDER	LITTLE_ENDIAN
> +#endif

We'd need these for all the other archs that we
support, otherwise ape will fail to build on
anything other than 386 and amd64.

> +#endif
> diff -r bfe93397b157 sys/include/ape/pthread.h

Would you be willing to split the pthread changes
out? it's a lot of tricky code, and it's rather
hard to review.

Same for the cpp include_next, which I'd rather
not commit if we can get away with it (ie, what
software is relying on that nonstandard extension,
and is it a big change to fix the software, and
maybe even upstream the change?)


  parent reply	other threads:[~2021-02-25  2:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  2:48 bsdsm
2021-02-22  4:14 ` ori
2021-02-22  5:20   ` Jens Staal
2021-02-25  2:15 ` ori [this message]
2021-02-25  2:21   ` ori
2021-02-25 16:37     ` Aaron
2021-02-25 18:06       ` ori
2021-02-26 10:28         ` cinap_lenrek
2021-02-26 15:38           ` Lucas Francesco
2021-02-26 19:23 ` [9front] " bsdsm
2021-03-01  3:41   ` ori
2021-03-15  3:20   ` ori
2021-03-15  3:36   ` ori

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=B7D5933418BF8E107C9CDF7AEBE64625@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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 NNTP newsgroup(s).