public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dylan@q-games.com
To: gcc-gnats@gcc.gnu.org
Cc: aj@suse.de, rth@redhat.com
Subject: c++/6144: segment-faults when using sse extensions and ia32 g++
Date: Tue, 02 Apr 2002 17:46:00 -0000	[thread overview]
Message-ID: <20020403014355.4108.qmail@sources.redhat.com> (raw)


>Number:         6144
>Category:       c++
>Synopsis:       segment-faults when using sse extensions and ia32 g++
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 02 17:46:21 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Dylan Cuthbert (dylan@q-games.com)
>Release:        3.1 (25th March 2002 snapshot)
>Organization:
>Environment:
cygwin 1.3.9, windows 2000, Athlon MP (2 processor) 1.2Ghz (problem occurs also on Pentium IV machines)
>Description:
A simplified piece of code to demonstrate SSE 16 byte values not being stack-aligned correctly in certain cases.  The main problem appears to be when they are encapsulated in another class (like a matrix) and then referenced individually in an expression.  This makes use of the SSE extensions unreliable and, in effect, unusable so I think the priority should be high.
>How-To-Repeat:
compile and run the attached code on Pentium IV or Athlon 4. MP or XP chipset.
>Fix:
Unknown
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-03  1:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 17:46 dylan [this message]
2002-04-02 23:36 Dylan Cuthbert
2002-04-03 10:06 Tim Prince
2002-04-03 17:16 Dylan Cuthbert
2002-12-12  7:38 bangerth
2003-05-08 23:13 bangerth

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=20020403014355.4108.qmail@sources.redhat.com \
    --to=dylan@q-games.com \
    --cc=aj@suse.de \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=rth@redhat.com \
    /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).