public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39258]  New: No ABI warnings on __m128i  when SSE is disabled
Date: Sat, 21 Feb 2009 17:28:00 -0000	[thread overview]
Message-ID: <bug-39258-682@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

bash-3.2$ cat /tmp/u1.i 
typedef long long __m128i __attribute__ ((__vector_size__ (16),
__may_alias__)); 

union sse2
{
  float i;
  __m128i x;
};

void foo2 (union sse2);

void
bar2 (union sse2 x)
{
  foo2 (x);
}
bash-3.2$ gcc  -S -O2 /tmp/u1.i -mno-sse
bash-3.2$ gcc  -S -O2 /tmp/u1.i -mno-sse -m32
bash-3.2$ cat /tmp/u2.i
typedef long long __m128i __attribute__ ((__vector_size__ (16),
__may_alias__)); 

void foo2 (__m128i);

void
bar2 (__m128i y, __m128i x)
{
  foo2 (x);
}
bash-3.2$ gcc  -S -O2 /tmp/u2.i -mno-sse

I am expecting a warning here, like

bash-3.2$ gcc  -S -O2 /tmp/u2.i -mno-sse -m32
/tmp/u2.i: In function ‘bar2’:
/tmp/u2.i:7: warning: SSE vector argument without SSE enabled changes the ABI
bash-3.2$


-- 
           Summary: No ABI warnings on __m128i  when SSE is disabled
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl dot tools at gmail dot com


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


             reply	other threads:[~2009-02-21 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 17:28 hjl dot tools at gmail dot com [this message]
2009-02-22 19:21 ` [Bug target/39258] " hjl dot tools at gmail dot com
2009-02-22 22:04 ` hjl dot tools at gmail dot com
2009-04-16 18:33 ` pinskia at gcc dot gnu 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-39258-682@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).