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 testsuite/59442] movapd tests fail if built with -fstack-protector-strong/all
Date: Thu, 12 Dec 2013 07:53:00 -0000	[thread overview]
Message-ID: <bug-59442-4-oqR0dlrW2x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59442-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu Dec 12 07:53:33 2013
New Revision: 205920

URL: http://gcc.gnu.org/viewcvs?rev=205920&root=gcc&view=rev
Log:
    Backport from mainline
    2013-12-12  Ryan Mansfield  <rmansfield@qnx.com>

    PR testsuite/59442
    * gcc.target/i386/sse2-movapd-1.c: Fix alignment attributes.
    * gcc.target/i386/sse2-movapd-2.c: Likewise.
    * gcc.target/i386/avx-vmovapd-256-1.c: Likewise.
    * gcc.target/i386/avx-vmovapd-256-2.c: Likewise.


Modified:
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/avx-vmovapd-256-1.c
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/avx-vmovapd-256-2.c
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/sse2-movapd-1.c
    branches/gcc-4_8-branch/gcc/testsuite/gcc.target/i386/sse2-movapd-2.c


  parent reply	other threads:[~2013-12-12  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  1:06 [Bug testsuite/59442] New: " rmansfield at qnx dot com
2013-12-10  9:29 ` [Bug testsuite/59442] " ubizjak at gmail dot com
2013-12-12  7:49 ` uros at gcc dot gnu.org
2013-12-12  7:53 ` uros at gcc dot gnu.org [this message]
2013-12-12  8:00 ` uros at gcc dot gnu.org
2013-12-12  8:09 ` 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-59442-4-oqR0dlrW2x@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).