From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1586 invoked by alias); 9 Sep 2012 16:24:18 -0000 Received: (qmail 1576 invoked by uid 22791); 9 Sep 2012 16:24:16 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 09 Sep 2012 16:24:04 +0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/54419] [4.8 Regression] Compiling libstdc++-v3/src/c++11/random.cc fails on platforms not knowing rdrand Date: Sun, 09 Sep 2012 16:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Keywords: X-Bugzilla-Severity: blocker X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-09/txt/msg00717.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54419 --- Comment #58 from Jonathan Wakely 2012-09-09 16:21:25 UTC --- (In reply to comment #56) > I suppose that the lack of responsiveness may be ultimately due to the fact > that the issue only shows up on some specific systems (that is, those using old > assemblers) which normally the maintainers (in general, not just the library > ones) working on mainline GCC don't develop on The fact the build was broken on the compile farm machines would normally be an issue for me, but as I was on holiday I wasn't building gcc. As soon as I tried to build on the compile farm I found the PR and reviewed the patch. Again, if it had been sent to the right list I could have done that sooner, instead of waiting until the bug affected me directly.