public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59539] Missed optimisation: VEX-prefixed operations don't need aligned data
Date: Wed, 18 Dec 2013 11:04:00 -0000	[thread overview]
Message-ID: <bug-59539-4-8dXn9R3YxA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59539-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2880 bytes --]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59539

--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #8)
> Because otherwise it can generate an aligned load, and I thought when user
> explicitly writes he wants an unaligned load we should honor it, perhaps for
> some reason the alignment info can't be trusted etc.
> ix86_expand_vector_move_misalign also checks misaligned_operand and only
> emits
> the non-UNSPEC insn for TARGET_AVX if it will result in misaligned load.

Thanks, the patch looks OK then (perhaps with the comment on misaligned_operand
usage).
>From gcc-bugs-return-437983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 18 11:05:30 2013
Return-Path: <gcc-bugs-return-437983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25419 invoked by alias); 18 Dec 2013 11:05:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25370 invoked by uid 48); 18 Dec 2013 11:05:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/58668] [4.8/4.9 regression] internal compiler error: in cond_exec_process_insns, at ifcvt.c:339
Date: Wed, 18 Dec 2013 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-58668-4-FyWcdGq4a5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-12/txt/msg01638.txt.bz2
Content-length: 405

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX668

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 31466
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id1466&actioníit
gcc49-pr58668.patch

So like this?  Note, the USE/CLOBBER change for flow_find_cross_jump
has been added in 2011 for 4.7 as PR43920 fix:
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg02246.html


  parent reply	other threads:[~2013-12-18 11:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  0:50 [Bug target/59539] New: " thiago at kde dot org
2013-12-18  8:33 ` [Bug target/59539] " jakub at gcc dot gnu.org
2013-12-18  8:49 ` thiago at kde dot org
2013-12-18  9:38 ` ubizjak at gmail dot com
2013-12-18  9:43 ` jakub at gcc dot gnu.org
2013-12-18  9:50 ` ubizjak at gmail dot com
2013-12-18 10:18 ` jakub at gcc dot gnu.org
2013-12-18 10:39 ` ubizjak at gmail dot com
2013-12-18 11:04 ` ubizjak at gmail dot com [this message]
2013-12-18 16:50 ` jakub at gcc dot gnu.org
2013-12-18 16:52 ` jakub at gcc dot gnu.org
2013-12-18 17:36 ` thiago at kde dot org
2013-12-19  0:07 ` thiago at kde dot org
2013-12-19  0:14 ` thiago at kde dot 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-59539-4-8dXn9R3YxA@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).