66.html diff - Use MACHINE_ARCH consistently

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

66.html diff - Use MACHINE_ARCH consistently

Brad Smith-14
Fix the release notes to use MACHINE_ARCH consistently instead of
some random MACHINE mixed in.



Index: 66.html
===================================================================
RCS file: /home/cvs/www/66.html,v
retrieving revision 1.49
diff -u -p -u -p -r1.49 66.html
--- 66.html 6 Oct 2019 01:13:44 -0000 1.49
+++ 66.html 17 Oct 2019 20:41:53 -0000
@@ -81,14 +81,14 @@ to 6.6.
     <li>Fixed support for amd64 machines with greater than 1023GB
       physical memory.
     <li><a href="https://man.openbsd.org/drm.4">drm(4)</a> updates.
-    <li>The octeon platform is now using
+    <li>The mips64 architecture is now using
       <a href="https://man.openbsd.org/clang-local.1">clang(1)</a>
       as the base system compiler.
     <li>The powerpc architecture is now provided with
       <a href="https://man.openbsd.org/clang.1">clang(1)</a>, in
-      addition to aarch64, amd64, armv7, i386, mips64el, sparc64.
+      addition to aarch64, amd64, arm, i386, mips64el, sparc64.
     <li>Disabled <a href="https://man.openbsd.org/gcc.1">gcc</a> in
-      base on armv7 and i386.
+      base on arm and i386.
     <li>Prevented <a href="https://man.openbsd.org/dhclient.8">dhclient(8)</a>
       from repeatedly obtaining a new lease when the mtu is given in a
       lease.

Reply | Threaded
Open this post in threaded view
|

Re: 66.html diff - Use MACHINE_ARCH consistently

Stuart Henderson
On 2019/10/17 16:44, Brad Smith wrote:
> Fix the release notes to use MACHINE_ARCH consistently instead of
> some random MACHINE mixed in.

OK with me, any objections?

>
>
> Index: 66.html
> ===================================================================
> RCS file: /home/cvs/www/66.html,v
> retrieving revision 1.49
> diff -u -p -u -p -r1.49 66.html
> --- 66.html 6 Oct 2019 01:13:44 -0000 1.49
> +++ 66.html 17 Oct 2019 20:41:53 -0000
> @@ -81,14 +81,14 @@ to 6.6.
>      <li>Fixed support for amd64 machines with greater than 1023GB
>        physical memory.
>      <li><a href="https://man.openbsd.org/drm.4">drm(4)</a> updates.
> -    <li>The octeon platform is now using
> +    <li>The mips64 architecture is now using
>        <a href="https://man.openbsd.org/clang-local.1">clang(1)</a>
>        as the base system compiler.
>      <li>The powerpc architecture is now provided with
>        <a href="https://man.openbsd.org/clang.1">clang(1)</a>, in
> -      addition to aarch64, amd64, armv7, i386, mips64el, sparc64.
> +      addition to aarch64, amd64, arm, i386, mips64el, sparc64.
>      <li>Disabled <a href="https://man.openbsd.org/gcc.1">gcc</a> in
> -      base on armv7 and i386.
> +      base on arm and i386.
>      <li>Prevented <a href="https://man.openbsd.org/dhclient.8">dhclient(8)</a>
>        from repeatedly obtaining a new lease when the mtu is given in a
>        lease.
>

Reply | Threaded
Open this post in threaded view
|

Re: 66.html diff - Use MACHINE_ARCH consistently

Christian Weisgerber
In reply to this post by Brad Smith-14
On 2019-10-17, Brad Smith <[hidden email]> wrote:

> -    <li>The octeon platform is now using
> +    <li>The mips64 architecture is now using
>        <a href="https://man.openbsd.org/clang-local.1">clang(1)</a>
>        as the base system compiler.

This is wrong; sgi still uses gcc.  No release has been built for
sgi, but it wasn't removed from the tree, so I guess it isn't quite
dead and buried yet.

--
Christian "naddy" Weisgerber                          [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: 66.html diff - Use MACHINE_ARCH consistently

Theo de Raadt-2
Christian Weisgerber <[hidden email]> wrote:

> On 2019-10-17, Brad Smith <[hidden email]> wrote:
>
> > -    <li>The octeon platform is now using
> > +    <li>The mips64 architecture is now using
> >        <a href="https://man.openbsd.org/clang-local.1">clang(1)</a>
> >        as the base system compiler.
>
> This is wrong; sgi still uses gcc.  No release has been built for
> sgi, but it wasn't removed from the tree, so I guess it isn't quite
> dead and buried yet.

Yes, in fact the decision about which arch have gcc or clang is
done per-machine, not per-architecture:

CLANG_ARCH=aarch64 amd64 arm i386 mips64 mips64el powerpc sparc64
GCC4_ARCH=alpha hppa mips64el powerpc sh sparc64
GCC3_ARCH=m88k
LLD_ARCH=aarch64 amd64 arm i386

So the original diff is wrong.