public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "t.artem at mailcity dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/54073] SciMark Monte Carlo test performance has seriously decreased in recent GCC releases Date: Mon, 23 Jul 2012 15:44:00 -0000 [thread overview] Message-ID: <bug-54073-4-89NJU3XDOV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54073-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54073 --- Comment #1 from Artem S. Tashkinov <t.artem at mailcity dot com> 2012-07-23 15:43:50 UTC --- The results are obtained from here: http://openbenchmarking.org/result/1207077-SU-GCCPERFOR59 Benchmarking of GCC 4.2 through GCC 4.8 when building the compiler the same and setting CFLAGS/CXXFLAGS of -O3 and -march=native prior to test installation and execution. Benchmarking for a future article on Phoronix.com by Michael Larabel. Testing on an Intel Core i7 and AMD Opteron 2384 when using the 64-bit (x86_64 target) build of Ubuntu Linux. The CPU is: Nehalem microarchitecture, "Clarksfield" (45 nm), Intel® Core™ i7-720QM Processor (6M Cache, 1.60 GHz) http://ark.intel.com/products/43122/Intel-Core-i7-720QM-Processor-%286M-Cache-1_60-GHz%29
next prev parent reply other threads:[~2012-07-23 15:44 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-23 15:25 [Bug tree-optimization/54073] New: " t.artem at mailcity dot com 2012-07-23 15:44 ` t.artem at mailcity dot com [this message] 2012-07-24 9:23 ` [Bug tree-optimization/54073] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2012-07-24 11:29 ` markus at trippelsdorf dot de 2012-07-24 13:21 ` rguenth at gcc dot gnu.org 2012-07-26 15:41 ` venkataramanan.kumar at amd dot com 2012-07-26 16:13 ` markus at trippelsdorf dot de 2012-08-16 11:06 ` rguenth at gcc dot gnu.org 2012-09-07 10:09 ` rguenth at gcc dot gnu.org 2012-09-20 10:28 ` jakub at gcc dot gnu.org 2012-11-13 13:05 ` jakub at gcc dot gnu.org 2012-11-13 15:07 ` t.artem at mailcity dot com 2012-11-13 15:14 ` ubizjak at gmail dot com 2012-11-13 15:24 ` jakub at gcc dot gnu.org 2012-11-13 15:55 ` hubicka at gcc dot gnu.org 2012-11-16 11:41 ` jakub at gcc dot gnu.org 2012-11-16 14:50 ` [Bug tree-optimization/54073] [4.7 " jakub at gcc dot gnu.org 2012-12-31 9:41 ` pinskia at gcc dot gnu.org 2013-02-16 19:12 ` jake.stine at gmail dot com 2013-02-17 8:41 ` ubizjak at gmail dot com 2013-04-11 7:59 ` rguenth at gcc dot gnu.org 2014-06-12 13:16 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-54073-4-89NJU3XDOV@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).