From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16055 invoked by alias); 23 Aug 2005 14:15:28 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 16036 invoked by uid 48); 23 Aug 2005 14:15:27 -0000 Date: Tue, 23 Aug 2005 14:15:00 -0000 Message-ID: <20050823141527.16035.qmail@sourceware.org> From: "tromey at gcc dot gnu dot org" To: java-prs@gcc.gnu.org In-Reply-To: <20050808100453.23283.netzberg@gmail.com> References: <20050808100453.23283.netzberg@gmail.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug java/23283] Sun's JIT faster than gcc for Random.nextDouble X-Bugzilla-Reason: CC X-SW-Source: 2005-q3/txt/msg00378.txt.bz2 List-Id: ------- Additional Comments From tromey at gcc dot gnu dot org 2005-08-23 14:15 ------- I see this too. Compiling with -fno-bounds-check helps, but not enough. One possibility is simply that our implementation of nextDouble is inefficient. I doubt this function was coded for maximum performance. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-08-23 14:15:25 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23283