public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ian Ollmann <iano@cco.caltech.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8049: SSE unaligned vector stores crash with -O0
Date: Thu, 10 Oct 2002 10:56:00 -0000	[thread overview]
Message-ID: <20021010175601.31718.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8049; it has been noted by GNATS.

From: Ian Ollmann <iano@cco.caltech.edu>
To: Jan Hubicka <jh@suse.cz>
Cc: hubicka@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
        <gcc-gnats@gcc.gnu.org>
Subject: Re: optimization/8049: SSE unaligned vector stores crash with -O0
Date: Thu, 10 Oct 2002 10:54:51 -0700

 On Thu, 10 Oct 2002, Jan Hubicka wrote:
 
 > > On 10 Oct 2002 hubicka@gcc.gnu.org wrote:
 > >
 > > > Synopsis: SSE unaligned vector stores crash with -O0
 > > >
 > > > State-Changed-From-To: open->closed
 > > > State-Changed-By: hubicka
 > > > State-Changed-When: Thu Oct 10 09:45:59 2002
 > > > State-Changed-Why:
 > > >     It is runtime bug to not align stack properly for main.
 > > >     It will go away with runtime compiled using gcc 3.2 or can be workarounded by avoiding vector stuff in main.
 > > >
 > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8049
 > >
 > > I see this in functions that are not main(). Didn't I provide an example
 > > of one?
 >
 > I didn't see it.  Can you send me some?
 
 The original example is one.  The three buffers passed into MatrixMultiply
 happen to be aligned on my system. The actual crash happens when the stack
 copy of C1 is loaded, before the _mm_store_ps (uninlined) function is
 called.
 
 Ian
 
 ---------------------------------------------------
    Ian Ollmann, Ph.D.       iano@cco.caltech.edu
 ---------------------------------------------------
 


             reply	other threads:[~2002-10-10 17:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 10:56 Ian Ollmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-08 13:14 hubicka
2002-10-11 12:41 hubicka
2002-10-11  2:36 Jan Hubicka
2002-10-10 18:06 Ian Ollmann
2002-10-10 17:46 Ian Ollmann
2002-10-10 12:46 Ian Ollmann
2002-10-10 12:26 Jan Hubicka
2002-10-10 12:16 Ian Ollmann
2002-10-10 11:06 Jan Hubicka
2002-10-10 10:56 Jan Hubicka
2002-10-10 10:46 Ian Ollmann
2002-10-10  9:46 hubicka
2002-09-25 20:16 Tim Prince
2002-09-25 16:06 iano

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=20021010175601.31718.qmail@sources.redhat.com \
    --to=iano@cco.caltech.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).