On 29.02.24 00:29, Chris Johns wrote:
On 28/2/2024 6:24 pm, Sebastian Huber wrote:
On 28.02.24 06:34, Chris Johns wrote:
The manual says:
The string can either be a number (decimal, octal or hex) or
an arbitrary string (in which case it’s converted to a number by
computing CRC32).
The string should be different for every file you compile.
I take this to mean the option `-frandom-seed=0` uses `0` as a number however it
is the same for every file and the manual clearly says it must be different?
Using -frandom-seed=0 seems to be quite common on the internet. The random seed
is rarely used in GCC. The only use case in RTEMS I found is related to the gcov
code coverage instrumentation.
There are lots of things that are common on the internet I ignore 😉
Is this a bug in the documentation?
From my point of view this random seed is a gray area in the compiler.
The cases in which it is used should not matter for the RTEMS build
(except for the code coverage):
https://gcc.gnu.org/pipermail/gcc-help/2024-February/143324.html
I will try to add it only to the coverage flags.
--
embedded brains GmbH & Co. KG
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
