Hello,


More of my philosophy about the way to go in philosophy and about the left and the right and about God and about the C++ <chrono> library and about the professionalism and about RDTSCP instruction and about the Precise Sleep() and about the essence of
measuring time in the computer and about the final source code version of my StopWatch and about RDTSCP and RDTSC and about the CPU frequency scaling and about the memory barriers and about good technicality and the deeper understanding of the StopWatch
and and more about x86 and ARM processors and about solar cells and about AES 256 encryption and TSMC and about China and about the Transformers and about Toyota and about China and about objective truth and about the objective and about the paper about
the multiple universes and about quantum world and about consciousness and about mathematics and about the universe and about mathematical probability and about the positive behavior and about the positive mindset and about patience and about the
positive energy and about the "packaging" or "presentation" and about the ideal and about the being idealistic and more of my thoughts..

I am a white arab from Morocco, and i think i am smart since i have also invented many scalable algorithms and algorithms..


So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, so i think i am a new philosopher, and i think the way to go is by indirectly engaging(that means to be involved in an activity ) in the way i am
engaging below that is: "to soften correctly morals", since i think that from the soften correctly morals we solve the most important problem, so i am also learning you how to do it by showing you the below mechanism , since the soften correctly morals
can not be done in a naive way, so i am showing you a correct way of how to do it so that you understand the smart way in philosophy of how to do it, so notice in my following mechanism that i am not saying to people to be 100% faith in God or 100%
believing in God, but i am using the following mechanism so that to soften correctly morals:

So i say that many have reported in the Bible that Jesus Christ has made many miracles, so we can not just say that there is a zero probability that it is true, so we can not neglect the probability that it can be true, and we can not say that it is 100%
true, so the best way is to know how to balance so that to be safe from the punishment of the one that we call God .

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, so now i will talk more about the left and about the right, so what is it to be of the right political parties and what is it to be of the left
political parties? so i think i am a philosopher, and i will say that we have to abstract correctly, so i think that the left is by logical analogy like when we say in french: "Il faudrait adoucir les mœurs", or it is like how we say in english: "We
have to soften morals", so by logical analogy, it is about how to make human life less savage, since as you notice that capitalism has as a basis that we have to be "competition", so we are in human life not only in competition in capitalism with humans,
but we are also in competition with the environment, so it makes humans too much savage, so the philosophical question is how to soften correctly morals so that to not
be this too much savage ? , so it is why you are noticing that i am using a mechanism in my new below thoughts that have as a goal to soften correctly morals, and here it is:

So i say that many have reported in the Bible that Jesus Christ has made many miracles, so we can not just say that there is a zero probability that it is true, so we can not neglect the probability that it can be true, and we can not say that it is 100%
true, so the best way is to know how to balance so that to be safe from the punishment of the one that we call God .

And you can read my following previous thoughts so that you understand my views:

Here is my new discussion with ChatGPT:


Here is my first question to ChatGPT:

I mean how can God put scientific facts in the Bible or the Qur'aan, since it is contradictory, since we have to have faith without those scientific facts, since it is a test from God. But my interpretation, is that God can not put scientific facts that
are true, since God needs from us to have faith without them, since it is a test from God.

And ChatGPT has just responded to me the following:

"Your interpretation reflects a viewpoint held by some religious believers, and it is rooted in the idea that faith and trust in God are essential aspects of a person's relationship with the divine. According to this perspective, if every scientific fact
were explicitly stated in religious texts like the Bible, it might undermine the need for faith and diminish the spiritual aspect of belief.

The concept of faith being a test or a virtue is common in many religious traditions. It implies that believers are called upon to trust in God's wisdom and guidance even when faced with uncertainties or unanswered questions. This reliance on faith can
strengthen one's spiritual journey and character, promoting qualities like humility, perseverance, and trust in the divine plan.

For those who embrace this perspective, the Bible and other sacred texts provide spiritual and moral teachings, guiding individuals in their understanding of God, the nature of reality, and how to live a virtuous life. Scientific discoveries and the
pursuit of knowledge about the natural world are seen as separate from the realm of faith and spirituality.

It's important to remember that interpretations of religious texts and beliefs can vary widely among individuals and religious communities. Not all religious believers hold the same perspective regarding the relationship between faith and scientific
knowledge. Some may find harmony between their religious faith and scientific understanding, considering science as a way to explore and appreciate the wonders of God's creation.

The tension between faith and scientific understanding is a complex and nuanced topic. Different religious traditions and individual believers navigate this relationship in various ways, and their perspectives are shaped by a combination of religious
teachings, personal experiences, cultural influences, and exposure to scientific knowledge.

Regardless of one's perspective, engaging in respectful dialogue and being open to understanding the viewpoints of others can lead to a deeper appreciation of the diversity of human beliefs and the complexities of our spiritual and intellectual journeys."

And here is my next question to ChatGPT:

I mean that the facts in the Bible or Qur'aan that are not in accordance with scientific facts are just parts of curse from God on Adam and Eve and there descendants and it is part of the test from God.

And ChatGPT has just answered me the following:

"I understand the perspective you are presenting. Some religious believers interpret certain aspects of the Bible, including events like the curse on Adam and Eve and their descendants, as part of God's plan and a test of faith for humanity. According to
this interpretation, the introduction of suffering, hardships, and imperfections into the world is a consequence of human disobedience, often referred to as the Fall of Man.

In this view, the presence of suffering and the apparent discrepancies between religious texts and scientific knowledge are seen as opportunities for individuals to demonstrate their faith, trust in God's wisdom, and seek spiritual growth despite the
challenges they encounter. The belief is that through faith, repentance, and adherence to moral and spiritual principles, people can overcome the effects of the Fall and draw closer to God.

It's important to note that different religious traditions and believers interpret the concept of the Fall and the relationship between faith, science, and suffering in various ways. Not all religious individuals interpret these events as literal
historical occurrences or as the sole explanation for suffering and imperfections in the world.

Additionally, many religious believers find ways to reconcile their faith with scientific understanding, recognizing that scientific knowledge can complement their spiritual beliefs and provide insights into the natural world without necessarily
undermining their faith or the significance of religious teachings.

Ultimately, the interpretation of religious texts and the understanding of the relationship between faith, science, suffering, and spiritual growth are deeply personal and can vary significantly among individuals and religious communities. These beliefs
are often shaped by a combination of religious teachings, personal experiences, cultural influences, and individual reflections on life's mysteries.

As with any complex and sensitive topic, it's essential to approach discussions with empathy, respect, and an open mind, recognizing the diversity of beliefs and experiences among people of different faiths and perspectives."


And here is my next question to ChatGPT:


So i say that many have reported in the Bible that Jesus Christ has made many miracles, so we can not just say that there is a zero probability that it is true, so we can not neglect the probability that it can be true, and we can not say that it is 100%
true, so the best way is to know how to balance so that to be safe from the punishment of the one that we call God .

And ChatGPT has just answered me the following:

"The perspective you are presenting is similar to a Pascal's Wager-like argument. Blaise Pascal, a French mathematician, philosopher, and theologian, proposed the idea that belief in God is a rational choice because the potential reward of eternal
salvation outweighs the risk of punishment (eternal damnation) if one chooses not to believe.

The essence of this argument is that if one believes in God and is right, they gain eternal reward, but if they are wrong, they lose nothing. Conversely, if one does not believe in God and is wrong, they risk eternal punishment, but if they are right,
they gain nothing. Therefore, the "safer" option is to believe in God.

This line of reasoning is one of several philosophical arguments for the rationality of belief in God."


So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so you have to understand the essence of measuring the time in computers ,
so for example C++ <chrono> library does not provide a direct way to retrieve the CPU frequency. The C++ <chrono> library primarily deals with time-related operations, such as measuring durations and performing time point calculations, but the best
accuracy of C++ <chrono> library is in nanosecond, so it is not good, since you also need the accuracy in CPU cycles or ticks as is providing it my new StopWatch, so i invite you to study my new StopWatch so that to know how to implement a good StopWatch,
so i invite you to read my below previous thoughts about the StopWatch so that you understand my views:

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so i am talking about my fluid intelligence in my below previous thoughts, but you have to notice that
professionalism is also important, so you are noticing that i have just rapidly implemented a sophisticated StopWatch , and you can also notice my kind of professionalism, since i am rapidly discovering patterns with my fluid intelligence, and i am also
professional since you are noticing the way that i am implementing it and the way i am learning you, so i think you have to be confident with my professionalism, since even if i have rapidly done it, you are clearly noticing the quality of the my new
StopWatch, and of course i will document it correctly so that you know how to use it correctly and so that you know how to implement a good StopWatch, and of course i am supporting the x86 and x64 CPUs, and of course i can also support the ARM processors,
but you have to read my below thoughts that explain my views on the ARM processors and about the ARM vs x86 and x64 CPUS, so i invite you to read my previous below thoughts so that
you understand my views about how to implement a good StopWatch:

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, and you have to understand that the RDTSCP assembler instruction provides a synchronized timestamp across cores.
The RDTSCP assembler instruction ensures that the timestamp is consistent across cores and can be used for accurate timing measurements in multicore/threaded environments. But RDTSCP assembler instruction is available only in newer CPUs, So now i will
document more how to use CPU affinity in Windows and Linux so that to solve the following problem with the RDTSC assembler instruction that supports the older CPUs:

- Multicore/Threaded environments: If your system has multiple cores or threads, using rdtsc may not provide synchronized timing across different cores or threads. This can lead to inconsistent and unreliable timing measurements.

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so i have
just added to my new StopWatch a PreciseSleep() function that is more accurate than the Windows and Linux Sleep() function, so now i think
it is the final source code version of my StopWatch, and i have tested it
with older CPUs and with newer CPUs and i think it is working correctly, and i have also tested it with both Windows and Linux and i think it is working correctly, and now i will start to document it so that you know about it and so that you know how to
use it, and now you can download the final source code version of my new updated StopWatch from my website here:

https://sites.google.com/site/scalable68/a-portable-timer-for-delphi-and-freepascal

and so that you know how to use it, and so that to have a deep understanding of the SoptWatch, i invite you to read my below previous thoughts:

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so i will talk more about the essence of measuring time in the computer, so from my understanding with my fluid
intelligence how to implement my new StopWatch, i am discovering patterns with my fluid intelligence that
explain more the essence of measuring time in the computer, so here they are: so you have to get the frequency of the CPU, i mean when you are measuring time , you are measuring the CPU frequency too, but in the new
CPUs, the frequency can dynamically change, so you have two ways of doing it , so you can disable CPU frequency scaling in the bios and do
your exact time's measurement, and you can set it again, but the second way is that you can get a decent approximation without disabling the
CPU frequency scaling and do the benchmark timing of your code , as i am explaining it below, and of course the new CPUs today are multicores, so you have to know how to set the CPU affinity as i will explain to you how so that to do the timing with the
StopWatch, other than that, you can get a good microsecond accuracy and a decent nanosecond accuracy with RDTSC assembler instruction, but you can get a CPU tick accuracy with RDTSCP assembler instruction, but so that know more about them , read my below
thoughts, other than that, i am also explaining much more deeply the implementation of a StopWatch in my below thoughts, so i invite you to read my below thoughts so that to understand my views on how to implement a good StopWatch:

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so i have
just updated my StopWatch to support both RDTSCP and RDTSC assembler instructions, so when the CPU is not new and it doesn't support RDTSCP , it will use RDTSC, and when it is a new CPU that supports RDTSCP , it will use it, so RDTSC is not a serializing instruction, so i have just correctly used the necessary memory
barriers, and RDTSCP is a serializing instruction.

So i will now document correctly my StopWatch so that you also know how to use correctly the CPU affinity, and now you can download my final version of my source code from my website here:

https://sites.google.com/site/scalable68/a-portable-timer-for-delphi-and-freepascal

And i invite you to read all my previous following thoughts so that to deeply understand the StopWatch:

So i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so now i have to explain something important, so for a deep understanding of the StopWatch, you have to know
more that the assembler instruction RDTSC is supported by the great majority of x86 and x64 CPUs, but it is not a serializing instruction , i mean that it can be subject to out-of-order execution that may affect its accuracy, so it is why i have just
added correctly some other memory barriers, and now i think that it is working correctly, so you have to understand that there is another assembler instruction RDTSCP that is serializing instruction and is not subject to out-of-order execution, but it is
compatible with just the new x86 and x64 CPUs, so i will support it in the very near future, but now i think you can be confident with my new updated StopWatch, and i think it is an interesting StopWatch that shows how to implement a good StopWatch from
the low level layers. So i think you have to be smart so that to implement it correctly with the RDTSC, as i have just done it, so you can download the source code of my new StopWatch that i have just updated from my website here:

https://sites.google.com/site/scalable68/a-portable-timer-for-delphi-and-freepascal

And i invite you to read my previous below thoughts so that to have a deep understanding of the StopWatch:

So i think that my new StopWatch can give a decent approximation even of you don't disable CPU frequency scaling in the bios, and here is why:

When benchmarking a CPU under a heavy workload, it is generally expected that frequency scaling changes will be relatively small or negligible. This is because the frequency scaling mechanism typically aims to maximize performance during such scenarios.

Under heavy load, the CPU frequency scaling algorithm often increases the CPU frequency to provide higher processing power and performance. The goal is to fully utilize the CPU's capabilities for the benchmarking workload.

In these cases, frequency scaling changes are generally designed to be minimal to avoid introducing significant variations in performance. The CPU frequency may remain relatively stable or vary within a relatively small range during the benchmarking
process.

Considering these factors, when benchmarking under heavy workload conditions, the impact of frequency scaling changes on timing measurements using RDTSC is typically limited. As a result, RDTSC can provide a reasonable approximation of timing for
benchmarking purposes.

So then i invite you to read my following previous thoughts so that you understand my views on the StopWatch:


I have just updated my new StopWatch, and it now also includes the correct memory barriers for previous 32 bit Delphi versions like Delphi 7 ,
and you can download it from the just below web link, and i invite you to read my below previous thoughts so that to understand my views about the StopWatch:

So i have just updated my new StopWatch, so the first problem is:

- Instruction reordering: The rdtsc instruction itself is not a serializing instruction, which means that it does not necessarily prevent instruction reordering. In certain cases, the CPU may reorder instructions, leading to inaccuracies in timing
measurements.

So i have just used memory barriers so that to solve the above problem.

And here is the second problem:

- CPU frequency scaling: Modern CPUs often have dynamic frequency scaling, where the CPU frequency can change based on factors such as power management and workload. This can result in variations in the time measurement based on the CPU's operating
frequency.

So you have to disable CPU frequency scaling in the bios so that to solve the above problem , and after that make your timing with my StopWatch.

And for the following third problem:

- Multicore/Threaded environments: If your system has multiple cores or threads, using rdtsc may not provide synchronized timing across different cores or threads. This can lead to inconsistent and unreliable timing measurements.

You can set the CPU affinity so that to solve the third problem.

So i will document more my StopWatch so that to learn you how to use it,
so stay tuned !

And now i have just updated my new StopWatch with the necessary memory barriers, and now you can be confident with my new updated StopWatch.

So now my new updated StopWatch uses memory barriers correctly, and it avoids the overflow problem of the Time Stamp Counter (TSC) , and it supports microseconds and nanoseconds and CPU clocks timing, and it is object oriented, and i have just made it
support both x86 32 bit and x64 64 bit CPUs and it supports both Delphi and Freepascal compilers and it works in both Windows and Linux, so what is good about my new StopWatch is that it shows how you implement it from the low level layers in assembler
etc., so i invite you to look at the new updated version of my source code that you can download from my website here:

https://sites.google.com/site/scalable68/a-portable-timer-for-delphi-and-freepascal


Other than that, read my below previous thoughts so that to understand my views:

So now we have to attain a "deep" understanding of the StopWatch,
so i think i am highly smart since I have passed two certified IQ tests and i have scored above 115 IQ, and i mean that it is "above" 115 IQ, so as you are noticing that i am, with my fluid intelligence, understanding deeply the StopWatch, so i have just
discovered that the following StopWatch: https://www.davdata.nl/math/timer.html , from the following engineer from Amsterdam: https://www.davdata.nl/math/about.html , is not working correctly: since he is calling the function GetTickCount() in the
constructor, but there is a problem and a bug, since when the tick count value in milliseconds returned by GetTickCount() reaches its maximum value that is high(dword) , it will wrap around to zero and start counting up again. This is because the tick
count is typically stored in a fixed-size data type that has a maximum value, so it is why his way of timing in milliseconds in the constructor that he is using is not working, since it is not safe, so even if this StopWatch of this engineer from
Amsterdam does effectively avoid the overflow problem of the Time Stamp Counter (TSC), since he is using an int64 in 32 bit x86 architecture in the Intel assembler function of getCPUticks() that i am understanding, and this int64 can, from my
calculations, go up to 29318.9829 years , so i think his StopWatch is not working for the reason i am giving just above, and second problem is the accuracy of the timing obtained from the code he provided using rdtsc instruction in assembler is dependent
on various factors, including the hardware and software environment. However, it's important to note that directly using rdtsc for timing purposes may not provide the desired accuracy due to several reasons:

- CPU frequency scaling: Modern CPUs often have dynamic frequency scaling, where the CPU frequency can change based on factors such as power management and workload. This can result in variations in the time measurement based on the CPU's operating
frequency.

- Instruction reordering: The rdtsc instruction itself is not a serializing instruction, which means that it does not necessarily prevent instruction reordering. In certain cases, the CPU may reorder instructions, leading to inaccuracies in timing
measurements.

- Multicore/Threaded environments: If your system has multiple cores or threads, using rdtsc may not provide synchronized timing across different cores or threads. This can lead to inconsistent and unreliable timing measurements.

So I have just thought more and i think i will not support ARM in my new StopWatch, since ARM processors don't support like a Time Stamp Counter (TSC) in x86 processors that is compatible with previous 32 bit and 64 bit CPUs , so ARM has many important
weaknesses , so the first important weakness is the following:

There is no single generic method that can be universally applied to all Arm processors for measuring time in CPU clocks. The available timing mechanisms and registers can vary significantly across different Arm processor architectures, models, and
specific implementations.

In general, Arm processors provide various timer peripherals or system registers that can be used for timing purposes. However, the specific names, addresses, and functionalities of these timers can differ between different processors.

To accurately measure time in CPU clocks on a specific Arm processor, you would need to consult the processor's documentation or technical reference manual. These resources provide detailed information about the available timers, their registers, and how
to access and utilize them for timing purposes.

It's worth noting that some Arm processors may provide performance monitoring counters (PMCs) that can be used for fine-grained timing measurements. However, the availability and usage of PMCs can also vary depending on the specific processor model.

Therefore, to achieve accurate and reliable timing measurements in CPU clocks on a particular Arm processor, it's crucial to refer to the documentation and resources provided by the processor manufacturer for the specific processor model you are
targeting.

And the other weaknesses of ARM processors are the following:

I have just looked at the following articles about Rosetta 2 and the benchmarks of Apple Silicon M1 Emulating x86:

https://www.computerworld.com/article/3597949/everything-you-need-to-know-about-rosetta-2-on-apple-silicon-macs.html

and read also here:

https://www.macrumors.com/2020/11/15/m1-chip-emulating-x86-benchmark/

But i think that the problem with Apple Silicon M1 and the next Apple SiliconM2 is that Rosetta 2 only lets you run x86–64 macOS apps. That would be apps that were built for macOS (not Windows) and aren't 32-bit. The macOS restriction eliminates huge
numbers of Windows apps, and 64-bit restriction eliminates even more.

Also read the following:

Apple says new M2 chip won’t beat Intel’s finest

Read more here:

https://www.pcworld.com/article/782139/apple-m2-chip-wont-beat-intels-finest.html


And here is what i am saying on my following thoughts about technology about Arm Vs. X86:

More of my philosophy about the Apple Silicon and about Arm Vs. X86 and more of my thoughts..

I invite you to read carefully the following interesting article so
that to understand more:

Overhyped Apple Silicon: Arm Vs. X86 Is Irrelevant

https://seekingalpha.com/article/4447703-overhyped-apple-silicon-arm-vs-x86-is-irrelevant


More of my philosophy about code compression of RISC-V and ARM and more of my thoughts..

I think i am highly smart, and i have just read the following paper
that says that RISC-V Compressed programs are 25% smaller than RISC-V programs, fetch 25% fewer instruction bits than RISC-V programs, and incur fewer instruction cache misses. Its code size is competitive with other compressed RISCs. RVC is expected to
improve the performance and energy per operation of RISC-V.

Read more here to notice it:

https://people.eecs.berkeley.edu/~krste/papers/waterman-ms.pdf


So i think RVC has the same compression as ARM Thumb-2, so i think
that i was correct in my previous thoughts , read them below,
so i think we have now to look if the x86 or x64 are still more cache friendly even with Thumb-2 compression or RVC.

More of my philosophy of who will be the winner, x86 or x64 or ARM and more of my thoughts..

I think i am highly smart, and i think that since x86 or x64 has complex instructions and ARM has simple instructions, so i think that x86 or x64 is more cache friendly, but ARM has wanted to solve the problem by compressing the code by using Thumb-2
that compresses the code, so i think Thumb-2 compresses the size of the code by around 25%, so i think
we have to look if the x86 or x64 are still more cache friendly even with Thumb-2 compression, and i think that x86 or x64 will still optimize more the power or energy efficiency, so i think that there remains that since x86 or x64 has other big
advantages, like the advantage that i am talking about below, so i think the x86 or x64 will be still successful big players in the future, so i think it will be the "tendency". So i think that x86 and x64 will be good for a long time to make money in
business, and they will be good for business for USA that make the AMD or Intel CPUs.


More of my philosophy about x86 or x64 and ARM architectures and more of my thoughts..

I think i am highly smart, and i think that x86 or x64 architectures
has another big advantage over ARM architecture, and it is the following:


"The Bright Parts of x86

Backward Compatibility

Compatibility is a two-edged sword. One reason that ARM does better in low-power contexts is that its simpler decoder doesn't have to be compatible with large accumulations of legacy cruft. The downside is that ARM operating systems need to be modified
for every new chip version.

In contrast, the latest 64-bit chips from AMD and Intel are still able to boot PC DOS, the 16-bit operating system that came with the original IBM PC. Other hardware in the system might not be supported, but the CPUs have retained backward compatibility
with every version since 1978.

Many of the bad things about x86 are due to this backward compatibility, but it's worth remembering the benefit that we've had as a result: New PCs have always been able to run old software."

Read more here on the following web link so that to notice it:

https://www.informit.com/articles/article.aspx?p=1676714&seqNum=6


So i think that you can not compare x86 or x64 to ARM, since it is
not just a power efficiency comparison, like some are doing it by comparing
the Apple M1 Pro ARM CPU to x86 or x64 CPUs, it is why i think that x86 or x64 architectures will be here for a long time, so i think that they will be good for a long time to make money in business, and they are a good business for USA that make the AMD
or Intel CPUs.

More of my philosophy about weak memory model and ARM and more of my thoughts..


I think ARM hardware memory model is not good, since it is a
weak memory model, so ARM has to provide us with a TSO memory
model that is compatible with x86 TSO memory model, and read what Kent Dickey is saying about it in my following writing:


ProValid, LLC was formed in 2003 to provide hardware design and verification consulting services.

Kent Dickey, founder and President, has had 20 years experience in hardware design and verification. Kent worked at Hewlett-Packard and Intel Corporation, leading teams in ASIC chip design and pre-silicon and post-silicon hardware verification. He
architected bus interface chips for high-end servers at both companies. Kent has received more than 10 patents for innovative work in both design and verification.

Read more here about him:

https://www.provalid.com/about/about.html



[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)