public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wittman@acm.org
To: gcc-gnats@gcc.gnu.org
Subject: target/9844: Segmentation fault using operator function with intrinsics
Date: Tue, 25 Feb 2003 05:26:00 -0000	[thread overview]
Message-ID: <20030225052439.1961.qmail@sources.redhat.com> (raw)


>Number:         9844
>Category:       target
>Synopsis:       Segmentation fault using operator function with intrinsics
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 25 05:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Michael Wittman
>Release:        gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
>Organization:
>Environment:
host:
Linux texel.localdomain 2.4.18-24.8.0 #1 Fri Jan 31 07:28:55 EST 2003 i686 athlon i386 GNU/Linux

gcc:
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit
Thread model: posix
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)

>Description:
Compiling the following code that attempts to mix intrinsics with an operator function causes g++ to crash with a segmentation fault:

class v8qi
{
   operator int __attribute__ ((mode(V8QI))) () { }
};


% g++ -mmmx -march=athlon test.cpp
test.cpp:3: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.

Note that the -mmmx and -march=athlon options are not required for it to crash.
>How-To-Repeat:
Compile with the command line described.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-02-25  5:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030225052439.1961.qmail@sources.redhat.com \
    --to=wittman@acm.org \
    --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).