Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #80902 > unrolled thread
| Started by | "Alf P. Steinbach" <alf.p.steinbach@gmail.com> |
|---|---|
| First post | 2021-08-29 20:57 +0200 |
| Last post | 2021-09-01 16:32 -0400 |
| Articles | 20 on this page of 301 — 30 participants |
Back to article view | Back to comp.lang.c++
Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-08-29 20:57 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Lynn McGuire <lynnmcguire5@gmail.com> - 2021-08-30 21:59 -0500
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2021-08-30 21:53 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2021-08-30 21:59 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-08-31 09:01 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-08-31 03:00 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Lynn McGuire <lynnmcguire5@gmail.com> - 2021-08-31 23:46 -0500
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 08:19 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 15:32 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 19:20 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 19:44 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Lynn McGuire <lynnmcguire5@gmail.com> - 2021-09-01 13:17 -0500
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 20:32 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 19:00 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Lynn McGuire <lynnmcguire5@gmail.com> - 2021-09-01 15:06 -0500
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 20:14 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 20:37 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-08-31 10:08 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-08-31 14:54 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-08-31 15:00 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Lynn McGuire <lynnmcguire5@gmail.com> - 2021-09-01 12:49 -0500
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Siri Cruise <chine.bleu@yahoo.com> - 2021-08-30 21:23 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-08-30 23:29 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 12:27 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Richard Damon <Richard@Damon-Family.org> - 2021-08-31 07:37 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 14:14 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2021-08-31 07:06 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 17:20 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-08-31 15:36 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 17:44 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2021-08-31 09:12 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 18:20 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-08-31 16:40 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 19:04 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Vir Campestris <vir.campestris@invalid.invalid> - 2021-08-31 21:37 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 07:25 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 09:26 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 10:14 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 11:07 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-01 10:31 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 20:27 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 15:22 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? red floyd <no.spam.here@its.invalid> - 2021-09-01 07:52 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 15:21 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? red floyd <no.spam.here@its.invalid> - 2021-09-01 09:41 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-01 18:11 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 18:04 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-01 18:27 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 19:02 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-01 21:36 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-02 06:58 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-02 11:34 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-09-02 14:51 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-02 23:31 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-03 11:12 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-03 15:35 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-03 16:46 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-03 22:01 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-03 20:45 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-04 01:06 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-04 02:12 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-04 09:12 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Manfred <noname@add.invalid> - 2021-09-04 18:05 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-06 08:43 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-09-06 08:59 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-06 10:12 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-06 11:27 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-06 12:48 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-04 15:28 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-04 17:44 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Ian Collins <ian-news@hotmail.com> - 2021-09-05 11:24 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Ian Collins <ian-news@hotmail.com> - 2021-09-04 10:14 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-04 09:36 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-04 17:00 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-06 11:03 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-06 09:11 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-06 13:08 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-06 15:26 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Manfred <noname@add.invalid> - 2021-09-07 15:05 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-07 15:07 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-07 19:41 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-08 09:38 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-08 10:29 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-09 10:58 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-09 08:55 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-09 12:15 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-09 09:19 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-09 14:41 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-09 22:19 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-09 16:09 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-09 12:41 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-08 10:24 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-08 20:22 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-09 08:54 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-09 14:47 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-09 16:13 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-09 12:42 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-10 09:37 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 13:27 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-10 05:41 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 15:31 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-10 16:45 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-10 07:21 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-11 11:20 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-10 14:50 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-10 14:56 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 17:38 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-10 15:47 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-11 18:40 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 09:23 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-12 12:57 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 16:22 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 12:49 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 16:13 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 18:45 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-13 10:55 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-13 14:15 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-13 15:32 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-13 12:07 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-13 22:18 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-12 09:48 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-13 10:52 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-12 23:12 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > Vir Campestris <vir.campestris@invalid.invalid> - 2021-09-13 22:00 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-14 09:24 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-13 21:42 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-14 10:15 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-14 09:12 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-14 15:01 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-14 17:07 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Vir Campestris <vir.campestris@invalid.invalid> - 2021-09-14 21:42 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-10 16:13 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 17:45 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-10 12:23 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-10 17:09 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-10 14:17 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-11 09:06 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-09 12:41 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-09 22:17 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-10 09:39 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 13:29 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-12 08:56 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 09:18 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-12 09:21 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 09:29 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 12:55 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-12 16:14 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-12 23:13 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-13 05:23 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > HorseyWorsey@the_stables.com - 2021-09-13 10:56 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-13 14:55 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Manfred <noname@add.invalid> - 2021-09-12 01:09 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-12 01:29 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 11:46 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-12 04:42 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 13:54 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-12 06:01 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-09-12 15:22 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 18:53 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-12 11:29 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-13 08:38 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-09-12 17:38 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > Manfred <noname@add.invalid> - 2021-09-13 03:52 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-09-12 19:10 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 11:32 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-09 18:37 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-07 17:56 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > MisterMule@stubborn.uk - 2021-09-08 10:28 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-08 13:31 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-09 11:06 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-09 01:27 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-09 13:05 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-09 10:29 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-09 22:28 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-09 12:40 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-10 09:51 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-10 00:07 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-10 11:26 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 10:02 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-10 09:10 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-10 11:32 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-12 09:00 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-12 11:29 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-10 13:47 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-11 11:02 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-11 00:33 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-11 11:42 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Manfred <noname@add.invalid> - 2021-09-15 19:20 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-11 19:15 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-11 20:56 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-12 12:11 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 11:53 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-12 11:17 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-13 12:51 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-13 11:03 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-14 12:05 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-14 10:28 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-15 08:17 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-12 09:10 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Ian Collins <ian-news@hotmail.com> - 2021-09-12 21:51 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > Chris Vine <chris@cvine--nospam--.freeserve.co.uk> - 2021-09-12 15:55 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > Vir Campestris <vir.campestris@invalid.invalid> - 2021-09-12 21:18 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-13 08:48 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > scott@slp53.sl.home (Scott Lurndal) - 2021-09-13 15:09 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > Juha Nieminen <nospam@thanks.invalid> - 2021-09-13 05:28 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-13 09:23 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > David Brown <david.brown@hesbynett.no> - 2021-09-12 12:21 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > Michael S <already5chosen@yahoo.com> - 2021-09-10 05:29 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > Bart <bc@freeuk.com> - 2021-09-10 12:20 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > "daniel...@gmail.com" <danielaparker@gmail.com> - 2021-09-06 11:51 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-03 05:13 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-03 11:30 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-03 11:19 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-03 13:33 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-03 15:44 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-03 17:40 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-03 17:58 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-03 22:23 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-04 12:20 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-06 05:42 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-03 08:49 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-03 17:42 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-05 04:29 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Michael S <already5chosen@yahoo.com> - 2021-09-05 05:11 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-06 05:45 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-06 03:38 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-06 12:00 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-06 16:38 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-06 15:52 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-07 04:39 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-07 07:23 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-07 07:31 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Ian Collins <ian-news@hotmail.com> - 2021-09-07 21:47 +1200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-08 10:18 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-08 11:32 -0400
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-08 05:02 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-08 13:44 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-08 07:41 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-08 16:44 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "daniel...@gmail.com" <danielaparker@gmail.com> - 2021-09-08 09:04 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-08 20:16 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-08 17:27 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-08 20:23 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-08 22:38 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-09 08:11 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Öö Tiib <ootiib@hot.ee> - 2021-09-09 09:25 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-09 18:43 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-09-06 05:37 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "daniel...@gmail.com" <danielaparker@gmail.com> - 2021-09-06 11:54 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-10-06 13:01 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 23:41 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-01 23:32 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-02 12:31 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bart <bc@freeuk.com> - 2021-09-02 11:11 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Paavo Helde <myfirstname@osa.pri.ee> - 2021-09-02 16:04 +0300
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? RantingRover <noemail@4u.com> - 2021-09-02 13:14 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Vir Campestris <vir.campestris@invalid.invalid> - 2021-09-01 21:43 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-01 04:40 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-08-31 15:02 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "see.my....@gmail.com" <see.my.homepage@gmail.com> - 2021-08-31 10:26 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-08-31 19:46 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-01 04:42 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 07:26 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-01 07:41 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 08:03 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-01 08:34 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 08:43 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Christian Gollwitzer <auriocus@gmx.de> - 2021-09-01 08:55 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 10:05 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Vir Campestris <vir.campestris@invalid.invalid> - 2021-09-01 21:34 +0100
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 10:10 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 10:37 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 10:44 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 10:48 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 10:51 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 11:15 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 12:15 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2021-09-01 06:49 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 15:50 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "james...@alumni.caltech.edu" <jameskuyper@alumni.caltech.edu> - 2021-09-01 07:16 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 16:30 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 10:28 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 09:57 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 10:13 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 10:44 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 11:05 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 11:17 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 12:17 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 12:48 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 12:54 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-09-01 15:20 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? David Brown <david.brown@hesbynett.no> - 2021-09-01 11:11 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 12:19 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Juha Nieminen <nospam@thanks.invalid> - 2021-09-01 18:14 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 20:34 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bo Persson <bo@bo-persson.se> - 2021-09-01 21:55 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-09-01 16:30 -0700
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-02 05:30 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? scott@slp53.sl.home (Scott Lurndal) - 2021-09-01 19:03 +0000
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? Bonita Montero <Bonita.Montero@gmail.com> - 2021-09-01 21:12 +0200
Re: Examples of current platforms/architectures where sizeof(void*) > sizeof(int*) ? James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-09-01 16:32 -0400
Page 8 of 16 — ← Prev page 1 … 6 7 [8] 9 10 … 16 Next page →
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2021-09-10 13:29 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shffhv$e91$2@dont-email.me> |
| In reply to | #81135 |
On 10/09/2021 11:39, HorseyWorsey@the_stables.com wrote:
> On Thu, 9 Sep 2021 22:17:59 +0200
> David Brown <david.brown@hesbynett.no> wrote:
>> On 09/09/2021 18:41, James Kuyper wrote:
>> So, for example, if you have these files:
>>
>> a.h
>> ---
>> #include "b.h"
>>
>> b.h
>> ---
>> #define TEST 1
>>
>> c.c
>> ---
>> #include "a.h"
>> #include <stdio.h>
>>
>> int main(void) {
>> printf("Test is %d\n", TEST);
>> }
>>
>>
>> Then "gcc -MD c.c" makes a file
>>
>> c.d
>> ---
>> c.o: c.c /usr/include/stdc-predef.h a.h b.h /usr/include/stdio.h \
>> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h \
>> /usr/include/features.h /usr/include/x86_64-linux-gnu/sys/cdefs.h \
>> /usr/include/x86_64-linux-gnu/bits/wordsize.h \
>> ...
>>
>>
>> Using "gcc -MMD c.c" is more helpful, usually, because it skips the
>> system includes:
>>
>> c.d
>> ---
>> c.o: c.c a.h b.h
>>
>>
>> But the real trick is "gcc -MMD -MT 'c.d c.o' c.c" :
>>
>> c.d
>> ---
>> c.d c.o: c.c a.h b.h
>
> Very nice. Now you have a single globals.h type file (VERY common in large
> projects). How does gcc figure out which C files it needs to build from that?
See my other reply that I hope will clear up your misunderstandings.
>>
>>
>> Now "make" knows that the dependency file is also dependent on the C
>> file and headers.
>
>
[toc] | [prev] | [next] | [standalone]
| From | Juha Nieminen <nospam@thanks.invalid> |
|---|---|
| Date | 2021-09-12 08:56 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkfc8$1lpj$1@gioia.aioe.org> |
| In reply to | #81135 |
HorseyWorsey@the_stables.com wrote: > Very nice. Now you have a single globals.h type file (VERY common in large > projects). How does gcc figure out which C files it needs to build from that? It doesn't. It only compiles what you tell it to compile. It has to be *something else* that runs it and tells it what to compile. Often this is the 'make' program (which is reading a file usually named 'Makefile').
[toc] | [prev] | [next] | [standalone]
| From | HorseyWorsey@the_stables.com |
|---|---|
| Date | 2021-09-12 09:18 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkgkt$9rf$1@gioia.aioe.org> |
| In reply to | #81190 |
On Sun, 12 Sep 2021 08:56:42 -0000 (UTC) Juha Nieminen <nospam@thanks.invalid> wrote: >HorseyWorsey@the_stables.com wrote: >> Very nice. Now you have a single globals.h type file (VERY common in large >> projects). How does gcc figure out which C files it needs to build from that? > > >It doesn't. It only compiles what you tell it to compile. > >It has to be *something else* that runs it and tells it what to >compile. Often this is the 'make' program (which is reading a >file usually named 'Makefile'). Well thanks for that valuable input, we're all so much more informed now.
[toc] | [prev] | [next] | [standalone]
| From | Juha Nieminen <nospam@thanks.invalid> |
|---|---|
| Date | 2021-09-12 09:21 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkgrc$3cc$3@gioia.aioe.org> |
| In reply to | #81193 |
HorseyWorsey@the_stables.com wrote: > On Sun, 12 Sep 2021 08:56:42 -0000 (UTC) > Juha Nieminen <nospam@thanks.invalid> wrote: >>HorseyWorsey@the_stables.com wrote: >>> Very nice. Now you have a single globals.h type file (VERY common in large >>> projects). How does gcc figure out which C files it needs to build from that? >> >> >>It doesn't. It only compiles what you tell it to compile. >> >>It has to be *something else* that runs it and tells it what to >>compile. Often this is the 'make' program (which is reading a >>file usually named 'Makefile'). > > Well thanks for that valuable input, we're all so much more informed now. You made that sound sarcastic. If it is indeed sarcasm, I don't really understand why.
[toc] | [prev] | [next] | [standalone]
| From | HorseyWorsey@the_stables.com |
|---|---|
| Date | 2021-09-12 09:29 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkh9c$i5o$1@gioia.aioe.org> |
| In reply to | #81195 |
On Sun, 12 Sep 2021 09:21:50 -0000 (UTC) Juha Nieminen <nospam@thanks.invalid> wrote: >HorseyWorsey@the_stables.com wrote: >> On Sun, 12 Sep 2021 08:56:42 -0000 (UTC) >> Juha Nieminen <nospam@thanks.invalid> wrote: >>>HorseyWorsey@the_stables.com wrote: >>>> Very nice. Now you have a single globals.h type file (VERY common in large > >>>> projects). How does gcc figure out which C files it needs to build from >that? >>> >>> >>>It doesn't. It only compiles what you tell it to compile. >>> >>>It has to be *something else* that runs it and tells it what to >>>compile. Often this is the 'make' program (which is reading a >>>file usually named 'Makefile'). >> >> Well thanks for that valuable input, we're all so much more informed now. > >You made that sound sarcastic. If it is indeed sarcasm, I don't >really understand why. Try following a thread before replying. A couple of posters were claiming the compiler could automate the entire build system and I gave some basic examples of why it couldn't. Now one of them is back peddaling and basically saying it can automate all the bits except the bits it can't when you need to edit the makefile yourself. Genius. Then you come along and mention Makefiles. Well thanks for the heads up, I'd forgotten what they were called. Yes, it was sarcasm.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2021-09-12 12:55 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkmap$eqd$1@dont-email.me> |
| In reply to | #81197 |
On 12/09/2021 11:29, HorseyWorsey@the_stables.com wrote: > On Sun, 12 Sep 2021 09:21:50 -0000 (UTC) > Juha Nieminen <nospam@thanks.invalid> wrote: >> HorseyWorsey@the_stables.com wrote: >>> On Sun, 12 Sep 2021 08:56:42 -0000 (UTC) >>> Juha Nieminen <nospam@thanks.invalid> wrote: >>>> HorseyWorsey@the_stables.com wrote: >>>>> Very nice. Now you have a single globals.h type file (VERY common in large >> >>>>> projects). How does gcc figure out which C files it needs to build from >> that? >>>> >>>> >>>> It doesn't. It only compiles what you tell it to compile. >>>> >>>> It has to be *something else* that runs it and tells it what to >>>> compile. Often this is the 'make' program (which is reading a >>>> file usually named 'Makefile'). >>> >>> Well thanks for that valuable input, we're all so much more informed now. >> >> You made that sound sarcastic. If it is indeed sarcasm, I don't >> really understand why. > > Try following a thread before replying. A couple of posters were claiming the > compiler could automate the entire build system and I gave some basic examples > of why it couldn't. Now one of them is back peddaling and basically saying it > can automate all the bits except the bits it can't when you need to edit the > makefile yourself. Genius. Then you come along and mention Makefiles. Well > thanks for the heads up, I'd forgotten what they were called. > Ah, so you are saying that /you/ have completely misunderstood the thread and what people wrote, and thought mocking would make you look clever. I guess you'll figure it out in the end, and we can look forward to another name change so you can pretend it wasn't you who got everything so wrong. > Yes, it was sarcasm. >
[toc] | [prev] | [next] | [standalone]
| From | HorseyWorsey@the_stables.com |
|---|---|
| Date | 2021-09-12 16:14 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shl91e$1ihm$1@gioia.aioe.org> |
| In reply to | #81210 |
On Sun, 12 Sep 2021 12:55:21 +0200 David Brown <david.brown@hesbynett.no> wrote: >On 12/09/2021 11:29, HorseyWorsey@the_stables.com wrote: >> On Sun, 12 Sep 2021 09:21:50 -0000 (UTC) >> Juha Nieminen <nospam@thanks.invalid> wrote: >>> HorseyWorsey@the_stables.com wrote: >>>> On Sun, 12 Sep 2021 08:56:42 -0000 (UTC) >>>> Juha Nieminen <nospam@thanks.invalid> wrote: >>>>> HorseyWorsey@the_stables.com wrote: >>>>>> Very nice. Now you have a single globals.h type file (VERY common in >large >>> >>>>>> projects). How does gcc figure out which C files it needs to build from >>> that? >>>>> >>>>> >>>>> It doesn't. It only compiles what you tell it to compile. >>>>> >>>>> It has to be *something else* that runs it and tells it what to >>>>> compile. Often this is the 'make' program (which is reading a >>>>> file usually named 'Makefile'). >>>> >>>> Well thanks for that valuable input, we're all so much more informed now. >>> >>> You made that sound sarcastic. If it is indeed sarcasm, I don't >>> really understand why. >> >> Try following a thread before replying. A couple of posters were claiming the > >> compiler could automate the entire build system and I gave some basic >examples >> of why it couldn't. Now one of them is back peddaling and basically saying it > >> can automate all the bits except the bits it can't when you need to edit the >> makefile yourself. Genius. Then you come along and mention Makefiles. Well >> thanks for the heads up, I'd forgotten what they were called. >> > >Ah, so you are saying that /you/ have completely misunderstood the >thread and what people wrote, and thought mocking would make you look >clever. Its nice to know you can spot mocking even if you can't following a simple thread.
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@alumni.caltech.edu> |
|---|---|
| Date | 2021-09-12 23:13 -0400 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shmfkk$74h$3@dont-email.me> |
| In reply to | #81197 |
On 9/12/21 5:29 AM, HorseyWorsey@the_stables.com wrote: ... > Try following a thread before replying. A couple of posters were claiming the > compiler could automate the entire build system I have been following the thread, and no one said anything of the kind. The claim that started this subthread was: On 9/8/21 1:22 PM, Paavo Helde wrote: > Such dependencies are taken care automatically by the gcc -MD option, > which you have to specify for both Makefile and CMake based builds Note that he only referred to "such dependencies", in context, that refers only to the dependencies that result from #include directives. He made no claim that all dependencies could be automated that way. Secondly, he quite clearly indicated that gcc -MD was to be used with Makefile or CMake based builds, he did not in any way suggest that it replaced the need for a build system.
[toc] | [prev] | [next] | [standalone]
| From | Juha Nieminen <nospam@thanks.invalid> |
|---|---|
| Date | 2021-09-13 05:23 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shmn82$mct$1@gioia.aioe.org> |
| In reply to | #81197 |
HorseyWorsey@the_stables.com wrote: > Yes, it was sarcasm. Well, good luck trying to get any more answers from me. I don't usually placate to assholes.
[toc] | [prev] | [next] | [standalone]
| From | HorseyWorsey@the_stables.com |
|---|---|
| Date | 2021-09-13 10:56 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shnapb$1qae$1@gioia.aioe.org> |
| In reply to | #81234 |
On Mon, 13 Sep 2021 05:23:16 -0000 (UTC) Juha Nieminen <nospam@thanks.invalid> wrote: >HorseyWorsey@the_stables.com wrote: >> Yes, it was sarcasm. > >Well, good luck trying to get any more answers from me. I don't usually >placate to assholes. I'm not interested what you do with your donkey or its hole.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2021-09-13 14:55 +0000 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <uDJ%I.15474$4X4.7373@fx27.iad> |
| In reply to | #81234 |
Juha Nieminen <nospam@thanks.invalid> writes: >HorseyWorsey@the_stables.com wrote: >> Yes, it was sarcasm. > >Well, good luck trying to get any more answers from me. I don't usually >placate to assholes. Come now, its nom-de-post is sufficient to make one wary of its goals.
[toc] | [prev] | [next] | [standalone]
| From | Manfred <noname@add.invalid> |
|---|---|
| Date | 2021-09-12 01:09 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shjcuk$s9j$1@gioia.aioe.org> |
| In reply to | #81128 |
On 9/9/2021 10:17 PM, David Brown wrote:
> On 09/09/2021 18:41, James Kuyper wrote:
>> On 9/9/21 4:54 AM, MisterMule@stubborn.uk wrote:
>>> On Wed, 8 Sep 2021 20:22:52 +0300
>>> Paavo Helde <myfirstname@osa.pri.ee> wrote:
>>>> 08.09.2021 13:24 MisterMule@stubborn.uk kirjutas:
>>>>>
>>>>> You can write a makefile just as simple. However what happens when you
>>>>> want foo.c recompiled when foo.h and bar.h changes but bar.c should only
>>>>> be recompiled when bar.h and moo.h change, moo.c should only be recompiled
>>>> when
>>>>> moo.h changes and main.c should be recompiled when anything changes?
>>>>>
>>>>
>>>> Such dependencies are taken care automatically by the gcc -MD option,
>>>
>>> No unless the compiler is clairvoyant they arn't.
>>
>> That option causes a dependencies file to be created specifying all the
>> dependencies that the compiler notices during compilation. That file can
>> then be used to avoid unnecessary re-builds the next time the same file
>> is compiled. The dependency file is therefore always one build
>> out-of-date; if you created any new dependencies, or removed any old
>> ones, the dependencies file will be incorrect until after the next time
>> you do a build. It's therefore not a perfect solution - but neither is
>> it useless.
>>
>
> The trick is to have makefile (or whatever build system you use) rules
> along with gcc so that the dependency file not only labels the object
> file as dependent on the C or C++ file and all the include files it
> uses, recursively, but also labels the dependency file itself to be
> dependent on the same files. Then if the source file or includes are
> changed, the dependency file is re-created, and make is smart enough to
> then reload that dependency file to get the new dependencies for
> building the object file.
>
> The makefile rules involved are close to APL in readability, but once
> you have figured out what you need, you can re-use it for any other
> project. And it solves the problem you have here.
>
>
> So, for example, if you have these files:
>
> a.h
> ---
> #include "b.h"
>
> b.h
> ---
> #define TEST 1
>
> c.c
> ---
> #include "a.h"
> #include <stdio.h>
>
> int main(void) {
> printf("Test is %d\n", TEST);
> }
>
>
> Then "gcc -MD c.c" makes a file
>
> c.d
> ---
> c.o: c.c /usr/include/stdc-predef.h a.h b.h /usr/include/stdio.h \
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h \
> /usr/include/features.h /usr/include/x86_64-linux-gnu/sys/cdefs.h \
> /usr/include/x86_64-linux-gnu/bits/wordsize.h \
> ...
>
>
> Using "gcc -MMD c.c" is more helpful, usually, because it skips the
> system includes:
>
> c.d
> ---
> c.o: c.c a.h b.h
>
>
> But the real trick is "gcc -MMD -MT 'c.d c.o' c.c" :
>
> c.d
> ---
> c.d c.o: c.c a.h b.h
>
>
> Now "make" knows that the dependency file is also dependent on the C
> file and headers.
>
What you are describing is substantially:
https://www.gnu.org/software/make/manual/html_node/Automatic-Prerequisites.html
with the addition of the -MT gcc option, which removes the need for the
nasty 'sed' command in the "%.d: %.c" rule - which is the kind of thing
that tends to keep people away.
Thanks for pointing this out.
I guess in that rule one can use the single command:
%.d: %.c
$(CC) $(CPPFLAGS) -MM -MT '$*.o $@' -MF $@ $<
(As a side note, it wouldn't hurt if the GCC people updated their docs
from time to time...)
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2021-09-12 01:29 -0700 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <f62679e2-ce8a-4ed5-bbba-4fd791860135n@googlegroups.com> |
| In reply to | #81186 |
On Sunday, September 12, 2021 at 2:09:30 AM UTC+3, Manfred wrote:
> On 9/9/2021 10:17 PM, David Brown wrote:
> > On 09/09/2021 18:41, James Kuyper wrote:
> >> On 9/9/21 4:54 AM, Miste...@stubborn.uk wrote:
> >>> On Wed, 8 Sep 2021 20:22:52 +0300
> >>> Paavo Helde <myfir...@osa.pri.ee> wrote:
> >>>> 08.09.2021 13:24 Miste...@stubborn.uk kirjutas:
> >>>>>
> >>>>> You can write a makefile just as simple. However what happens when you
> >>>>> want foo.c recompiled when foo.h and bar.h changes but bar.c should only
> >>>>> be recompiled when bar.h and moo.h change, moo.c should only be recompiled
> >>>> when
> >>>>> moo.h changes and main.c should be recompiled when anything changes?
> >>>>>
> >>>>
> >>>> Such dependencies are taken care automatically by the gcc -MD option,
> >>>
> >>> No unless the compiler is clairvoyant they arn't.
> >>
> >> That option causes a dependencies file to be created specifying all the
> >> dependencies that the compiler notices during compilation. That file can
> >> then be used to avoid unnecessary re-builds the next time the same file
> >> is compiled. The dependency file is therefore always one build
> >> out-of-date; if you created any new dependencies, or removed any old
> >> ones, the dependencies file will be incorrect until after the next time
> >> you do a build. It's therefore not a perfect solution - but neither is
> >> it useless.
> >>
> >
> > The trick is to have makefile (or whatever build system you use) rules
> > along with gcc so that the dependency file not only labels the object
> > file as dependent on the C or C++ file and all the include files it
> > uses, recursively, but also labels the dependency file itself to be
> > dependent on the same files. Then if the source file or includes are
> > changed, the dependency file is re-created, and make is smart enough to
> > then reload that dependency file to get the new dependencies for
> > building the object file.
> >
> > The makefile rules involved are close to APL in readability, but once
> > you have figured out what you need, you can re-use it for any other
> > project. And it solves the problem you have here.
> >
> >
> > So, for example, if you have these files:
> >
> > a.h
> > ---
> > #include "b.h"
> >
> > b.h
> > ---
> > #define TEST 1
> >
> > c.c
> > ---
> > #include "a.h"
> > #include <stdio.h>
> >
> > int main(void) {
> > printf("Test is %d\n", TEST);
> > }
> >
> >
> > Then "gcc -MD c.c" makes a file
> >
> > c.d
> > ---
> > c.o: c.c /usr/include/stdc-predef.h a.h b.h /usr/include/stdio.h \
> > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h \
> > /usr/include/features.h /usr/include/x86_64-linux-gnu/sys/cdefs.h \
> > /usr/include/x86_64-linux-gnu/bits/wordsize.h \
> > ...
> >
> >
> > Using "gcc -MMD c.c" is more helpful, usually, because it skips the
> > system includes:
> >
> > c.d
> > ---
> > c.o: c.c a.h b.h
> >
> >
> > But the real trick is "gcc -MMD -MT 'c.d c.o' c.c" :
> >
> > c.d
> > ---
> > c.d c.o: c.c a.h b.h
> >
> >
> > Now "make" knows that the dependency file is also dependent on the C
> > file and headers.
> >
> What you are describing is substantially:
>
> https://www.gnu.org/software/make/manual/html_node/Automatic-Prerequisites.html
>
> with the addition of the -MT gcc option, which removes the need for the
> nasty 'sed' command in the "%.d: %.c" rule - which is the kind of thing
> that tends to keep people away.
>
> Thanks for pointing this out.
>
> I guess in that rule one can use the single command:
> %.d: %.c
> $(CC) $(CPPFLAGS) -MM -MT '$*.o $@' -MF $@ $<
>
> (As a side note, it wouldn't hurt if the GCC people updated their docs
> from time to time...)
gcc maintainers have policy against updating/fixing docs.
From their perspective, compiler and docs are inseparable parts of holy "release".
I tried to change their mind about it few years ago, but didn't succeed.
So, if you are not satisfied with quality of gcc docs supplied with your release of gcc compiler then the best you can do is to look at the docs for the most recent "release". I.e. right now 11.2. Naturally, in order to be sure that these docs apply, you'd have to update the compiler itself too.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2021-09-12 11:46 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shki9g$kd5$1@dont-email.me> |
| In reply to | #81189 |
On 12/09/2021 10:29, Michael S wrote: > On Sunday, September 12, 2021 at 2:09:30 AM UTC+3, Manfred wrote: >> (As a side note, it wouldn't hurt if the GCC people updated their docs >> from time to time...) > Your reference here was to the "make" manual, rather than the gcc documentation. But the gcc folk could add an example like this to their manual for the "-MT" option. > > gcc maintainers have policy against updating/fixing docs. > From their perspective, compiler and docs are inseparable parts of holy "release". Well, yes. The gcc manual of a particular version documents the gcc of that version. It seems an excellent policy to me. It would be a little different if they were publishing a tutorial on using gcc. > I tried to change their mind about it few years ago, but didn't succeed. Thankfully. It would be rather messy if they only had one reference manual which was full of comments about which versions the particular options or features applied to, as these come and go over time. I suppose it would be possible to make some kind of interactive reference where you selected your choice of compiler version, target processor, etc., and the text adapted to suit. That could be a useful tool, and help people see exactly what applied to their exact toolchain. But it would take a good deal of work, and a rather different thing from the current manuals. > So, if you are not satisfied with quality of gcc docs supplied with > your release of gcc compiler then the best you can do is to look at the > docs for the most recent "release". I.e. right now 11.2. Naturally, in > order to be sure that these docs apply, you'd have to update the > compiler itself too. > I think most people /do/ look up the gcc documents online, rather than locally. The gcc website has many versions easily available, so you can read the manual for the version you are using. And while new features in later gcc versions add to the manuals, it's rare that there are changes to the text for existing features. The documentation for "-MT" is substantially the same for the latest development version of gcc 12 and for gcc 3.0 from about 20 years ago.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2021-09-12 04:42 -0700 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <49327438-156d-45a3-bb23-29ac8f844085n@googlegroups.com> |
| In reply to | #81200 |
On Sunday, September 12, 2021 at 12:46:42 PM UTC+3, David Brown wrote: > On 12/09/2021 10:29, Michael S wrote: > > On Sunday, September 12, 2021 at 2:09:30 AM UTC+3, Manfred wrote: > > >> (As a side note, it wouldn't hurt if the GCC people updated their docs > >> from time to time...) > > > Your reference here was to the "make" manual, rather than the gcc > documentation. But the gcc folk could add an example like this to their > manual for the "-MT" option. > > > > gcc maintainers have policy against updating/fixing docs. > > From their perspective, compiler and docs are inseparable parts of holy "release". > Well, yes. The gcc manual of a particular version documents the gcc of > that version. It seems an excellent policy to me. > > It would be a little different if they were publishing a tutorial on > using gcc. > > I tried to change their mind about it few years ago, but didn't succeed. > Thankfully. It would be rather messy if they only had one reference > manual which was full of comments about which versions the particular > options or features applied to, as these come and go over time. > That's not what I was suggesting. I was suggesting to add an clarifications and suggestions for a feature (it was something about function attribute 'optimize') that existed in gcc5 to online copy of respective manual hosted on gcc.gnu.org/onlinedocs Obviously, a previous version of the manual could have been available to historians among us in gcc source control database. Instead, said clarifications+suggestions were added to the *next* release of the manual. Oh, in fact, no, it didn't made it into gcc6 manual. It was added to gcc 7 manual. So, gcc5 users now have no way to know that changes in docs apply to gcc5 every bit as much as they apply to gcc7 and later. > I suppose it would be possible to make some kind of interactive > reference where you selected your choice of compiler version, target > processor, etc., and the text adapted to suit. That could be a useful > tool, and help people see exactly what applied to their exact toolchain. > But it would take a good deal of work, and a rather different thing > from the current manuals. > > So, if you are not satisfied with quality of gcc docs supplied with > > your release of gcc compiler then the best you can do is to look at the > > docs for the most recent "release". I.e. right now 11.2. Naturally, in > > order to be sure that these docs apply, you'd have to update the > > compiler itself too. > > > I think most people /do/ look up the gcc documents online, rather than > locally. I am pretty sure that it is a case. And that was exactly my argument *for* updating online copy of gcc5 docs. And the argument of maintainers was that people that read manuals locally do exist. > The gcc website has many versions easily available, so you can > read the manual for the version you are using. And while new features > in later gcc versions add to the manuals, it's rare that there are > changes to the text for existing features. In my specific case it was a change to the text of existing feature. > The documentation for "-MT" > is substantially the same for the latest development version of gcc 12 > and for gcc 3.0 from about 20 years ago.
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2021-09-12 13:54 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkpqj$4rm$1@dont-email.me> |
| In reply to | #81211 |
On 12/09/2021 13:42, Michael S wrote: > On Sunday, September 12, 2021 at 12:46:42 PM UTC+3, David Brown > wrote: >> On 12/09/2021 10:29, Michael S wrote: >>> On Sunday, September 12, 2021 at 2:09:30 AM UTC+3, Manfred wrote: >>> >> >>>> (As a side note, it wouldn't hurt if the GCC people updated >>>> their docs from time to time...) >>> >> Your reference here was to the "make" manual, rather than the gcc >> documentation. But the gcc folk could add an example like this to >> their manual for the "-MT" option. >>> >>> gcc maintainers have policy against updating/fixing docs. From >>> their perspective, compiler and docs are inseparable parts of >>> holy "release". >> Well, yes. The gcc manual of a particular version documents the gcc >> of that version. It seems an excellent policy to me. >> >> It would be a little different if they were publishing a tutorial >> on using gcc. >>> I tried to change their mind about it few years ago, but didn't >>> succeed. >> Thankfully. It would be rather messy if they only had one reference >> manual which was full of comments about which versions the >> particular options or features applied to, as these come and go >> over time. >> > > That's not what I was suggesting. I was suggesting to add an > clarifications and suggestions for a feature (it was something about > function attribute 'optimize') that existed in gcc5 to online copy of > respective manual hosted on gcc.gnu.org/onlinedocs Obviously, a > previous version of the manual could have been available to > historians among us in gcc source control database. > > Instead, said clarifications+suggestions were added to the *next* > release of the manual. Oh, in fact, no, it didn't made it into gcc6 > manual. It was added to gcc 7 manual. So, gcc5 users now have no way > to know that changes in docs apply to gcc5 every bit as much as they > apply to gcc7 and later. gcc 5 users /do/ have a way to see the change - they can look at later gcc references just as easily as older ones. Occasionally, changes to the manuals might be back-ported a couple of versions, just as changes to the compilers are back-ported if they are important enough (wrong code generation bugs). I'm sure the policies could be be better in some aspects - there are always going to be cases where new improvements to the manual would apply equally to older versions. But such flexibility comes at a cost - more work, and more risk of getting things wrong. > >> I suppose it would be possible to make some kind of interactive >> reference where you selected your choice of compiler version, >> target processor, etc., and the text adapted to suit. That could be >> a useful tool, and help people see exactly what applied to their >> exact toolchain. But it would take a good deal of work, and a >> rather different thing from the current manuals. >>> So, if you are not satisfied with quality of gcc docs supplied >>> with your release of gcc compiler then the best you can do is to >>> look at the docs for the most recent "release". I.e. right now >>> 11.2. Naturally, in order to be sure that these docs apply, you'd >>> have to update the compiler itself too. >>> >> I think most people /do/ look up the gcc documents online, rather >> than locally. > > I am pretty sure that it is a case. And that was exactly my argument > *for* updating online copy of gcc5 docs. And the argument of > maintainers was that people that read manuals locally do exist. > >> The gcc website has many versions easily available, so you can read >> the manual for the version you are using. And while new features in >> later gcc versions add to the manuals, it's rare that there are >> changes to the text for existing features. > > In my specific case it was a change to the text of existing feature. > I think it's fair to say there is scope for improvement in the way gcc documentation is handled, but it is still a good deal better than many compilers and other projects. >> The documentation for "-MT" is substantially the same for the >> latest development version of gcc 12 and for gcc 3.0 from about 20 >> years ago.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2021-09-12 06:01 -0700 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <89bdc4f2-03ca-40ec-a7a3-fb742a70242bn@googlegroups.com> |
| In reply to | #81212 |
On Sunday, September 12, 2021 at 2:55:15 PM UTC+3, David Brown wrote: > On 12/09/2021 13:42, Michael S wrote: > > On Sunday, September 12, 2021 at 12:46:42 PM UTC+3, David Brown > > wrote: > >> On 12/09/2021 10:29, Michael S wrote: > >>> On Sunday, September 12, 2021 at 2:09:30 AM UTC+3, Manfred wrote: > >>> > >> > >>>> (As a side note, it wouldn't hurt if the GCC people updated > >>>> their docs from time to time...) > >>> > >> Your reference here was to the "make" manual, rather than the gcc > >> documentation. But the gcc folk could add an example like this to > >> their manual for the "-MT" option. > >>> > >>> gcc maintainers have policy against updating/fixing docs. From > >>> their perspective, compiler and docs are inseparable parts of > >>> holy "release". > >> Well, yes. The gcc manual of a particular version documents the gcc > >> of that version. It seems an excellent policy to me. > >> > >> It would be a little different if they were publishing a tutorial > >> on using gcc. > >>> I tried to change their mind about it few years ago, but didn't > >>> succeed. > >> Thankfully. It would be rather messy if they only had one reference > >> manual which was full of comments about which versions the > >> particular options or features applied to, as these come and go > >> over time. > >> > > > > That's not what I was suggesting. I was suggesting to add an > > clarifications and suggestions for a feature (it was something about > > function attribute 'optimize') that existed in gcc5 to online copy of > > respective manual hosted on gcc.gnu.org/onlinedocs Obviously, a > > previous version of the manual could have been available to > > historians among us in gcc source control database. > > > > Instead, said clarifications+suggestions were added to the *next* > > release of the manual. Oh, in fact, no, it didn't made it into gcc6 > > manual. It was added to gcc 7 manual. So, gcc5 users now have no way > > to know that changes in docs apply to gcc5 every bit as much as they > > apply to gcc7 and later. > gcc 5 users /do/ have a way to see the change - they can look at later > gcc references just as easily as older ones. > They can see a change, but they can't be sure that it applies to they version of compiler. > Occasionally, changes to the manuals might be back-ported a couple of > versions, just as changes to the compilers are back-ported if they are > important enough (wrong code generation bugs). > As far as I understand, the policy is strict - even obviously wrong statements in the released manual can't be fixed. > I'm sure the policies could be be better in some aspects - there are > always going to be cases where new improvements to the manual would > apply equally to older versions. But such flexibility comes at a cost - > more work, and more risk of getting things wrong. > > > >> I suppose it would be possible to make some kind of interactive > >> reference where you selected your choice of compiler version, > >> target processor, etc., and the text adapted to suit. That could be > >> a useful tool, and help people see exactly what applied to their > >> exact toolchain. But it would take a good deal of work, and a > >> rather different thing from the current manuals. > >>> So, if you are not satisfied with quality of gcc docs supplied > >>> with your release of gcc compiler then the best you can do is to > >>> look at the docs for the most recent "release". I.e. right now > >>> 11.2. Naturally, in order to be sure that these docs apply, you'd > >>> have to update the compiler itself too. > >>> > >> I think most people /do/ look up the gcc documents online, rather > >> than locally. > > > > I am pretty sure that it is a case. And that was exactly my argument > > *for* updating online copy of gcc5 docs. And the argument of > > maintainers was that people that read manuals locally do exist. > > > >> The gcc website has many versions easily available, so you can read > >> the manual for the version you are using. And while new features in > >> later gcc versions add to the manuals, it's rare that there are > >> changes to the text for existing features. > > > > In my specific case it was a change to the text of existing feature. > > > I think it's fair to say there is scope for improvement in the way gcc > documentation is handled, but it is still a good deal better than many > compilers and other projects. Comparatively to public variant of llvm/clang docs - sure, but that's pretty low bar. I never looked at apple's and google's releases of clang docs, hopefully they are better than public release. Comparatively to Microsoft - it depends. Some parts of the gcc docs are better others are worse. However I would think that when Microsoft's maintainers see a mistake in their online docs for old compiler, or, more likely, are pointed to mistake by community, they fix it without hesitation. > >> The documentation for "-MT" is substantially the same for the > >> latest development version of gcc 12 and for gcc 3.0 from about 20 > >> years ago.
[toc] | [prev] | [next] | [standalone]
| From | "Alf P. Steinbach" <alf.p.steinbach@gmail.com> |
|---|---|
| Date | 2021-09-12 15:22 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shkuvi$7gp$1@dont-email.me> |
| In reply to | #81213 |
On 12 Sep 2021 15:01, Michael S wrote: > [snip] Comparatively to Microsoft - it depends. Some parts of the gcc > docs are better others are worse. However I would think that when > Microsoft's maintainers see a mistake in their online docs for old > compiler, or, more likely, are pointed to mistake by community, they > fix it without hesitation. Sometimes fastish, sometimes decades (!), sometimes never. As an example, `WinMain` was erroneously documented as the machine code entry point of a program, and the actual machine code entry point was undocumented, for decades. That has in turn caused other documentation errors. I don't know if it's been fixed. Apparently MS documentation fix delays depend on politics, as I see it politics of three kinds (this is my impression over ~20 years) : * Vendor lock-in measures. MS became infamous for this when certain internal e-mails became public during a court case fought against Sun. Well, maybe also earlier, for they were already infamous for the ¹“embrace, extend, extinguish” strategy to deal with common standards. * Internal sabotage. Different parts of Microsoft fight the others by subtle and not-so-subtle means. Including missing or misleading docs. * Unwillingness to admit sheer incompetence. - Alf Notes: ¹ https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2021-09-12 18:53 +0200 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <shlb9n$v9m$1@dont-email.me> |
| In reply to | #81213 |
On 12/09/2021 15:01, Michael S wrote: > On Sunday, September 12, 2021 at 2:55:15 PM UTC+3, David Brown >> I think it's fair to say there is scope for improvement in the way >> gcc documentation is handled, but it is still a good deal better >> than many compilers and other projects. > > Comparatively to public variant of llvm/clang docs - sure, but that's > pretty low bar. I never looked at apple's and google's releases of > clang docs, hopefully they are better than public release. > Comparatively to Microsoft - it depends. Some parts of the gcc docs > are better others are worse. However I would think that when > Microsoft's maintainers see a mistake in their online docs for old > compiler, or, more likely, are pointed to mistake by community, they > fix it without hesitation. > I have not nearly enough experience with the documentation of MS's compiler to tell - I have only ever looked up a few points. (The same with clang.) I've read manuals for many other compilers over the years, which are often much worse, but none of these tools are direct comparisons with gcc (being commercial embedded toolchains targetting one or a few specific microcontroller cores). One especially "fun" case was a toolchain that failed to zero-initialise non-local objects that were not explicitly initialised - what you normally get by startup code clearing the ".bss" segment. This "feature" was documented in a footnote in the middle of the manual, noting that the behaviour was not standards conforming and would silently break existing C code.
[toc] | [prev] | [next] | [standalone]
| From | Michael S <already5chosen@yahoo.com> |
|---|---|
| Date | 2021-09-12 11:29 -0700 |
| Subject | Re: Examples of current platforms/architectures where sizeof(void*) > |
| Message-ID | <9cb1e763-6e78-4fa1-8676-88d115771402n@googlegroups.com> |
| In reply to | #81224 |
On Sunday, September 12, 2021 at 7:53:29 PM UTC+3, David Brown wrote: > On 12/09/2021 15:01, Michael S wrote: > > On Sunday, September 12, 2021 at 2:55:15 PM UTC+3, David Brown > >> I think it's fair to say there is scope for improvement in the way > >> gcc documentation is handled, but it is still a good deal better > >> than many compilers and other projects. > > > > Comparatively to public variant of llvm/clang docs - sure, but that's > > pretty low bar. I never looked at apple's and google's releases of > > clang docs, hopefully they are better than public release. > > Comparatively to Microsoft - it depends. Some parts of the gcc docs > > are better others are worse. However I would think that when > > Microsoft's maintainers see a mistake in their online docs for old > > compiler, or, more likely, are pointed to mistake by community, they > > fix it without hesitation. > > > I have not nearly enough experience with the documentation of MS's > compiler to tell - I have only ever looked up a few points. (The same > with clang.) I've read manuals for many other compilers over the years, > which are often much worse, but none of these tools are direct > comparisons with gcc (being commercial embedded toolchains targetting > one or a few specific microcontroller cores). > > One especially "fun" case was a toolchain that failed to zero-initialise > non-local objects that were not explicitly initialised - what you > normally get by startup code clearing the ".bss" segment. This > "feature" was documented in a footnote in the middle of the manual, > noting that the behaviour was not standards conforming and would > silently break existing C code. I suppose, you are talking about TI compilers. IIRC, in their old docs (around 1998 to 2002) it was documented in relatively clear way. But it was quite a long time ago so it's possible that I misremember.
[toc] | [prev] | [next] | [standalone]
Page 8 of 16 — ← Prev page 1 … 6 7 [8] 9 10 … 16 Next page →
Back to top | Article view | comp.lang.c++
csiph-web