public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linux at carewolf dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/67351] New: Missed optimisation on 64-bit field compared to 32-bit
Date: Tue, 25 Aug 2015 15:38:00 -0000	[thread overview]
Message-ID: <bug-67351-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67351
           Summary: Missed optimisation on 64-bit field compared to 32-bit
           Product: gcc
           Version: 5.2.1
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: linux at carewolf dot com
  Target Milestone: ---

Created attachment 36253
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36253&action=edit
Test

Gcc will expand and detect field setting on 32-bit integers, but for some
reason miss the opportunity on 64-bit.

This was discovered as gcc was inexplicably slower compared to clang on the
64-bit case but not when using 32bit.


             reply	other threads:[~2015-08-25 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 15:38 linux at carewolf dot com [this message]
2015-08-25 15:39 ` [Bug middle-end/67351] " linux at carewolf dot com
2015-08-25 16:37 ` [Bug target/67351] " ubizjak at gmail dot com
2015-08-26  6:57 ` rguenth at gcc dot gnu.org
2015-09-01  9:00 ` [Bug tree-optimization/67351] " hs.naveen2u at gmail dot com
2015-09-03 10:20 ` naveenh at gcc dot gnu.org
2015-09-17 11:13 ` linux at carewolf dot com
2015-09-17 11:45 ` ubizjak 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-67351-4@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).