public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jdhall@uiuc.edu (Jesse Hall)
To: gcc-gnats@gcc.gnu.org
Subject: target/6624: SSE misalignment with -O0
Date: Fri, 10 May 2002 09:16:00 -0000	[thread overview]
Message-ID: <E176D0N-0000iq-00@12-221-64-141.client.insightbb.com> (raw)


>Number:         6624
>Category:       target
>Synopsis:       SSE mis-alignment with -O0
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri May 10 09:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Jesse Hall
>Release:        3.1 20020426 (prerelease)
>Organization:
>Environment:
System: Linux espresso 2.4.18-xfs #1 SMP Tue Mar 12 20:03:55 CST 2002 i686 unknown
Architecture: i686 (more precisely, dual AthlonMP)

        
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr/lib/gcc-snapshot --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux
>Description:
    The SSE intrinsic _mm_loadu_ps can do an aligned SSE load (LOADAPS) from
    an unaligned address when compiling with -O0. The problem seems to go away
    with -O1 and higher. This causes a segfault when the program is run. The
    assembly generated looks like:

        call   804834a <_mm_loadu_ps>
        add    $0x10,%esp
        movaps %xmm0,0xffffffe8(%ebp)

    On my machine, the movaps address is consistently not on a 16-byte
    boundary like it should be.

>How-To-Repeat:
    This simple program exhibits the problem on my machine:

    #include <xmmintrin.h>
    int main(int argc, char** argv) {
        __m128 x;
        float a[4] = {1.0f, 1.0f, 1.0f, 1.0f};
        x = _mm_loadu_ps(a);
        return 0;
    }

    Compiled with "gcc -g -O0 -msse foo.c -o foo".
    
>Fix:
    Compiling with -O1 or higher makes the problem go away, at least in the
    simple example above.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-10 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10  9:16 Jesse Hall [this message]
2002-05-10 10:56 Tim Prince

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=E176D0N-0000iq-00@12-221-64-141.client.insightbb.com \
    --to=jdhall@uiuc.edu \
    --cc=gcc-gnats@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).