Re: Re: Big GOTCHAs WITH forprime()

[Oliver Bandel <oliver@first.in-berlin.de>]

Quoting  Ilya Zakharevich <nospam-abuse@ilyaz.org> (snt: 2024-01-13 10:42 +0100 CET) (rcv: 2024-01-13 10:42 +0100 CET):
> On Sat, Jan 13, 2024 at 02:25:53AM +0100, Oliver Bandel wrote:
> > How do you meaure the time in your two short examples at the top?
> > A complete code, that shows it, would be nice.
> 
> The example of the code is immediately above the table.  For example,
> for the bottom right entry:
> 
>      my(s=191*10^15); forprime(p=s, s + 6*10^8,);

That's the code you are running/benchmarking.
But I asked about how you measure the time, and in this context asked
for a complete example.
Are you using a stop-watch?
Or certain commands for benchmarking these snippets?

> 
> > Regarding your crash: I could not confirm it on my (quite old) laptop.
> 
> Mine is 10 years old.  i5-3210M.  (But I do not think this is
> relevant.)

Mine also is about 10 years old, also i5.

It's not irrelevant for getting a rough impression on the timing results,
which I think was something you were reasoning about.
The "old computer" could also trigger you reflecting on how old *your* computer
is. And if there might be hardware issues (defected RAM or so) that may
cause the crash.
As I had no crash, this points not in the direction of a general problem of PARI.


> It is Win 7 with all the possible updates.  Yours is
> Linux & threaded.  (⇒ Different memory layout.)

So you think the different memory layout has to do with the crash?
Or would the different memory layout also be irrelevant to mention?
Not sure, what you intend to say here.

Ciao,
  Oliver