From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7340 invoked by alias); 20 Jul 2011 21:41:37 -0000 Received: (qmail 7317 invoked by uid 22791); 20 Jul 2011 21:41:36 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (74.125.121.67) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 20 Jul 2011 21:41:22 +0000 Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p6KLfKcB003839 for ; Wed, 20 Jul 2011 14:41:21 -0700 Received: from iyh42 (iyh42.prod.google.com [10.241.50.234]) by wpaz13.hot.corp.google.com with ESMTP id p6KLf2XT024368 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Wed, 20 Jul 2011 14:41:19 -0700 Received: by iyh42 with SMTP id 42so956678iyh.39 for ; Wed, 20 Jul 2011 14:41:19 -0700 (PDT) Received: by 10.231.17.3 with SMTP id q3mr1367804iba.21.1311198079126; Wed, 20 Jul 2011 14:41:19 -0700 (PDT) Received: from coign.google.com ([2620:0:1000:2301:21c:25ff:fe14:8d86]) by mx.google.com with ESMTPS id y3sm404127iba.4.2011.07.20.14.41.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Jul 2011 14:41:18 -0700 (PDT) From: Ian Lance Taylor To: Mike Stump Cc: David Edelsohn , gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: PATCH RFA: Build stages 2 and 3 with C++ References: <4E26E775.7070802@moene.org> Date: Thu, 21 Jul 2011 00:10:00 -0000 In-Reply-To: (Mike Stump's message of "Wed, 20 Jul 2011 13:53:12 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-07/txt/msg00398.txt.bz2 Mike Stump writes: >> Presumably the fix will be to use -frandom-seed. > > But, the random seem was to ensure that things that should not collide, don't. If you use 0, then things that should not collide, eventually will and your world with then end. In the present code base, it is perfectly safe to do this. If the codebase is ever extended to use C++ features, then, that code can break. I wasn't suggesting using -frandom-seed=0. Ian