[Bug libfortran/32812] random_seed and date_and_time

2008-03-11 Thread fxcoudert at gcc dot gnu dot org
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2008-03-11 10:50 --- Fixed on mainline. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/32812] random_seed and date_and_time

2008-03-11 Thread fxcoudert at gcc dot gnu dot org
--- Comment #9 from fxcoudert at gcc dot gnu dot org 2008-03-11 10:49 --- Subject: Bug 32812 Author: fxcoudert Date: Tue Mar 11 10:49:13 2008 New Revision: 133104 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=133104 Log: PR libfortran/32812 * intrinsics/random.

[Bug libfortran/32812] random_seed and date_and_time

2008-02-25 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added URL||http://gcc.gnu.org/ml/gcc- |

[Bug libfortran/32812] random_seed and date_and_time

2007-08-12 Thread fxcoudert at gcc dot gnu dot org
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-08-12 19:50 --- (In reply to comment #7) > It might even be better to do bit-wise shuffling to get > the most out of the millisecond-field in date_and_time. I thought about that at the beginning, but then it really gets messy :(

[Bug libfortran/32812] random_seed and date_and_time

2007-08-12 Thread tkoenig at gcc dot gnu dot org
--- Comment #7 from tkoenig at gcc dot gnu dot org 2007-08-12 11:19 --- > So, since it's just shuffling bytes (and it's a bijective operation, of > course), I don't think I'm messing with any of the properties of the > generator. I concur. It might even be better to do bit-wise shuff

[Bug libfortran/32812] random_seed and date_and_time

2007-08-10 Thread fxcoudert at gcc dot gnu dot org
--- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-08-10 21:28 --- (In reply to comment #5) > Your attempt to randomize the seeds really isn't all that good because > there is such a limited amount of entropy in year, month, day, and hour. I do agree. There's no way I'm adding e

[Bug libfortran/32812] random_seed and date_and_time

2007-08-10 Thread kargl at gcc dot gnu dot org
--- Comment #5 from kargl at gcc dot gnu dot org 2007-08-10 20:47 --- (In reply to comment #4) > (In reply to comment #3) > > UGH. > > > > I'd rather document gfortran's behavior than add additional hacks > > into the compiler. > > Hum, I was of the same opinion at first. What somehow

[Bug libfortran/32812] random_seed and date_and_time

2007-08-10 Thread fxcoudert at gcc dot gnu dot org
--- Comment #4 from fxcoudert at gcc dot gnu dot org 2007-08-10 19:23 --- (In reply to comment #3) > UGH. > > I'd rather document gfortran's behavior than add additional hacks > into the compiler. Hum, I was of the same opinion at first. What somehow convinced me that it might be wort

[Bug libfortran/32812] random_seed and date_and_time

2007-08-10 Thread kargl at gcc dot gnu dot org
--- Comment #3 from kargl at gcc dot gnu dot org 2007-08-10 19:10 --- UGH. I'd rather document gfortran's behavior than add additional hacks into the compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32812

[Bug libfortran/32812] random_seed and date_and_time

2007-08-10 Thread fxcoudert at gcc dot gnu dot org
--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-08-10 19:04 --- I guess we have to scramble the seed given by the user, something like this: Index: intrinsics/random.c === --- intrinsics/random.c (revision 127331

[Bug libfortran/32812] random_seed and date_and_time

2007-07-28 Thread fxcoudert at gcc dot gnu dot org
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2007-07-28 13:07 --- (In reply to comment #0) > <[EMAIL PROTECTED]>, This Usenet post can be found at: http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/0b60cf25162534bf/2e8d2775f455a33f -- fxcoudert at gcc do