public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50875] O3 and -mavx lead to internal compiler error: in find_reloads
Date: Thu, 27 Oct 2011 21:55:00 -0000	[thread overview]
Message-ID: <bug-50875-4-uWJvaR8w3k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50875-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from uros at gcc dot gnu.org 2011-10-27 21:55:26 UTC ---
Author: uros
Date: Thu Oct 27 21:55:22 2011
New Revision: 180582

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180582
Log:
    PR target/50875
    * config/i386/sse.md (*avx_unpcklpd256): Remove extra insn
    constraints.  Change alternative 1 to "x,m,1".

testsuitee/ChangeLog:

    PR target/50875
    * gfortran.dg/pr50875.f90: New test.


Added:
    branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/pr50875.f90
Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/config/i386/sse.md
    branches/gcc-4_6-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-10-27 21:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 15:43 [Bug fortran/50875] New: O3 and -march=native " holyjoly at gmail dot com
2011-10-26 15:54 ` [Bug fortran/50875] " xunxun1982 at gmail dot com
2011-10-26 16:08 ` holyjoly at gmail dot com
2011-10-26 16:35 ` xunxun1982 at gmail dot com
2011-10-26 18:03 ` holyjoly at gmail dot com
2011-10-26 18:10 ` holyjoly at gmail dot com
2011-10-26 22:53 ` [Bug target/50875] O3 and -mavx " ubizjak at gmail dot com
2011-10-27 19:07 ` uros at gcc dot gnu.org
2011-10-27 21:55 ` uros at gcc dot gnu.org [this message]
2011-10-30 10:31 ` uros at gcc dot gnu.org
2011-10-30 11:35 ` 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-50875-4-uWJvaR8w3k@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).