Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #171992 > unrolled thread
| Started by | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| First post | 2023-08-10 04:29 -0700 |
| Last post | 2023-09-13 09:40 -0700 |
| Articles | 20 on this page of 359 — 21 participants |
Back to article view | Back to comp.lang.c
bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-10 04:29 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-10 12:57 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-10 05:07 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-10 13:14 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-10 06:53 -0700
Re: bart again (UCX64) cross@spitfire.i.gajendra.net (Dan Cross) - 2023-08-16 11:52 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-16 02:31 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-28 03:30 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-28 11:43 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-28 03:47 -0700
Re: bart again (UCX64) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-09-04 18:43 -0700
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-10 04:59 -0700
Re: bart again (UCX64) Anton Shepelev <anton.txt@g{oogle}mail.com> - 2023-08-28 17:45 +0300
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-28 19:19 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-29 22:01 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-29 20:00 -0700
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 00:25 -0700
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 01:35 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-30 11:38 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 07:06 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-30 15:53 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 12:46 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-30 22:59 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 15:54 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 00:17 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 16:30 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 11:58 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 05:32 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 14:45 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 07:43 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 15:56 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 08:38 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 12:56 -0700
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-08-31 22:09 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 10:12 +0200
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 23:53 -0700
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-08-31 14:39 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-08-31 20:56 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-08-31 14:36 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 15:30 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 16:17 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-08-31 19:36 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 20:26 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 13:17 -0700
Verbosity in command output (Was: bart again (UCX64)) gazelle@shell.xmission.com (Kenny McCormack) - 2023-08-31 21:43 +0000
Re: Verbosity in command output (Was: bart again (UCX64)) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-31 23:31 +0000
Re: Verbosity in command output (Was: bart again (UCX64)) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-08-31 21:36 -0700
Re: Verbosity in command output (Was: bart again (UCX64)) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 17:22 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 23:07 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 15:32 -0700
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-08-31 22:05 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-08-31 22:07 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 23:18 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-08-31 23:03 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 16:46 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 01:44 +0100
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 18:09 -0700
Re: bart again (UCX64) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-08-31 18:11 -0700
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-31 18:14 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 01:38 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 02:40 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 01:29 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 20:28 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 11:10 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 12:01 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 13:20 +0200
Re: bart again (UCX64) Richard Harnden <richard.nospam@gmail.com> - 2023-09-01 13:08 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 13:39 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 15:29 +0200
Re: bart again (UCX64) Richard Harnden <richard.nospam@gmail.com> - 2023-09-01 14:32 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 18:14 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 19:01 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 18:53 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-01 14:53 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 15:57 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-01 19:07 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 19:27 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 18:55 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 21:27 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 20:46 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 22:29 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 22:19 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 13:56 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 15:31 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 16:05 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 03:17 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 10:34 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-04 03:07 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 11:43 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-04 04:21 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 17:16 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 18:33 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-05 01:33 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-04 15:27 +0200
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 17:18 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-04 16:26 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 19:33 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-04 19:17 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 20:48 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 21:25 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-04 21:56 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-05 01:34 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 21:06 +0100
Re: bart again (UCX64) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-09-04 13:09 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-04 16:04 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 00:52 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-04 17:16 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 15:33 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-05 14:55 +0000
Re: bart again (UCX64) Bobby Moore <bobbymoore018@gmail.com> - 2023-09-05 08:30 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-05 17:31 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 18:06 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 17:54 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-05 20:10 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 20:57 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-05 22:37 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 22:05 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-05 15:10 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 22:32 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-07 06:49 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-06 16:08 +0200
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-06 07:53 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-06 17:35 +0200
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-06 09:37 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-06 20:49 +0200
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-06 19:51 +0000
Re: bart again (UCX64) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-09-06 12:52 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 00:36 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 17:06 -0700
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-06 18:47 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-07 11:11 +0200
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-07 04:04 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-07 13:24 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-06 18:13 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-06 21:17 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-06 22:24 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-07 11:37 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 11:53 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-07 13:33 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 14:36 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 22:59 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 16:58 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-08 00:35 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 20:41 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 20:47 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-05 14:07 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 22:22 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-05 15:26 -0700
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-05 18:26 -0700
Re: bart again (UCX64) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-09-07 23:15 -0400
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-05 13:48 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 21:36 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-05 13:24 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-04 15:46 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 17:44 +0200
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-02 01:14 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-01 18:13 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 01:43 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 17:51 +0200
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 17:58 +0200
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-02 23:28 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-02 20:09 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-03 07:15 +0000
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-03 03:03 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-03 18:53 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 16:24 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-03 12:22 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 02:01 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-05 21:40 -0700
[OT] Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 17:06 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-03 18:02 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 10:39 +0100
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-02 07:33 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 16:26 +0100
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-02 09:03 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 19:22 +0100
Re: bart again (UCX64) vallor <vallor@cultnix.org> - 2023-09-05 01:38 +0000
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-04 20:05 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 16:45 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 06:49 +0000
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-05 05:30 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-05 17:16 +0000
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 08:47 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 19:57 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 19:01 -0700
Re: bart again (UCX64) James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-09-09 01:14 -0400
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-09 05:22 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 12:51 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-02 12:58 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 16:29 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 20:00 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 00:08 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 01:36 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 02:41 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 17:49 +0200
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 18:32 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-01 18:59 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 18:02 +0200
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-03 15:54 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 19:50 +0200
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-03 21:25 +0000
Re: bart again (UCX64) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-09-03 16:44 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-03 11:47 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 18:16 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 17:48 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 19:12 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 18:49 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 21:33 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 21:09 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 22:41 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 22:34 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-01 15:51 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 14:06 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 17:27 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-01 16:02 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 01:50 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 01:12 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-01 19:13 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 11:57 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 18:19 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 19:53 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-03 06:32 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 16:02 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 18:11 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-03 11:31 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 20:07 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 22:08 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 03:16 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-04 10:54 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 11:06 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-04 14:54 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-04 22:02 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-05 01:31 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-05 02:24 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 04:29 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-05 21:06 -0700
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-06 01:03 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 20:58 +0100
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-06 19:21 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 20:18 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-06 13:07 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 22:41 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-06 15:56 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 00:53 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-06 18:47 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 17:25 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-12 10:32 -0700
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-04 18:30 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-06 03:04 +0100
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-06 21:48 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-07 06:10 +0000
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-07 02:06 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-07 15:52 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 14:18 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 15:28 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-07 16:54 +0200
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 17:02 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-07 16:12 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 16:17 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 17:37 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 14:51 -0700
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-08 00:46 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 11:06 +0200
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 10:19 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 15:55 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 15:16 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 17:02 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 16:15 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 17:51 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 17:24 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 21:53 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 21:34 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 17:25 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 21:37 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 21:02 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 16:14 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 16:09 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-07 17:34 +0100
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-07 17:22 +0000
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-07 11:44 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 15:16 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-07 23:48 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-07 17:16 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 11:16 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-08 10:51 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 13:00 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-08 13:05 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 16:11 +0200
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-09 00:56 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-09 00:47 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-09 18:49 +0200
Re: bart again (UCX64) Richard Damon <Richard@Damon-Family.org> - 2023-09-09 10:27 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-10 12:06 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-08 05:03 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-08 13:39 +0100
Re: bart again (UCX64) candycanearter07 <no@thanks.net> - 2023-09-08 07:49 -0500
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-09 01:07 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-09 18:51 +0200
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-08 16:35 +0200
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-09 01:04 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-04 14:14 +0000
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-04 16:59 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-04 15:41 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-04 18:15 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-04 18:57 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-30 09:23 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-30 15:55 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 17:10 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-02 13:13 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-02 22:50 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-02 14:54 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-01 19:02 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-02 22:42 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-02 15:08 -0700
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 02:00 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 23:18 +0100
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 02:28 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-03 06:58 +0000
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 15:52 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-03 11:02 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 16:25 +0200
Re: bart again (UCX64) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-09-03 16:49 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 16:16 +0200
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-02 18:11 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-02 22:08 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 16:48 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-02 14:52 -0700
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-03 02:23 -0700
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-03 03:47 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-03 18:44 +0000
Re: bart again (UCX64) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-09-03 18:01 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-03 16:59 +0200
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-03 17:50 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 10:43 +0200
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-01 02:17 -0700
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 13:26 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 11:35 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 13:39 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 14:09 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 15:33 +0200
Re: bart again (UCX64) Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2023-09-01 05:14 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 17:41 +0000
Re: bart again (UCX64) scott@slp53.sl.home (Scott Lurndal) - 2023-09-01 18:21 +0000
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-09-01 14:31 -0700
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-01 22:39 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-09-02 07:07 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-31 19:17 +0000
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-31 19:28 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 21:03 +0100
Re: bart again (UCX64) David Brown <david.brown@hesbynett.no> - 2023-09-01 11:23 +0200
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-31 20:50 +0100
Re: bart again (UCX64) Kaz Kylheku <864-117-4973@kylheku.com> - 2023-08-31 23:12 +0000
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-09-01 02:25 +0100
Re: bart again (UCX64) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-08-31 20:37 -0700
Re: bart again (UCX64) Paul Edwards <mutazilah@gmail.com> - 2023-08-30 07:51 -0700
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-30 16:09 +0100
Re: bart again (UCX64) Bart <bc@freeuk.com> - 2023-08-30 20:17 +0100
Re: bart again (UCX64) Michael S <already5chosen@yahoo.com> - 2023-08-29 04:46 -0700
Buy Magic Mushrooms online Buy Magic Mushroom Chocolate Bars <taresa67kolyta@gmail.com> - 2023-09-13 09:40 -0700
Page 1 of 18 [1] 2 3 … 18 Next page →
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-10 04:29 -0700 |
| Subject | bart again (UCX64) |
| Message-ID | <b74c088d-09e6-4842-8b6c-1921d68154c7n@googlegroups.com> |
Hi Bart. I'm not sure what your goals are, but at one point you were interested in the executable loader code in PDOS, to the point that you even compiled it with a 64-bit C compiler and pointed out issues with it. I corrected those issues, but I don't think you used it again. And at one point you released a generated 64-bit compiler suitable for a Win64 environment with msvcrt.dll. Note that at the time I was only doing 32-bit coding, so I didn't test the fixes that I made, nor was I able to use the C compiler for anything I was trying to do. As of a couple of hours ago, that has changed. There is a version of PDOS - basically I convert the UEFI OS into a basic Win64 OS - there wasn't a lot of "glue" required to do that. Since we did the original activity above, there have been new developments such as a public domain 64-bit coff linker. So now there is a purely public domain distribution called "University Challenge x64" available at http://pdos.org The only thing missing in the toolchain is a viable C compiler. SubC is included, but it is only a subset of C90. Can you tell me what the current status is of your public domain C compiler and whether you are interested in getting it to run on this new Win64 environment? Thanks. Paul.
[toc] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-10 12:57 +0100 |
| Message-ID | <ub2jbh$c32q$1@dont-email.me> |
| In reply to | #171992 |
On 10/08/2023 12:29, Paul Edwards wrote: > Hi Bart. > > I'm not sure what your goals are, but at one point you were > interested in the executable loader code in PDOS, to the > point that you even compiled it with a 64-bit C compiler > and pointed out issues with it. > > I corrected those issues, but I don't think you used it again. > > And at one point you released a generated 64-bit compiler > suitable for a Win64 environment with msvcrt.dll. > > Note that at the time I was only doing 32-bit coding, so I > didn't test the fixes that I made, nor was I able to use > the C compiler for anything I was trying to do. > > As of a couple of hours ago, that has changed. > > There is a version of PDOS - basically I convert the UEFI > OS into a basic Win64 OS - there wasn't a lot of "glue" > required to do that. > > Since we did the original activity above, there have been > new developments such as a public domain 64-bit coff > linker. > > So now there is a purely public domain distribution > called "University Challenge x64" available at http://pdos.org > > The only thing missing in the toolchain is a viable C compiler. > > SubC is included, but it is only a subset of C90. > > Can you tell me what the current status is of your public > domain C compiler and whether you are interested in > getting it to run on this new Win64 environment? I think it's best to forget my compiler: * I've lost interest in C and in implementing it. (It seems mainly a tool for raising my blood pressure.) * The compiler is non conforming in many ways, and buggy * It's not written in C, and the tool used to create a C rendering is being deprecated * Its output is anyway not usually an object file; it is ASM in a special format, directly assembled into EXE files * There was a .OBJ format that could be produced, but that is no longer viable, as my compiler's code is intended for low memory (within first 2GB) at a fixed address. But modern OSes and linkers now like to load at arbitrary, high addresses, which only works with position-independent code. I may anyway, at any time, decide to just delete the lot. I just don't want any external pressures or responsibilities. However there must be 100s of small, amateur C compilers out there, you just have to look for them. Tiny C is open source and one of the best.
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-10 05:07 -0700 |
| Message-ID | <ed9d3434-41da-4289-897a-dfdc23f7b8e8n@googlegroups.com> |
| In reply to | #171993 |
On Thursday, August 10, 2023 at 7:57:52 PM UTC+8, Bart wrote: > * There was a .OBJ format that could be produced, but that is no > longer viable, as my compiler's code is intended for low memory > (within first 2GB) at a fixed address. But modern OSes and linkers > now like to load at arbitrary, high addresses, which only works with > position-independent code. We aren't using what you would presumably call "modern OSes and linkers". Even though they are only hours/days old, loading below 2 GB is not an issue - we control all components except EFI, but you can request EFI to provide memory below a certain point, which is all that is needed. > I may anyway, at any time, decide to just delete the lot. I just don't > want any external pressures or responsibilities. Ok, sorry to hear your interests have changed. > However there must be 100s of small, amateur C compilers out there, you > just have to look for them. Tiny C is open source and one of the best. Almost all of them are copyrighted. I believe yours is the most advanced public domain one, and then there is SubC. As you noted - your version can't really be maintained, so the challenge would be on to bring SubC up to your (C90) level. BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-10 13:14 +0100 |
| Message-ID | <ub2kbv$c6ds$1@dont-email.me> |
| In reply to | #171997 |
On 10/08/2023 13:07, Paul Edwards wrote: > On Thursday, August 10, 2023 at 7:57:52 PM UTC+8, Bart wrote: > >> * There was a .OBJ format that could be produced, but that is no >> longer viable, as my compiler's code is intended for low memory >> (within first 2GB) at a fixed address. But modern OSes and linkers >> now like to load at arbitrary, high addresses, which only works with >> position-independent code. > > We aren't using what you would presumably call "modern > OSes and linkers". Even though they are only hours/days > old, loading below 2 GB is not an issue - we control all > components except EFI, but you can request EFI to > provide memory below a certain point, which is all that is > needed. > >> I may anyway, at any time, decide to just delete the lot. I just don't >> want any external pressures or responsibilities. > > Ok, sorry to hear your interests have changed. > >> However there must be 100s of small, amateur C compilers out there, you >> just have to look for them. Tiny C is open source and one of the best. > > Almost all of them are copyrighted. In a post-apocalyptic scenario (I think that's partly what you want this stuff for), I don't think many will care about copyrights!
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-10 06:53 -0700 |
| Message-ID | <0f0419b1-abb1-49b8-8552-a1c455fdae16n@googlegroups.com> |
| In reply to | #171999 |
On Thursday, August 10, 2023 at 8:16:56 PM UTC+8, Bart wrote: > > Almost all of them are copyrighted. > In a post-apocalyptic scenario (I think that's partly what you want this > stuff for), I don't think many will care about copyrights! No, a potential apocalypse is a scenario where we MAY need to go through the entire development of processor again. I am after software that has been released without strings attached. There are not 100s of C90-compliant compilers to choose between. There are zero. The rest of the toolchain, and editor, and OS, are all public domain (by various people). Only the C compiler remains, and I have seen about 6 talented people willing to donate their work to the public domain who have tried to write a C compiler, but all have failed to reach C90 (some haven't officially given up yet though). Despite the numerous number of people who like to claim how easy it is, without actually doing it. BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | cross@spitfire.i.gajendra.net (Dan Cross) |
|---|---|
| Date | 2023-08-16 11:52 +0000 |
| Message-ID | <ubid9c$5cc$1@reader2.panix.com> |
| In reply to | #171999 |
In article <ub2kbv$c6ds$1@dont-email.me>, Bart <bc@freeuk.com> wrote: >On 10/08/2023 13:07, Paul Edwards wrote: >> On Thursday, August 10, 2023 at 7:57:52 PM UTC+8, Bart wrote: >> >>> * There was a .OBJ format that could be produced, but that is no >>> longer viable, as my compiler's code is intended for low memory >>> (within first 2GB) at a fixed address. But modern OSes and linkers >>> now like to load at arbitrary, high addresses, which only works with >>> position-independent code. >> >> We aren't using what you would presumably call "modern >> OSes and linkers". Even though they are only hours/days >> old, loading below 2 GB is not an issue - we control all >> components except EFI, but you can request EFI to >> provide memory below a certain point, which is all that is >> needed. >> >>> I may anyway, at any time, decide to just delete the lot. I just don't >>> want any external pressures or responsibilities. >> >> Ok, sorry to hear your interests have changed. >> >>> However there must be 100s of small, amateur C compilers out there, you >>> just have to look for them. Tiny C is open source and one of the best. >> >> Almost all of them are copyrighted. > >In a post-apocalyptic scenario (I think that's partly what you want this >stuff for), I don't think many will care about copyrights! PLEASE don't feed this troll. - Dan C.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-16 02:31 +0100 |
| Message-ID | <ubh8tq$31gtm$1@dont-email.me> |
| In reply to | #171993 |
On 10/08/2023 12:57, Bart wrote: > On 10/08/2023 12:29, Paul Edwards wrote: > > Hi Bart. > > > > I'm not sure what your goals are, but at one point you were > > interested in the executable loader code in PDOS, to the > > point that you even compiled it with a 64-bit C compiler > > and pointed out issues with it. > > > > I corrected those issues, but I don't think you used it again. > > > > And at one point you released a generated 64-bit compiler > > suitable for a Win64 environment with msvcrt.dll. > > > > Note that at the time I was only doing 32-bit coding, so I > > didn't test the fixes that I made, nor was I able to use > > the C compiler for anything I was trying to do. > > > > As of a couple of hours ago, that has changed. > > > > There is a version of PDOS - basically I convert the UEFI > > OS into a basic Win64 OS - there wasn't a lot of "glue" > > required to do that. > > > > Since we did the original activity above, there have been > > new developments such as a public domain 64-bit coff > > linker. > > > > So now there is a purely public domain distribution > > called "University Challenge x64" available at http://pdos.org > > > > The only thing missing in the toolchain is a viable C compiler. > > > > SubC is included, but it is only a subset of C90. > > > > Can you tell me what the current status is of your public > > domain C compiler and whether you are interested in > > getting it to run on this new Win64 environment? > > I think it's best to forget my compiler: > > * I've lost interest in C and in implementing it. (It seems mainly > a tool for raising my blood pressure.) > > * The compiler is non conforming in many ways, and buggy > > * It's not written in C, and the tool used to create a C rendering > is being deprecated > > * Its output is anyway not usually an object file; it is ASM in > a special format, directly assembled into EXE files > > * There was a .OBJ format that could be produced, but that is no > longer viable, as my compiler's code is intended for low memory > (within first 2GB) at a fixed address. But modern OSes and linkers > now like to load at arbitrary, high addresses, which only works with > position-independent code. > > I may anyway, at any time, decide to just delete the lot. I just don't > want any external pressures or responsibilities. It's pretty much gone now together with other tools associated with C (converting to C or from C). It only exists now as an archived ZIP on a pen drive. I'll give it a week to see what to do about that. It's a relief!
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-28 03:30 -0700 |
| Message-ID | <8fc28691-5b44-4498-a6d3-2acccc1c846bn@googlegroups.com> |
| In reply to | #172346 |
On Wednesday, August 16, 2023 at 9:31:54 AM UTC+8, Bart wrote: > > I may anyway, at any time, decide to just delete the lot. I just don't > > want any external pressures or responsibilities. > It's pretty much gone now together with other tools associated with C > (converting to C or from C). It only exists now as an archived ZIP on a > pen drive. I'll give it a week to see what to do about that. > > It's a relief! Ok, you don't intend to challenge the legal status of the code already released though, do you? I ask because someone asked me "are you sure it's public domain?" and I wasn't sure how to answer that. Below is what it says - no sign of an author, but that's not really a problem - I have other code included in PDOS where the author wishes to remain anonymous (even though I know his name) for some reason (which I've never asked). I can ask him why he has a specific concern about this code, but I think I already know the answer - he looked where bcc came from and noted that it wasn't public domain, and had a known author. So people may ask more questions - well - one person already has. Anything you can say to help me address his concerns (before we start using this in full knowledge that it is unsupported and not expected to be maintainable)? Thanks. Paul. Toy C compiler for Windows. This code is placed in the Public Domain. Generated C code (not original non-C sources); build with gcc or tcc. -------------------------------------- 'BCC' Compiler for 'C'-like language.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-28 11:43 +0100 |
| Message-ID | <uchtp4$1lh0a$1@dont-email.me> |
| In reply to | #172966 |
On 28/08/2023 11:30, Paul Edwards wrote: > On Wednesday, August 16, 2023 at 9:31:54 AM UTC+8, Bart wrote: > >>> I may anyway, at any time, decide to just delete the lot. I just don't >>> want any external pressures or responsibilities. > >> It's pretty much gone now together with other tools associated with C >> (converting to C or from C). It only exists now as an archived ZIP on a >> pen drive. I'll give it a week to see what to do about that. >> >> It's a relief! > > Ok, you don't intend to challenge the legal status of the code > already released though, do you? > > I ask because someone asked me "are you sure it's public > domain?" and I wasn't sure how to answer that. > > Below is what it says - no sign of an author, but that's not > really a problem - I have other code included in PDOS > where the author wishes to remain anonymous (even > though I know his name) for some reason (which I've > never asked). > > I can ask him why he has a specific concern about this > code, but I think I already know the answer - he looked > where bcc came from and noted that it wasn't public > domain, and had a known author. Was that the Borland C Compiler? If so that's nothing to do with me. The file you have remains as public domain. You can add the name 'Bart' or 'Bart C', but I don't want to divulge my surname as it will likely be unique worldwide. > So people may ask > more questions - well - one person already has. > > Anything you can say to help me address his concerns > (before we start using this in full knowledge that it is > unsupported and not expected to be maintainable)? > > Thanks. Paul. > > > > Toy C compiler for Windows. > > This code is placed in the Public Domain. > > Generated C code (not original non-C sources); build with gcc or tcc. > > -------------------------------------- > > 'BCC' Compiler for 'C'-like language. >
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-28 03:47 -0700 |
| Message-ID | <08adb571-05de-4824-9e56-c744d5253576n@googlegroups.com> |
| In reply to | #172978 |
On Monday, August 28, 2023 at 6:44:03 PM UTC+8, Bart wrote: > > I can ask him why he has a specific concern about this > > code, but I think I already know the answer - he looked > > where bcc came from and noted that it wasn't public > > domain, and had a known author. > Was that the Borland C Compiler? > > If so that's nothing to do with me. > > The file you have remains as public domain. > > You can add the name 'Bart' or 'Bart C', but I don't want to divulge my > surname as it will likely be unique worldwide. Thankyou sir! BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-09-04 18:43 -0700 |
| Message-ID | <ud614v$1qed6$1@dont-email.me> |
| In reply to | #171993 |
On 8/10/2023 4:57 AM, Bart wrote: > On 10/08/2023 12:29, Paul Edwards wrote: > > Hi Bart. [...] Creating a compiler reminds of the following song: https://youtu.be/_jEP347F6_g
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-10 04:59 -0700 |
| Message-ID | <d552d855-f560-4d31-ad26-cc4ed52fc99en@googlegroups.com> |
| In reply to | #171992 |
On Thursday, August 10, 2023 at 7:29:52 PM UTC+8, Paul Edwards wrote: > So now there is a purely public domain distribution > called "University Challenge x64" available at http://pdos.org Oh - and the source code is distributed as part of the "University Challenge 386" distribution. I'll probably duplicate that later, but it's still mainly "proof of concept". BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Date | 2023-08-28 17:45 +0300 |
| Message-ID | <20230828174502.a279eb2b4ea06fac68dc6561@g{oogle}mail.com> |
| In reply to | #171992 |
Paul Edwards: > The only thing missing in the toolchain is a viable C > compile Have you checked `lice': https://github.com/public-domain/lice -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-28 19:19 -0700 |
| Message-ID | <e3051618-59e9-453f-a72b-14155a1c46f4n@googlegroups.com> |
| In reply to | #173004 |
On Monday, August 28, 2023 at 10:45:17 PM UTC+8, Anton Shepelev wrote: > Paul Edwards: > > The only thing missing in the toolchain is a viable C > > compile > Have you checked `lice': > https://github.com/public-domain/lice Jean-Marc emailed me in 2020 and said: I found LICE ( https://github.com/public-domain/lice ) but I've not worked on it (I can't find the name of the original author, this is a issue). If he's leery, I'm leery too. BTW, this is the same guy who was leery about cc64 from Bart, so I went back to him with this thread and asked him if that was good enough, and he said he was happy with that, so I have now incorporated cc64 into the PDOS source tree: https://sourceforge.net/p/pdos/gitcode/ci/master/tree/cc64/ And the results have been fantastic. It accepted most of PDPCLIB, and I was happy to change some minor things that it needed. I encountered one presumed bug, and worked around that. I have since encountered another presumed bug when building PDOS-generic, and worked around that too. And I am able to build both Windows and EFI executables, so the stack must be aligned on a 16-byte boundary, which was a major concern (the most major concern was whether it would accept the C90 syntax I actually use). I am expecting to prioritize work on UCX64 at http://pdos.org with this new tool, which gives close enough to full closure. Thanks Bart! BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-29 22:01 +0100 |
| Message-ID | <uclmau$2d8p3$1@dont-email.me> |
| In reply to | #173134 |
On 29/08/2023 03:19, Paul Edwards wrote: > On Monday, August 28, 2023 at 10:45:17 PM UTC+8, Anton Shepelev wrote: >> Paul Edwards: >>> The only thing missing in the toolchain is a viable C >>> compile > >> Have you checked `lice': >> https://github.com/public-domain/lice > > Jean-Marc emailed me in 2020 and said: > > I found LICE ( https://github.com/public-domain/lice ) but I've not > worked on it (I can't find the name of the original author, this is a > issue). > > > If he's leery, I'm leery too. > > BTW, this is the same guy who was leery about cc64 from Bart, > so I went back to him with this thread and asked him if that was > good enough, and he said he was happy with that, so I have now > incorporated cc64 into the PDOS source tree: > > https://sourceforge.net/p/pdos/gitcode/ci/master/tree/cc64/ > > And the results have been fantastic. It accepted most of > PDPCLIB, and I was happy to change some minor things > that it needed. > > I encountered one presumed bug, and worked around that. > > I have since encountered another presumed bug when > building PDOS-generic, and worked around that too. You can try raising issues here: https://github.com/sal55/langs/tree/master I just need to notice that something has been posted, as I don't check it often.
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-29 20:00 -0700 |
| Message-ID | <a2f70a58-6b6e-41fd-864a-bcf947bdfdedn@googlegroups.com> |
| In reply to | #173230 |
On Wednesday, August 30, 2023 at 5:01:32 AM UTC+8, Bart wrote:
> > I encountered one presumed bug, and worked around that.
> >
> > I have since encountered another presumed bug when
> > building PDOS-generic, and worked around that too.
> You can try raising issues here:
>
> https://github.com/sal55/langs/tree/master
>
> I just need to notice that something has been posted, as I don't check
> it often.
Sorry - I thought you were very clear that this is unsupported
software and you don't want the headache? I checked the
link and it clearly says that bcc is archived.
Here are the workarounds I needed:
__PDPCLIB_HEADFUNC FILE **__gtin(void);
#define __stdin (*(__gtin()))
#ifdef __CC64__
*__stdin->fbuf = '\0';
__stdin->fbuf++;
*__stdin->fbuf = '\0';
__stdin->fbuf++;
#else
*__stdin->fbuf++ = '\0';
*__stdin->fbuf++ = '\0';
#endif
static int (*genstart)(OS *bios);
#ifdef __CC64__
rc = (*genstart)(&bios);
#else
rc = genstart(&bios);
#endif
Regardless, things are looking REALLY good and this is
likely to change my direction in life (as a Win64 vendor
on modern machines instead of scouring landfill for
Compaq BIOSes).
BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-30 00:25 -0700 |
| Message-ID | <cc26e867-f5fe-4780-812c-e26b88ee77e1n@googlegroups.com> |
| In reply to | #173243 |
One more issue has just come up: From the author of pdld analyzing a problem I sent him: The kernel32.obj produced by cc64 is lacking .drectve section which tells the linker which symbols should be exported. We're still seeing if we can work around this problem. BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-30 01:35 -0700 |
| Message-ID | <963d9c5c-a20a-40dc-8550-8f59a1b283f3n@googlegroups.com> |
| In reply to | #173249 |
On Wednesday, August 30, 2023 at 3:25:27 PM UTC+8, Paul Edwards wrote: > We're still seeing if we can work around this problem. An "export-all-symbols" option was added to pdld and that seems to be sufficient for my immediate needs. BFN. Paul.
[toc] | [prev] | [next] | [standalone]
| From | Bart <bc@freeuk.com> |
|---|---|
| Date | 2023-08-30 11:38 +0100 |
| Message-ID | <ucn66n$2n166$1@dont-email.me> |
| In reply to | #173243 |
On 30/08/2023 04:00, Paul Edwards wrote:
> On Wednesday, August 30, 2023 at 5:01:32 AM UTC+8, Bart wrote:
>>> I encountered one presumed bug, and worked around that.
>>>
>>> I have since encountered another presumed bug when
>>> building PDOS-generic, and worked around that too.
>
>> You can try raising issues here:
>>
>> https://github.com/sal55/langs/tree/master
>>
>> I just need to notice that something has been posted, as I don't check
>> it often.
>
> Sorry - I thought you were very clear that this is unsupported
> software and you don't want the headache? I checked the
> link and it clearly says that bcc is archived.
I can't guarantee anything, but sometimes I will try and fix something I
find irksome, just for my own satisfaction.
(The bcc project is a major test program for my own language.)
> Here are the workarounds I needed:
>
> __PDPCLIB_HEADFUNC FILE **__gtin(void);
>
> #define __stdin (*(__gtin()))
>
> #ifdef __CC64__
> *__stdin->fbuf = '\0';
> __stdin->fbuf++;
> *__stdin->fbuf = '\0';
> __stdin->fbuf++;
> #else
> *__stdin->fbuf++ = '\0';
> *__stdin->fbuf++ = '\0';
> #endif
>
>
>
> static int (*genstart)(OS *bios);
>
> #ifdef __CC64__
> rc = (*genstart)(&bios);
> #else
> rc = genstart(&bios);
> #endif
The latter bug (needing to call a function pointer F as (*F)() rather
than F()), I know about. The increment one is new. However, I can't
reproduce it. This program:
-----------------------------
#include <stdio.h>
//typedef char T;
typedef short T;
//typedef int T;
typedef struct {
int dummy;
T* fbuf;
} rec;
int main(void) {
T a[] = {10,20,30,40,50};
rec x = {999, NULL};
rec* p = &x;
x.fbuf = &a[2];
printf("*p->fbuf = %d\n", *p->fbuf);
*p->fbuf++ = 77; // From your example
for (int i=0; i<5; ++i) {
printf("%d: %d\n",i, a[i]);
}
printf("*p->fbuf = %d\n", *p->fbuf);
}
-----------------------------
gives the same results with both bcc and gcc, whatever T is chosen. What
is the actual type of fbuf? And at what offset is it within __stdin? I
tried with and without that dummy field.
In any case, the code you've had to use for CC64 should work with other
compilers too.
[toc] | [prev] | [next] | [standalone]
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Date | 2023-08-30 07:06 -0700 |
| Message-ID | <d500e1f2-7486-4425-a7e2-4472cce70e44n@googlegroups.com> |
| In reply to | #173265 |
Hi Bart.
I have encountered the below problem.
mingw64 works, but cc64 crashes on the fprintf.
Any idea? I will answer your other post now.
Thanks. Paul.
C:\devel\pdos\pdpclib>temp2
C:\devel\pdos\pdpclib>x86_64-w64-mingw32-gcc -S -O2 -D__WIN32__ -D__64BIT__ -I . -I ../src -o pdptest.s pdptest.c
C:\devel\pdos\pdpclib>pdas --oformat coff --64 -o pdptest.obj pdptest.s
C:\devel\pdos\pdpclib>rm -f pdptest.s
C:\devel\pdos\pdpclib>pdld -s -nostdlib --no-insert-timestamp -o pdptest.exe w32start.obj pdptest.obj msvcrt.lib
C:\devel\pdos\pdpclib>pdptest
xhello 5
yhello, world
C:\devel\pdos\pdpclib>temp
C:\devel\pdos\pdpclib>cc64 -c -out:pdptest.obj pdptest.c
Compiling pdptest.c to pdptest.obj
C:\devel\pdos\pdpclib>pdld -s -nostdlib --no-insert-timestamp --image-base 0x400000 -o pdptest.exe w32start.obj pdptest.obj msvcrt.lib
C:\devel\pdos\pdpclib>pdptest
xhello 5
C:\devel\pdos\pdpclib>type pdptest.c
int fprintf(void *stream, const char *format, ...);
int printf(const char *format, ...);
extern char *__imp__iob;
int main(void)
{
printf("xhello %d\n", 5);
fprintf(__imp__iob + 48, "yhello, world\n");
return (0);
}
C:\devel\pdos\pdpclib>
[toc] | [prev] | [next] | [standalone]
Page 1 of 18 [1] 2 3 … 18 Next page →
Back to top | Article view | comp.lang.c
csiph-web