public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57777] Python module fails compilation with "-march=core-avx2 -O3"
Date: Tue, 02 Jul 2013 17:41:00 -0000	[thread overview]
Message-ID: <bug-57777-4-dYTryysszt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57777-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase for -O3 -mavx2 -fpic:
void
foo (unsigned long *x, int *y)
{
  static unsigned long b[2] = { 0x0UL, 0x9908b0dfUL };
  int c;
  for (c = 0; c < 512; c++)
    x[c] = b[x[c] & 1UL];
}


  parent reply	other threads:[~2013-07-02 17:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-57777-4@http.gcc.gnu.org/bugzilla/>
2013-07-02 11:23 ` [Bug c/57777] " dirkjan at ochtman dot nl
2013-07-02 11:43 ` redi at gcc dot gnu.org
2013-07-02 12:33 ` julian.ospald at googlemail dot com
2013-07-02 15:41 ` hjl.tools at gmail dot com
2013-07-02 17:41 ` jakub at gcc dot gnu.org [this message]
2013-07-02 18:49 ` [Bug target/57777] [4.7/4.8/4.9 Regression] " jakub at gcc dot gnu.org
2013-07-02 18:50 ` jakub at gcc dot gnu.org
2013-07-02 21:16 ` julian.ospald at googlemail dot com
2013-07-02 21:37 ` julian.ospald at googlemail dot com
2013-07-03 13:49 ` julian.ospald at googlemail dot com
2013-07-03 20:30 ` [Bug target/57777] [4.7 " jakub at gcc dot gnu.org
2013-08-10 18:47 ` lbbsome9 at gmail dot com
2014-05-07 16:00 ` jakub at gcc dot gnu.org
2014-05-07 16:18 ` jakub 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-57777-4-dYTryysszt@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).