From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by sourceware.org (Postfix) with ESMTP id 0D62E383642C for ; Tue, 22 Feb 2022 11:42:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0D62E383642C Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A5C57106F; Tue, 22 Feb 2022 03:42:34 -0800 (PST) Received: from [10.57.15.132] (unknown [10.57.15.132]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 0597C3F70D; Tue, 22 Feb 2022 03:42:33 -0800 (PST) Message-ID: Date: Tue, 22 Feb 2022 11:42:32 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Benchmark recommendations needed Content-Language: en-GB To: Andras Tantos , Gary Oblock , "gcc@gcc.gnu.org" References: <33a21357ddb10b187935cf4ea269bb5a7a800c1d.camel@tantosonline.com> From: Richard Earnshaw In-Reply-To: <33a21357ddb10b187935cf4ea269bb5a7a800c1d.camel@tantosonline.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3491.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2022 11:42:37 -0000 Dhrystone is (and probably always was) a bogus benchmark. It's a well-known truism that MIPS stands for Meaningless Indication of Processor Speed, and dhrystone scores are equally meaningless. Dhrystone fell out of common usage over 20 years ago. It's not GCC that is being peculiar, it's just Dhrystone is pointless. R. On 22/02/2022 05:22, Andras Tantos wrote: > That's true, I did notice GCC being rather ... peculiar about > drhystone. Is there a way to make it less clever about the benchmark? > > Or is there some alteration to the benchmark I can make to not trigger > the special behavior in GCC? > > Andras > > On Mon, 2022-02-21 at 03:19 +0000, Gary Oblock via Gcc wrote: >> Trying to use the dhrystone isn't going to be very useful. It has >> many downsides not the least is that gcc's optimizer can run rings >> about it. >> >> Gary >> >> ________________________________ >> From: Gcc on >> behalf of gcc-request@gcc.gnu.org >> Sent: Tuesday, February 15, 2022 6:25 AM >> To: gcc@gcc.gnu.org >> Subject: Re: >> >> [EXTERNAL EMAIL NOTICE: This email originated from an external >> sender. Please be mindful of safe email handling and proprietary >> information protection practices.] >> >> >> Send Gcc mailing list submissions to >> gcc@gcc.gnu.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://gcc.gnu.org/mailman/listinfo/gcc >> or, via email, send a message with subject or body 'help' to >> gcc-request@gcc.gnu.org >> >> You can reach the person managing the list at >> gcc-owner@gcc.gnu.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Gcc digest..." >