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 <gcc-bounces+gary=amperecomputing....@gcc.gnu.org> on > behalf of gcc-requ...@gcc.gnu.org <gcc-requ...@gcc.gnu.org> > Sent: Tuesday, February 15, 2022 6:25 AM > To: gcc@gcc.gnu.org <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-requ...@gcc.gnu.org > > You can reach the person managing the list at > gcc-ow...@gcc.gnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gcc digest..."
