Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #118058 > unrolled thread
| Started by | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| First post | 2023-12-10 10:46 +0100 |
| Last post | 2024-02-14 15:57 +0100 |
| Articles | 20 on this page of 213 — 14 participants |
Back to article view | Back to comp.lang.c++
Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-10 10:46 +0100
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-10 21:48 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-11 04:15 +0100
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-11 17:12 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-11 18:19 +0100
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-13 15:16 +0000
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-13 15:25 +0000
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-14 15:06 +0000
Re: Sieve of Erastosthenes optimized to the max red floyd <no.spam.here@its.invalid> - 2023-12-14 08:20 -0800
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-12-23 10:30 -0800
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-23 21:20 +0000
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-12-24 00:36 -0800
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-29 18:03 +0000
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-01-13 21:31 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-20 13:44 +0100
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-21 15:30 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-21 17:07 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-21 17:13 +0100
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-12-23 10:21 -0800
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2023-12-23 21:21 +0000
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-12-24 10:49 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-21 14:23 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-22 04:28 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-21 20:02 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-22 17:55 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-23 12:52 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-24 11:03 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-24 13:24 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-26 06:00 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-25 21:39 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-26 10:27 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-26 12:24 -0800
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-26 23:35 +0000
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-26 15:37 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-26 21:59 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-27 10:23 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-27 20:49 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-28 12:00 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-28 15:38 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-29 04:17 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-28 20:58 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-29 10:58 +0100
Re: Sieve of Erastosthenes optimized to the max David Brown <david.brown@hesbynett.no> - 2023-12-29 13:56 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-29 17:04 +0100
Re: Sieve of Erastosthenes optimized to the max David Brown <david.brown@hesbynett.no> - 2023-12-30 19:27 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-31 11:22 +0100
Re: Sieve of Erastosthenes optimized to the max scott@slp53.sl.home (Scott Lurndal) - 2023-12-31 18:49 +0000
Re: Sieve of Erastosthenes optimized to the max David Brown <david.brown@hesbynett.no> - 2024-01-01 12:46 +0100
Re: Sieve of Erastosthenes optimized to the max scott@slp53.sl.home (Scott Lurndal) - 2023-12-29 16:01 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-29 17:06 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-29 13:45 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-29 14:09 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-29 14:12 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-30 05:42 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-29 20:45 -0800
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-30 04:56 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-30 06:09 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-30 05:51 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-30 10:15 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-30 20:35 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-31 06:54 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-31 07:01 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-31 11:20 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-31 17:30 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-01 06:21 +0100
Re: Sieve of Erastosthenes optimized to the max scott@slp53.sl.home (Scott Lurndal) - 2023-12-31 18:44 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-01 06:22 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-01 08:28 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-01 14:11 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-01 15:36 -0800
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-30 04:51 +0000
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-30 12:00 -0800
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2023-12-29 17:29 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-30 05:45 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-30 11:58 -0800
Re: Sieve of Erastosthenes optimized to the max red floyd <no.spam.here@its.invalid> - 2023-12-30 14:58 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-31 11:49 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-31 06:51 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-31 11:36 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-01 07:28 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-31 22:53 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-01 14:11 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-01 15:34 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-02 11:55 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-02 10:38 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-03 06:48 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-03 13:32 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-04 04:37 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-05 19:21 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-06 08:18 +0100
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-06 08:31 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-06 10:30 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-06 13:15 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-06 13:19 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-07 10:14 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-07 10:10 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-07 12:46 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-08 06:48 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-08 12:18 -0800
Re: Sieve of Erastosthenes optimized to the max red floyd <no.spam.here@its.invalid> - 2024-01-08 17:14 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-09 07:19 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-01-09 23:33 -0800
Re: Sieve of Erastosthenes optimized to the max Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-09 02:02 +0000
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-01-09 15:12 +0100
OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Vir Campestris <vir.campestris@invalid.invalid> - 2024-01-29 21:31 +0000
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-16 08:06 -0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-02-16 18:30 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-23 05:51 -0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-02-24 10:45 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-25 00:48 -0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-02-25 15:51 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-03-11 10:10 -0700
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-12 10:15 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-14 12:44 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-14 07:25 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-14 17:20 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-14 17:35 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-14 17:41 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-14 19:20 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-15 16:30 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-15 11:21 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) wij <wyniijj5@gmail.com> - 2024-03-15 19:07 +0800
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-15 12:56 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-14 19:20 +0100
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-04-20 08:35 -0700
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-04-20 18:34 +0200
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-04-20 18:35 +0200
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-04-24 12:28 -0700
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Bonita Montero <Bonita.Montero@gmail.com> - 2024-04-25 06:19 +0200
Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-04-25 14:14 -0700
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-31 11:39 -0800
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2023-12-29 13:52 -0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2023-12-27 06:06 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-22 19:34 -0700
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-23 17:54 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-23 14:04 -0700
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-24 07:30 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-24 12:52 -0700
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-03-24 21:00 +0100
Re: Sieve of Erastosthenes optimized to the max "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-03-24 13:05 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-05-16 17:28 +0100
Re: Sieve of Erastosthenes optimized to the max Ben Bacarisse <ben@bsb.me.uk> - 2024-05-16 21:40 +0100
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-05-21 19:06 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-05-30 12:32 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-05-30 14:17 +0200
Re: Sieve of Erastosthenes optimized to the max Paavo Helde <eesnimi@osa.pri.ee> - 2024-05-30 19:55 +0300
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-05-31 10:17 +0200
Re: Sieve of Erastosthenes optimized to the max Paavo Helde <eesnimi@osa.pri.ee> - 2024-05-31 20:52 +0300
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-05-30 22:17 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-06-01 21:07 +0100
Re: Sieve of Erastosthenes optimized to the max Richard Damon <richard@damon-family.org> - 2024-06-01 20:43 -0400
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-06-02 03:23 -0700
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-06-02 19:50 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-06-18 20:56 +0100
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-06-18 17:34 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-06-30 21:47 +0100
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-07-01 23:20 -0700
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-07-02 21:24 +0100
Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-07-03 11:25 +0100
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-07-15 06:15 -0700
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-07-20 07:41 -0700
OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-07-25 12:46 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-10 07:07 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-12 15:32 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-16 07:48 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-15 17:52 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-16 08:40 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-16 19:35 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-16 19:55 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-19 21:23 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 17:21 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 17:24 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 17:43 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-20 17:55 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 18:59 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 12:08 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-27 06:09 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-09-01 21:23 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-01 20:40 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-09-02 07:08 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-09-03 17:45 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-09-28 03:46 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-09-28 13:49 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-10-02 11:44 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-10-02 13:10 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-10-07 08:41 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-10-20 12:44 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-11-04 03:56 -0800
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-19 21:34 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max red floyd <no.spam.here@its.invalid> - 2024-08-19 21:08 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-20 21:14 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 09:35 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 08:31 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 19:20 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 19:36 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 19:39 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-20 20:13 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max scott@slp53.sl.home (Scott Lurndal) - 2024-08-20 20:50 +0000
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-22 17:30 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-08-22 18:38 +0200
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-22 21:47 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max Vir Campestris <vir.campestris@invalid.invalid> - 2024-08-22 21:56 +0100
Re: OT: Re: Sieve of Erastosthenes optimized to the max red floyd <no.spam.here@its.invalid> - 2024-08-22 17:00 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 10:59 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Andrey Tarasevich <andreytarasevich@hotmail.com> - 2024-09-28 15:21 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-26 12:47 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-18 19:52 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-10 17:24 -0700
Re: OT: Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-08-11 00:00 -0700
Re: Sieve of Erastosthenes optimized to the max Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-07-23 07:34 -0700
Re: Sieve of Erastosthenes optimized to the max wij <wyniijj5@gmail.com> - 2024-02-14 00:15 +0800
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-02-13 19:08 +0100
Re: Sieve of Erastosthenes optimized to the max Bonita Montero <Bonita.Montero@gmail.com> - 2024-02-14 15:57 +0100
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-15 11:21 +0100 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <ut17ft$27l64$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118523 |
Am 15.03.2024 um 09:30 schrieb wij: > Number=18446744073709551615 > 18446744073709551615= 3*5*17*257*641*65537*6700417* > Number=18446744073709551557 > 18446744073709551557= 18446744073709551557 > Number= > > ----------- > Note: 18446744073709551615= 2^64-1 > Note: 18446744073709551557 is the greatest prime found less than 2^64. > This shoud be the worst case (took about 5 sec.) > Note: Constructing PrimeTab ptab(1LL<<32) consumes about (2^32)/30= 143 (Mbytes) > > I know you are addressing hard-ware programming, but IMO, the performance/cost > ratio is very low. > > > Then you don't calculate the whole range from two up to your upper bound. If you have 30 numbers per 8 bits you'd need 1.073.741.824 Gigabytes for that.
[toc] | [prev] | [next] | [standalone]
| From | wij <wyniijj5@gmail.com> |
|---|---|
| Date | 2024-03-15 19:07 +0800 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <0ca3bba6e95ca432d4b72bf88526aeb799fba90e.camel@gmail.com> |
| In reply to | #118524 |
On Fri, 2024-03-15 at 11:21 +0100, Bonita Montero wrote: > Am 15.03.2024 um 09:30 schrieb wij: > > > Number=18446744073709551615 > > 18446744073709551615= 3*5*17*257*641*65537*6700417* > > Number=18446744073709551557 > > 18446744073709551557= 18446744073709551557 > > Number= > > > > ----------- > > Note: 18446744073709551615= 2^64-1 > > Note: 18446744073709551557 is the greatest prime found less than 2^64. > > This shoud be the worst case (took about 5 sec.) > > Note: Constructing PrimeTab ptab(1LL<<32) consumes about (2^32)/30= 143 (Mbytes) > > > > I know you are addressing hard-ware programming, but IMO, the performance/cost > > ratio is very low. > > > > > > > > Then you don't calculate the whole range from two up to your upper > bound. If you have 30 numbers per 8 bits you'd need 1.073.741.824 > Gigabytes for that. > Don't know what the upper bound and "1.073.741.824" mean. If I have 8-giga RAM, I can setup a primetable for number <= 8G*30= 2.4*10^11. From this table, I can factorize number <= (2.4*10^11)^2= 5.76*10^22 (a 76-bit number). As I remember, your program does not use integer greater than uint64_t, why you ask for such a big number?
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-15 12:56 +0100 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <ut1d1v$28pqg$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118525 |
Am 15.03.2024 um 12:07 schrieb wij: > On Fri, 2024-03-15 at 11:21 +0100, Bonita Montero wrote: >> Am 15.03.2024 um 09:30 schrieb wij: >> >>> Number=18446744073709551615 >>> 18446744073709551615= 3*5*17*257*641*65537*6700417* >>> Number=18446744073709551557 >>> 18446744073709551557= 18446744073709551557 >>> Number= >>> >>> ----------- >>> Note: 18446744073709551615= 2^64-1 >>> Note: 18446744073709551557 is the greatest prime found less than 2^64. >>> This shoud be the worst case (took about 5 sec.) >>> Note: Constructing PrimeTab ptab(1LL<<32) consumes about (2^32)/30= 143 (Mbytes) >>> >>> I know you are addressing hard-ware programming, but IMO, the performance/cost >>> ratio is very low. >>> >>> >>> >> >> Then you don't calculate the whole range from two up to your upper >> bound. If you have 30 numbers per 8 bits you'd need 1.073.741.824 >> Gigabytes for that. >> > > Don't know what the upper bound and "1.073.741.824" mean. If I have 8-giga RAM, I can setup a > primetable for number <= 8G*30= 2.4*10^11. From this table, I can > factorize number <= (2.4*10^11)^2= 5.76*10^22 (a 76-bit number). Maybe, but you can't store the whole range in memory but just calculate segments beyond sqrt( max ) fitting into memory. > As I remember, your program does not use integer greater than uint64_t, why you ask for such > a big number? >
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-14 19:20 +0100 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <usvf4h$1p4qk$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118518 |
Am 14.03.2024 um 10:35 schrieb wij:
> On Thu, 2024-03-14 at 17:20 +0800, wij wrote:
>> On Thu, 2024-03-14 at 07:25 +0100, Bonita Montero wrote:
>>> Am 14.03.2024 um 05:44 schrieb wij:
>>>> On Tue, 2024-03-12 at 10:15 +0100, Bonita Montero wrote:
>>>>> Am 11.03.2024 um 18:10 schrieb Tim Rentsch:
>>>>>
>>>>>> Sounds like you're using 1 bit per number, most of which are
>>>>>> wasted. If you use a different encoding the memory requirements
>>>>>> can be much smaller. How much memory do you have on the box?
>>>>>> If you have 64G you should be able to determine all primes
>>>>>> less than 1.5 trillion, using a simple encoding.
>>>>>
>>>>> I'm omitting even numbers and I handle the number two as a
>>>>> special case; that's the fastest solution.
>>>>>
>>>>>> I've mentioned this encoding before but let me give it again.
>>>>>> If numbers are considered mod 30, there are only 8 residues
>>>>>> that are not divisible by 2, 3, or 5. The 8 residues are
>>>>>> 1, 7, 11, 13, 17, 19, 23, and 29. So a single byte can
>>>>>> hold all the information needed for 30 numbers, which means
>>>>>>
>>>>>> 1500000000000 / 30 = 50000000000
>>>>>>
>>>>>> which is to say 50 gigabytes should suffice.
>>>>>
>>>>> Show me the code.
>>>>>
>>>>
>>>> Every 30 natural numbers (or more) can be coded in one byte(8 bits):
>>>
>>> Show me a working sieve with that that beats my code.
>>>
>>
>> I am not "Tim Rentsch". I did not intend to beat your code but try to make
>> things (what I saw) clear, and thought you might be confused. In general,
>> I cannot fully understand your code. Last time I copied your code, it did
>> not compile on my Linux machine.
>>
>>>> //----------------------------------------
>>>> #include <Wy.stdlib.h>
>>>> #include <CSCall/VLInt.h>
>>>>
>>>> // [Syn] PrimeTab is a table for prime numbers
>>>> //
>>>> class PrimeTab {
>>>> public:
>>>> typedef uint64_t NumType;
>>>>
>>>> private:
>>>> WY_ENSURE(sizeof(NumType)<=sizeof(size_t));
>>>> Wy::VLInt m_ptab;
>>>> NumType m_maxn;
>>>>
>>>> // [Syn] Get the bit position storing info. for n
>>>> // 0= pos for n (n is composite) is not available
>>>> //
>>>> static size_t bpos(NumType n) {
>>>> constexpr NumType Lcm=2*3*5;
>>>> const NumType grp= 8*(n/Lcm);
>>>> switch(n%30) {
>>>> case 1: return grp;
>>>> case 7: return grp+1;
>>>> case 11: return grp+2;
>>>> case 13: return grp+3;
>>>> case 17: return grp+4;
>>>> case 19: return grp+5;
>>>> case 23: return grp+6;
>>>> case 29: return grp+7;
>>>> default: return 0;
>>>> }
>>>> };
>>>>
>>>> public:
>>>> WY_DECL_REPLY;
>>>> PrimeTab() : m_ptab(), m_maxn(0) {};
>>>> PrimeTab(const PrimeTab& s) : m_ptab(s.m_ptab), m_maxn(s.m_maxn) {};
>>>> PrimeTab(PrimeTab& s, Wy::ByMove_t) : m_ptab(s.m_ptab,Wy::ByMove),
>>>> m_maxn(s.m_maxn) {};
>>>> explicit PrimeTab(NumType maxn) : m_ptab(), m_maxn(maxn) {
>>>> for(NumType n=2; n<=m_maxn; ++n) {
>>>> size_t p= bpos(n);
>>>> if(p==0) {
>>>> continue; // composite number
>>>> }
>>>> if(m_ptab.bit(p)) {
>>>> continue; // composite number
>>>> }
>>>>
>>>> for(NumType m=n+n; m<=m_maxn; m+=n) {
>>>> Wy::Errno r=m_ptab.set_bit(bpos(m),true);
>>>> if(r!=Wy::Ok) {
>>>> WY_THROW( Reply(r) );
>>>> }
>>>> }
>>>> };
>>>> };
>>>> NumType max_num() const { return m_maxn; };
>>>> bool is_prime(NumType n) const {
>>>> if(n>m_maxn) {
>>>> WY_THROW( Reply(EINVAL) );
>>>> }
>>>> if(n<=6) {
>>>> switch(n) {
>>>> case 1: // FALLTHROUGH
>>>> case 2: // FALLTHROUGH
>>>> case 3: // FALLTHROUGH
>>>> case 5: return true;
>>>> default: return false;
>>>> }
>>>> }
>>>> size_t p= bpos(n);
>>>> if(p==0) {
>>>> return false;
>>>> }
>>>> return !m_ptab.bit(p);
>>>> };
>>>> void swap(PrimeTab& ano) {
>>>> m_ptab.swap(ano.m_ptab);
>>>> Wy::swap(m_maxn, ano.m_maxn);
>>>> };
>>>> void reset() {
>>>> m_ptab.reset();
>>>> };
>>>>
>>>> Wy::Errno reset(NumType maxn) try {
>>>> PrimeTab tmp(maxn);
>>>> this->swap(tmp);
>>>> return Wy::Ok;
>>>> }
>>>> catch(const Wy::Errno& e) {
>>>> WY_RETURN(e);
>>>> };
>>>> Wy::Errno reset(const PrimeTab& rhs) {
>>>> WY_RETURN(m_ptab.reset(rhs.m_ptab));
>>>> };
>>>> PrimeTab& operator=(const PrimeTab& rhs) {
>>>> Wy::Errno r=m_ptab.reset(rhs.m_ptab);
>>>> if(r!=Wy::Ok) {
>>>> WY_THROW( Reply(r) );
>>>> }
>>>> return *this;
>>>> };
>>>> };
>>>>
>>>>
>>>
>>
> #include <Wy.stdio.h>
> #include "PrimeTab.h"
>
> using namespace Wy;
>
> void t1() {
> size_t pcnt;
> PrimeTab ptab(1LL<<31);
> pcnt=0;
> for(size_t n=0; n<ptab.max_num(); ++n) {
> if(ptab.is_prime(n)) {
> ++pcnt;
> }
> }
> cout << "pcnt=" << pcnt << WY_ENDL;
> };
>
> int main()
> try {
> t1();
> cout << "OK" WY_ENDL;
> return 0;
> }
> catch(const Errno& e) {
> cerr << wrd(e) << WY_ENDL;
> return -1;
> }
> catch(...) {
> cerr << "main caught(...)" WY_ENDL;
> return -1;
> };
>
> //----------------------
> []$ g++ t.cpp -lwy -O2
> []$ time ./a.out
> pcnt=105097566
> OK
>
> real 0m34.223s
> user 0m33.975s
> sys 0m0.079s
>
> PrimeTab(1LL<<31) should be able to test number <= 2^32
For my code this takes 1.7 seconds on a single Zen4 core with 5.7GHz.
With all 32 threads this takes 0,165 seconds. Any questions ? There's
a lot to do with your code ...
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-04-20 08:35 -0700 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <86wmosvyh0.fsf@linuxsc.com> |
| In reply to | #118511 |
Bonita Montero <Bonita.Montero@gmail.com> writes: > Am 11.03.2024 um 18:10 schrieb Tim Rentsch: > >> Sounds like you're using 1 bit per number, most of which are >> wasted. If you use a different encoding the memory requirements >> can be much smaller. How much memory do you have on the box? >> If you have 64G you should be able to determine all primes >> less than 1.5 trillion, using a simple encoding. > > I'm omitting even numbers and I handle the number two as a > special case; that's the fastest solution. > >> I've mentioned this encoding before but let me give it again. >> If numbers are considered mod 30, there are only 8 residues >> that are not divisible by 2, 3, or 5. The 8 residues are >> 1, 7, 11, 13, 17, 19, 23, and 29. So a single byte can >> hold all the information needed for 30 numbers, which means >> >> 1500000000000 / 30 = 50000000000 >> >> which is to say 50 gigabytes should suffice. > > Show me the code. Apparently you have missed the point.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-04-20 18:34 +0200 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <v00qr6$3orfb$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118813 |
Am 20.04.2024 um 17:35 schrieb Tim Rentsch: > Bonita Montero <Bonita.Montero@gmail.com> writes: > >> Am 11.03.2024 um 18:10 schrieb Tim Rentsch: >> >>> Sounds like you're using 1 bit per number, most of which are >>> wasted. If you use a different encoding the memory requirements >>> can be much smaller. How much memory do you have on the box? >>> If you have 64G you should be able to determine all primes >>> less than 1.5 trillion, using a simple encoding. >> >> I'm omitting even numbers and I handle the number two as a >> special case; that's the fastest solution. >> >>> I've mentioned this encoding before but let me give it again. >>> If numbers are considered mod 30, there are only 8 residues >>> that are not divisible by 2, 3, or 5. The 8 residues are >>> 1, 7, 11, 13, 17, 19, 23, and 29. So a single byte can >>> hold all the information needed for 30 numbers, which means >>> >>> 1500000000000 / 30 = 50000000000 >>> >>> which is to say 50 gigabytes should suffice. >> >> Show me the code. > > Apparently you have missed the point. I want to see the code for your idea.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-04-20 18:35 +0200 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <v00qs0$3orfb$2@raubtier-asyl.eternal-september.org> |
| In reply to | #118815 |
Am 20.04.2024 um 18:34 schrieb Bonita Montero: > Am 20.04.2024 um 17:35 schrieb Tim Rentsch: >> Bonita Montero <Bonita.Montero@gmail.com> writes: >> >>> Am 11.03.2024 um 18:10 schrieb Tim Rentsch: >>> >>>> Sounds like you're using 1 bit per number, most of which are >>>> wasted. If you use a different encoding the memory requirements >>>> can be much smaller. How much memory do you have on the box? >>>> If you have 64G you should be able to determine all primes >>>> less than 1.5 trillion, using a simple encoding. >>> >>> I'm omitting even numbers and I handle the number two as a >>> special case; that's the fastest solution. >>> >>>> I've mentioned this encoding before but let me give it again. >>>> If numbers are considered mod 30, there are only 8 residues >>>> that are not divisible by 2, 3, or 5. The 8 residues are >>>> 1, 7, 11, 13, 17, 19, 23, and 29. So a single byte can >>>> hold all the information needed for 30 numbers, which means >>>> >>>> 1500000000000 / 30 = 50000000000 >>>> >>>> which is to say 50 gigabytes should suffice. >>> >>> Show me the code. >> >> Apparently you have missed the point. > > I want to see the code for your idea. > Eh, wij's idea ...
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-04-24 12:28 -0700 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <86o79ywofh.fsf@linuxsc.com> |
| In reply to | #118815 |
Bonita Montero <Bonita.Montero@gmail.com> writes: > Am 20.04.2024 um 17:35 schrieb Tim Rentsch: > >> Bonita Montero <Bonita.Montero@gmail.com> writes: [...] >>> Show me the code. >> >> Apparently you have missed the point. > > I want to see the code for your idea. Yes I already understood what you want. That is what led me to conclude that you have missed the point.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-04-25 06:19 +0200 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <v0clk4$2qdj9$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118876 |
Am 24.04.2024 um 21:28 schrieb Tim Rentsch: > Bonita Montero <Bonita.Montero@gmail.com> writes: > >> Am 20.04.2024 um 17:35 schrieb Tim Rentsch: >> >>> Bonita Montero <Bonita.Montero@gmail.com> writes: > [...] >>>> Show me the code. >>> >>> Apparently you have missed the point. >> >> I want to see the code for your idea. > > Yes I already understood what you want. That is what > led me to conclude that you have missed the point. I don't have "missed the point"; I just want to see the code basing on the mentioned idea that is faster than my code.
[toc] | [prev] | [next] | [standalone]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Date | 2024-04-25 14:14 -0700 |
| Subject | Re: OT: A better sieve (was Re: Sieve of Erastosthenes optimized to the max) |
| Message-ID | <867cglw3eb.fsf@linuxsc.com> |
| In reply to | #118881 |
Bonita Montero <Bonita.Montero@gmail.com> writes: > Am 24.04.2024 um 21:28 schrieb Tim Rentsch: > >> Bonita Montero <Bonita.Montero@gmail.com> writes: >> >>> Am 20.04.2024 um 17:35 schrieb Tim Rentsch: >>> >>>> Bonita Montero <Bonita.Montero@gmail.com> writes: >> >> [...] >> >>>>> Show me the code. >>>> >>>> Apparently you have missed the point. >>> >>> I want to see the code for your idea. >> >> Yes I already understood what you want. That is what >> led me to conclude that you have missed the point. > > I don't have "missed the point"; [...] There is more than one school of thought on that question.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-12-31 11:39 -0800 |
| Message-ID | <umsg0t$1r16p$1@dont-email.me> |
| In reply to | #118169 |
On 12/30/2023 9:51 PM, Bonita Montero wrote: > Am 30.12.2023 um 20:58 schrieb Chris M. Thomasson: > >> Huh? Wow, you really need to write Intel a letter about it wrt their >> older hyperthreaded processors! ... > > The suggestion Intel made at this point is superfluous. > >> Intel's suggestions for how to mitigate the problem in their earlier >> hyperhtreaded processors actually worked wrt improving performance. ... > > I'm pretty sure they never ran the numbers on that. I am pretty sure you never read that paper before, even now. > >
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2023-12-29 13:52 -0800 |
| Message-ID | <umnf3q$ve1t$3@dont-email.me> |
| In reply to | #118143 |
On 12/28/2023 7:17 PM, Bonita Montero wrote:
> Am 29.12.2023 um 00:38 schrieb Chris M. Thomasson:
>
>> The use of alloca to try to get around the problem in their (Intel's)
>> early hyperthreaded processors was real, and actually helped. It was
>> in the Intel docs.
>
> I don't believe it.
>
I actually found an early version my old code on the wayback machine
that does this. Take note of the following function. It did improve
performance way back on those early hyperthreaded processors.
https://web.archive.org/web/20060214112446/http://appcore.home.comcast.net/appcore/src/ac_thread_c.html
___________________
void* AC_CDECL
prv_thread_entry
( void *state )
{
int ret;
void *uret;
ac_thread_t *_this = state;
ret = pthread_setspecific
( g_tls_key,
_this );
if ( ret ) { assert( ! ret ); abort(); }
if ( _this->id < 64 )
{
AC_OS_ALLOCA( 2048 * _this->id );
uret = _this->fp_entry( (void*)_this->state );
}
else
{
uret = _this->fp_entry( (void*)_this->state );
}
return uret;
}
___________________
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2023-12-27 06:06 +0100 |
| Message-ID | <umgbci$3qpao$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118134 |
Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: > So, are you familiar with Intel's early hyper threading problem? > There was false sharing between the ... False sharing can only happen between different cores.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-22 19:34 -0700 |
| Message-ID | <utlf3h$393l6$1@dont-email.me> |
| In reply to | #118137 |
On 12/26/2023 9:06 PM, Bonita Montero wrote: > Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: > >> So, are you familiar with Intel's early hyper threading problem? >> There was false sharing between the ... > > False sharing can only happen between different cores. Sigh.
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-23 17:54 +0100 |
| Message-ID | <utn1fp$3oeks$2@raubtier-asyl.eternal-september.org> |
| In reply to | #118532 |
Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: > On 12/26/2023 9:06 PM, Bonita Montero wrote: >> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >> >>> So, are you familiar with Intel's early hyper threading problem? >>> There was false sharing between the ... >> >> False sharing can only happen between different cores. > > Sigh. Why ? Do you think false sharing can happen between the threads of a single core ?
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-23 14:04 -0700 |
| Message-ID | <utng4n$3rn1f$2@dont-email.me> |
| In reply to | #118534 |
On 3/23/2024 9:54 AM, Bonita Montero wrote: > Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: >> On 12/26/2023 9:06 PM, Bonita Montero wrote: >>> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >>> >>>> So, are you familiar with Intel's early hyper threading problem? >>>> There was false sharing between the ... >>> >>> False sharing can only happen between different cores. >> >> Sigh. > > Why ? Do you think false sharing can happen between the threads > of a single core ? > Sigh again...
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-24 07:30 +0100 |
| Message-ID | <utoh9d$6lrr$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118537 |
Am 23.03.2024 um 22:04 schrieb Chris M. Thomasson: > On 3/23/2024 9:54 AM, Bonita Montero wrote: >> Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: >>> On 12/26/2023 9:06 PM, Bonita Montero wrote: >>>> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >>>> >>>>> So, are you familiar with Intel's early hyper threading problem? >>>>> There was false sharing between the ... >>>> >>>> False sharing can only happen between different cores. >>> >>> Sigh. >> >> Why ? Do you think false sharing can happen between the threads >> of a single core ? >> > > Sigh again... On a single core CPU with two thread's there's never false sharing.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-24 12:52 -0700 |
| Message-ID | <utq0ag$hvrl$3@dont-email.me> |
| In reply to | #118538 |
On 3/23/2024 11:30 PM, Bonita Montero wrote: > Am 23.03.2024 um 22:04 schrieb Chris M. Thomasson: >> On 3/23/2024 9:54 AM, Bonita Montero wrote: >>> Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: >>>> On 12/26/2023 9:06 PM, Bonita Montero wrote: >>>>> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >>>>> >>>>>> So, are you familiar with Intel's early hyper threading problem? >>>>>> There was false sharing between the ... >>>>> >>>>> False sharing can only happen between different cores. >>>> >>>> Sigh. >>> >>> Why ? Do you think false sharing can happen between the threads >>> of a single core ? >>> >> >> Sigh again... > > On a single core CPU with two thread's there's never false sharing. > Whatever you say man... ;^o
[toc] | [prev] | [next] | [standalone]
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Date | 2024-03-24 21:00 +0100 |
| Message-ID | <utq0os$ibqn$1@raubtier-asyl.eternal-september.org> |
| In reply to | #118543 |
Am 24.03.2024 um 20:52 schrieb Chris M. Thomasson: > On 3/23/2024 11:30 PM, Bonita Montero wrote: >> Am 23.03.2024 um 22:04 schrieb Chris M. Thomasson: >>> On 3/23/2024 9:54 AM, Bonita Montero wrote: >>>> Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: >>>>> On 12/26/2023 9:06 PM, Bonita Montero wrote: >>>>>> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >>>>>> >>>>>>> So, are you familiar with Intel's early hyper threading problem? >>>>>>> There was false sharing between the ... >>>>>> >>>>>> False sharing can only happen between different cores. >>>>> >>>>> Sigh. >>>> >>>> Why ? Do you think false sharing can happen between the threads >>>> of a single core ? >>>> >>> >>> Sigh again... >> >> On a single core CPU with two thread's there's never false sharing. >> > > Whatever you say man... ;^o You said: > So, are you familiar with Intel's early hyper threading problem? There was false sharing between the hyperhtreads. False sharing is a kind of cache thrashing, but not every cache thrashing is false sharing. False sharing can only happen between different cores and the Pentium 4 HT does only have one core.
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2024-03-24 13:05 -0700 |
| Message-ID | <utq11p$icmm$1@dont-email.me> |
| In reply to | #118544 |
On 3/24/2024 1:00 PM, Bonita Montero wrote: > Am 24.03.2024 um 20:52 schrieb Chris M. Thomasson: >> On 3/23/2024 11:30 PM, Bonita Montero wrote: >>> Am 23.03.2024 um 22:04 schrieb Chris M. Thomasson: >>>> On 3/23/2024 9:54 AM, Bonita Montero wrote: >>>>> Am 23.03.2024 um 03:34 schrieb Chris M. Thomasson: >>>>>> On 12/26/2023 9:06 PM, Bonita Montero wrote: >>>>>>> Am 26.12.2023 um 21:24 schrieb Chris M. Thomasson: >>>>>>> >>>>>>>> So, are you familiar with Intel's early hyper threading problem? >>>>>>>> There was false sharing between the ... >>>>>>> >>>>>>> False sharing can only happen between different cores. >>>>>> >>>>>> Sigh. >>>>> >>>>> Why ? Do you think false sharing can happen between the threads >>>>> of a single core ? >>>>> >>>> >>>> Sigh again... >>> >>> On a single core CPU with two thread's there's never false sharing. >>> >> >> Whatever you say man... ;^o > > You said: > > > So, are you familiar with Intel's early hyper threading problem? > There was false sharing between the hyperhtreads. > > False sharing is a kind of cache thrashing, but not every cache > thrashing is false sharing. False sharing can only happen between > different cores and the Pentium 4 HT does only have one core. > Yawn...
[toc] | [prev] | [next] | [standalone]
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
Back to top | Article view | comp.lang.c++
csiph-web