public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ncm at cantrip dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67153] [5/6 Regression] integer optimizations 53% slower than std::bitset<>
Date: Thu, 13 Aug 2015 01:49:00 -0000	[thread overview]
Message-ID: <bug-67153-4-KbZaQcyOyS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67153-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from ncm at cantrip dot org ---
I found this, which at first blush seems like it might be relevant.
The hardware complained about here is the same Haswell i7-4770.

http://stackoverflow.com/questions/25078285/replacing-a-32-bit-loop-count-variable-with-64-bit-introduces-crazy-performance


  parent reply	other threads:[~2015-08-13  1:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-67153-4@http.gcc.gnu.org/bugzilla/>
2015-08-07 23:55 ` [Bug c++/67153] " ncm at cantrip dot org
2015-08-08  5:03 ` ncm at cantrip dot org
2015-08-08  5:23 ` [Bug tree-optimization/67153] [5/6 Regression] " rguenth at gcc dot gnu.org
2015-08-10  2:37 ` ncm at cantrip dot org
2015-08-10 11:47 ` ncm at cantrip dot org
2015-08-11 17:39 ` ncm at cantrip dot org
2015-08-11 18:17 ` ubizjak at gmail dot com
2015-08-13  0:32 ` ncm at cantrip dot org
2015-08-13  1:49 ` ncm at cantrip dot org [this message]
2015-08-13  2:24 ` ncm at cantrip dot org
2015-08-13 14:32 ` ncm at cantrip dot org
2015-08-17  3:06 ` miyuki at gcc dot gnu.org
2021-05-14  9:47 ` [Bug tree-optimization/67153] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug tree-optimization/67153] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug tree-optimization/67153] [11/12/13/14 " 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-67153-4-KbZaQcyOyS@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).