public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59797] New: GCC doesn't warn AVX-512 ABI change
Date: Mon, 13 Jan 2014 22:23:00 -0000	[thread overview]
Message-ID: <bug-59797-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59797
           Summary: GCC doesn't warn AVX-512 ABI change
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: kirill.yukhin at intel dot com

[hjl@gnu-6 gcc]$ cat /tmp/z.i
typedef long long __m512i __attribute__ ((__vector_size__ (64),
__may_alias__));

__m512i
f1(__m512i x, __m512i y)
{
  return y;
}
[hjl@gnu-6 gcc]$ ./xgcc -B./ -S -O /tmp/z.i
/tmp/z.i: In function ‘f1’:
/tmp/z.i:4:1: note: The ABI for passing parameters with 64-byte alignment has
changed in GCC 4.6
 f1(__m512i x, __m512i y)
 ^
[hjl@gnu-6 gcc]$ ./xgcc -B./ -S -O /tmp/z.i -mavx512f
[hjl@gnu-6 gcc]$ 

When -mavx512f isn't used, GCC should warn ABI changes for passing/returning
AVX vector values.
>From gcc-bugs-return-440265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 13 22:23:42 2014
Return-Path: <gcc-bugs-return-440265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19299 invoked by alias); 13 Jan 2014 22:23:42 -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 19280 invoked by uid 48); 13 Jan 2014 22:23:38 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59797] GCC doesn't warn AVX-512 ABI change
Date: Mon, 13 Jan 2014 22:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-59797-4-GOHUDAHeIB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59797-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: 2014-01/txt/msg01407.txt.bz2
Content-length: 450

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-13
   Target Milestone|---                         |4.9.0
     Ever confirmed|0                           |1


             reply	other threads:[~2014-01-13 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 22:23 hjl.tools at gmail dot com [this message]
2014-01-14  6:29 ` [Bug target/59797] " kirill.yukhin at intel dot com
2014-01-14 13:00 ` hjl.tools at gmail dot com
2014-02-19 16:55 ` 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-59797-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).