All known working ports

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

All known working ports

Christian Jullien-3

Hi all,

 

With Herman, who did an impressive work with elf support, we recently added many new *BSD ports.

Today, I recompiled mob and ran tests on all platforms I can connect to.

 

I’m glad to share with you the most recent list of known ports and their status.

 

Committers, a you can see, you can’t assume that the world resumes to Linux and gcc on x64. Please take care to not break those ports which take an age to compile and verify.

 

OS      | cpu   | Compilers     | Status

--------+-------+---------------+-----------------------

Linux   | arm   | gcc/clang/tcc | Ok

        | arm64 | gcc/clang/tcc | Ok

        | riscv | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

        | x86   | gcc/clang/tcc | Ok (on real PIII!!)

--------+-------+---------------+-----------------------

FreeBSD | arm64 | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

--------+-------+---------------+-----------------------

NetBSD  | arm64 | gcc/clang/tcc | Ok a clang lib fails

        | x64   | gcc/clang/tcc | Ok (only tcc static)

--------+-------+---------------+-----------------------

OpenBSD | arm64 | gcc/clang     | Ok

        | x64   | gcc/clang     | Ok

        | x86   | gcc/clang     | Ok

--------+-------+---------------+-----------------------

macOS   | x64   | clang/tcc     | Ok (only tcc static)

--------+-------+---------------+-----------------------

Windows | x64   | gcc/tcc       | Ok (Cygwin build)

        | x86   | gcc/tcc       | Ok (Cygwin build)

--------+-------+---------------+-----------------------

??      | c67   | ??            | No info

 

 

Grischka, I think it worse to move 0.9.27 to something bigger. Wdyt?

 

Christian

 

P.S. I’d love to see tcc on macOS big sur M1, any volunteers?

 


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

W. Schmid
An OS/2 port would also be nice.

Am 14.01.2021 um 12:17 schrieb Christian Jullien:

Hi all,

 

With Herman, who did an impressive work with elf support, we recently added many new *BSD ports.

Today, I recompiled mob and ran tests on all platforms I can connect to.

 

I’m glad to share with you the most recent list of known ports and their status.

 

Committers, a you can see, you can’t assume that the world resumes to Linux and gcc on x64. Please take care to not break those ports which take an age to compile and verify.

 

OS      | cpu   | Compilers     | Status

--------+-------+---------------+-----------------------

Linux   | arm   | gcc/clang/tcc | Ok

        | arm64 | gcc/clang/tcc | Ok

        | riscv | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

        | x86   | gcc/clang/tcc | Ok (on real PIII!!)

--------+-------+---------------+-----------------------

FreeBSD | arm64 | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

--------+-------+---------------+-----------------------

NetBSD  | arm64 | gcc/clang/tcc | Ok a clang lib fails

        | x64   | gcc/clang/tcc | Ok (only tcc static)

--------+-------+---------------+-----------------------

OpenBSD | arm64 | gcc/clang     | Ok

        | x64   | gcc/clang     | Ok

        | x86   | gcc/clang     | Ok

--------+-------+---------------+-----------------------

macOS   | x64   | clang/tcc     | Ok (only tcc static)

--------+-------+---------------+-----------------------

Windows | x64   | gcc/tcc       | Ok (Cygwin build)

        | x86   | gcc/tcc       | Ok (Cygwin build)

--------+-------+---------------+-----------------------

??      | c67   | ??            | No info

 

 

Grischka, I think it worse to move 0.9.27 to something bigger. Wdyt?

 

Christian

 

P.S. I’d love to see tcc on macOS big sur M1, any volunteers?

 


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

Christian Jullien-3

Depending on what you expect to do, the Windows x86 binary “probably” works in WIN32 compatible mode. Otherwise, it would be a big effort to support this OS which has not evolved since 2001 (except in its ArcaOS flavor).

 

From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=[hidden email]] On Behalf Of W. Schmid
Sent: Thursday, January 14, 2021 12:35
To: [hidden email]
Subject: Re: [Tinycc-devel] All known working ports

 

An OS/2 port would also be nice.

Am 14.01.2021 um 12:17 schrieb Christian Jullien:

Hi all,

 

With Herman, who did an impressive work with elf support, we recently added many new *BSD ports.

Today, I recompiled mob and ran tests on all platforms I can connect to.

 

I’m glad to share with you the most recent list of known ports and their status.

 

Committers, a you can see, you can’t assume that the world resumes to Linux and gcc on x64. Please take care to not break those ports which take an age to compile and verify.

 

OS      | cpu   | Compilers     | Status

--------+-------+---------------+-----------------------

Linux   | arm   | gcc/clang/tcc | Ok

        | arm64 | gcc/clang/tcc | Ok

        | riscv | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

        | x86   | gcc/clang/tcc | Ok (on real PIII!!)

--------+-------+---------------+-----------------------

FreeBSD | arm64 | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

--------+-------+---------------+-----------------------

NetBSD  | arm64 | gcc/clang/tcc | Ok a clang lib fails

        | x64   | gcc/clang/tcc | Ok (only tcc static)

--------+-------+---------------+-----------------------

OpenBSD | arm64 | gcc/clang     | Ok

        | x64   | gcc/clang     | Ok

        | x86   | gcc/clang     | Ok

--------+-------+---------------+-----------------------

macOS   | x64   | clang/tcc     | Ok (only tcc static)

--------+-------+---------------+-----------------------

Windows | x64   | gcc/tcc       | Ok (Cygwin build)

        | x86   | gcc/tcc       | Ok (Cygwin build)

--------+-------+---------------+-----------------------

??      | c67   | ??            | No info

 

 

Grischka, I think it worse to move 0.9.27 to something bigger. Wdyt?

 

Christian

 

P.S. I’d love to see tcc on macOS big sur M1, any volunteers?

 



_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

 


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

Daniel Glöckner-2
In reply to this post by Christian Jullien-3
On Thu, Jan 14, 2021 at 12:17:23PM +0100, Christian Jullien wrote:
> macOS   | x64   | clang/tcc     | Ok (only tcc static)

You reported success with dynamic linking on June 21.
Why only static this time?

Best regards,

  Daniel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

Christian Jullien-3
Something looks broken (not sure) I'll better check and tell you.

-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=[hidden email]] On Behalf Of Daniel Glöckner
Sent: Thursday, January 14, 2021 14:34
To: [hidden email]; [hidden email]
Subject: Re: [Tinycc-devel] All known working ports

On Thu, Jan 14, 2021 at 12:17:23PM +0100, Christian Jullien wrote:
> macOS   | x64   | clang/tcc     | Ok (only tcc static)

You reported success with dynamic linking on June 21.
Why only static this time?

Best regards,

  Daniel

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

Christian Jullien-3
In reply to this post by Daniel Glöckner-2

Ok I remember, in fact tcc compiled by tcc only supports static build atm on macOS.

If we compile tcc with clang both static and shared versions do work.

My test suite produces:

     56 -rwxr-xr-x    1 jullien  staff       25668 Jan 14 15:56 tinycc-clang-shared

    872 -rwxr-xr-x    1 jullien  staff      444412 Jan 14 15:55 tinycc-clang-static

    784 -rwxr-xr-x    1 jullien  staff      399508 Jan 14 15:53 tinycc-tcc-static

 

That's what (only tcc statics) means, gcc and/or clang actually work.

 

To support shared version, tcc must allow all clang macOS specific options which is not the case, I can't remember who but a maintainer asked me to not pollute tcc with all macOS clang specific options.

 

If all maintainers agree, I can try to add them back. Just tell me.

 

Note that FreeBSD also supports tcc dynamic build, hence, the revised table is as below:

 

OS      | cpu   | Compilers     | Status

--------+-------+---------------+-----------------------

Linux   | arm   | gcc/clang/tcc | Ok

        | arm64 | gcc/clang/tcc | Ok

        | riscv | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

        | x86   | gcc/clang/tcc | Ok (on real PIII!!)

--------+-------+---------------+-----------------------

FreeBSD | arm64 | gcc/clang/tcc | Ok

        | x64   | gcc/clang/tcc | Ok

--------+-------+---------------+-----------------------

NetBSD  | arm64 | gcc/clang/tcc | Ok a clang lib fails

        | x64   | gcc/clang/tcc | Ok

--------+-------+---------------+-----------------------

OpenBSD | arm64 | gcc/clang     | Ok

        | x64   | gcc/clang     | Ok

        | x86   | gcc/clang     | Ok

--------+-------+---------------+-----------------------

macOS   | x64   | clang/tcc     | Ok (only tcc static)

--------+-------+---------------+-----------------------

Windows | x64   | gcc/tcc       | Ok (Cygwin build)

        | x86   | gcc/tcc       | Ok (Cygwin build)

--------+-------+---------------+-----------------------

??      | c67   | ??            | No info

 

-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=[hidden email]] On Behalf Of Daniel Glöckner
Sent: Thursday, January 14, 2021 14:34
To: [hidden email]; [hidden email]
Subject: Re: [Tinycc-devel] All known working ports

 

On Thu, Jan 14, 2021 at 12:17:23PM +0100, Christian Jullien wrote:

> macOS   | x64   | clang/tcc     | Ok (only tcc static)

 

You reported success with dynamic linking on June 21.

Why only static this time?

 

Best regards,

 

  Daniel

 

_______________________________________________

Tinycc-devel mailing list

[hidden email]

https://lists.nongnu.org/mailman/listinfo/tinycc-devel


_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Reply | Threaded
Open this post in threaded view
|

Re: All known working ports

Steffen Nurpmeso
In reply to this post by Christian Jullien-3
Christian Jullien wrote in
 <001f01d6ea66$d5b65b30$81231190$@orange.fr>:
 |Hi all,
 |
 |With Herman, who did an impressive work with elf support, we recently added
 |many new *BSD ports.

That is great!

 |Today, I recompiled mob and ran tests on all platforms I can connect to.
 |
 |I'm glad to share with you the most recent list of known ports and their
 |status.
 |
 |Committers, a you can see, you can't assume that the world resumes to Linux
 |and gcc on x64. Please take care to not break those ports which take an age
 |to compile and verify.
 ...
 |FreeBSD | arm64 | gcc/clang/tcc | Ok
 |
 || x64   | gcc/clang/tcc | Ok

The problem i had with tcc on FreeBSD a few years ago was that
they are using extensions in their /usr/include headers that tcc
does not understand to an extend where any non-trivial program was
effectively a no-go.
Having said that, i was only interested in using tcc for
compilation of entire projects, not for embedding etc.

Thanks for all the work with tcc!, a user.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

_______________________________________________
Tinycc-devel mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel