public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/61333] potential target specific performance issue with libgomp
Date: Wed, 28 May 2014 13:02:00 -0000	[thread overview]
Message-ID: <bug-61333-4-Eu3CuB6FQX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61333-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61333

--- Comment #11 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
(In reply to Jakub Jelinek from comment #10)

> Also, benchmarking -O0 code is weird.

Is gcc really optimizing that low by default? Certainly it is at least doing
-O1 when not passed a -O* optimization flag? In any case, shouldn't the
optimization be somewhat orthogonal to this problem since, by normalizing to
the one process timing, we are just looking at the effect of the overhead in
the processes?


  parent reply	other threads:[~2014-05-28 13:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 23:58 [Bug libgomp/61333] New: " howarth.at.gcc at gmail dot com
2014-05-27 23:58 ` [Bug libgomp/61333] " howarth.at.gcc at gmail dot com
2014-05-27 23:59 ` howarth.at.gcc at gmail dot com
2014-05-28  0:04 ` howarth.at.gcc at gmail dot com
2014-05-28  0:18 ` pinskia at gcc dot gnu.org
2014-05-28  0:35 ` howarth.at.gcc at gmail dot com
2014-05-28  0:52 ` howarth.at.gcc at gmail dot com
2014-05-28  0:57 ` pinskia at gcc dot gnu.org
2014-05-28  9:49 ` dominiq at lps dot ens.fr
2014-05-28  9:59 ` dominiq at lps dot ens.fr
2014-05-28 10:10 ` jakub at gcc dot gnu.org
2014-05-28 13:02 ` howarth.at.gcc at gmail dot com [this message]
2014-05-28 13:36 ` dominiq at lps dot ens.fr
2014-05-28 15:14 ` howarth.at.gcc at gmail dot com
2014-05-28 17:30 ` howarth.at.gcc at gmail dot com

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-61333-4-Eu3CuB6FQX@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: link
Be 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).