The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: elbingmiss@gmail.com (Álvaro Jurado)
Subject: [TUHS] Mac OS X is Unix
Date: Wed, 4 Jan 2017 11:04:37 +0100	[thread overview]
Message-ID: <CAHJeKDXX=uGS3KG0ni9ixEj7xot1ykw4AYuD46KKVTCmZK_w2g@mail.gmail.com> (raw)
In-Reply-To: <D0F059F0-0FBA-4682-B6EF-3E2A7119443E@tfeb.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

Not. Plan 9 developed a significant dependency of its original compilers.
Plan 9 cc is a caller compiler so main parts of the code couldn't work now
adapted in Harvey for gcc, clang and icc (intel) that are all callee. But
it's not a C problem, it's a compiler issue. Probably with Steve's pcc you
could too. Nerver tried, but it could be a good experiment.
At the end is extremely difficult not to be at any point toolchain
dependent, if Plan 9 original compilers could be improved enough to build
an standard ANSI program out of the tree (they are strongly dependent of
Plan 9 environment), also the Plan 9 code, that way you're suggesting would
be possible.
Anyway, for that, you wouldn't need any preprocessor code, also you
needen't to build amd64 or riscv with the same sources.

Álvaro

El 04/01/2017 10:12, "Tim Bradshaw" <tfb at tfeb.org> escribió:

> So, can you build the system with both  C11 compiler and its older
> compiler, from the same sources (so, no keeping two copies of the same
> functionality and selecting at build time based on the compiler)?  If you
> can I'm impressed.
>
> > On 4 Jan 2017, at 00:12, ron minnich <rminnich at gmail.com> wrote:
> >
> > Well, if by single-implementation, you mean single-compiler, I have a
> counter example: Harvey is Plan 9 with just enough changed to be C11
> compliant.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170104/46bea0ca/attachment.html>


  reply	other threads:[~2017-01-04 10:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 20:19 Doug McIlroy
2017-01-03 21:05 ` Charles Anthony
2017-01-03 21:33   ` [TUHS] When was #if introduced in C? (was: Re: Mac OS X is Unix) Michael Kjörling
2017-01-03 21:53     ` Robert Swierczek
2017-01-03 21:57       ` Clem Cole
2017-01-03 21:56     ` Clem Cole
2017-01-03 21:35 ` [TUHS] Mac OS X is Unix Clem Cole
2017-01-03 22:10   ` Lyndon Nerenberg
2017-01-03 21:39 ` Lyndon Nerenberg
2017-01-03 22:12   ` ron minnich
2017-01-03 23:39     ` Tim Bradshaw
2017-01-04  0:12       ` ron minnich
2017-01-04  9:11         ` Tim Bradshaw
2017-01-04 10:04           ` Álvaro Jurado [this message]
2017-01-04  0:13 ` Steve Johnson
2017-01-04  3:50 ` Dan Cross
2017-01-04 12:26   ` Tim Bradshaw
2017-01-04 13:49     ` Random832
2017-01-04 15:02     ` Dan Cross
2017-01-04 17:14       ` tfb

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='CAHJeKDXX=uGS3KG0ni9ixEj7xot1ykw4AYuD46KKVTCmZK_w2g@mail.gmail.com' \
    --to=elbingmiss@gmail.com \
    /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).