public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oremanj at get-linux dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/13344] New: Segmentation fault compiling xine-lib-1-rc2
Date: Sun, 07 Dec 2003 20:07:00 -0000 [thread overview]
Message-ID: <20031207200709.13344.oremanj@get-linux.org> (raw)
When compiling xine-lib-1-rc2, in the directory src/libffmpeg/libavcodec/i386, I
received the following error compiling dsputil_mmx.c:
> In file included from dsputil_mmx.c:22:
> ../dsputil.h:492: warning: static declaration for `lrintf' follows non-static
> ../dsputil.h: In function `lrintf':
> ../dsputil.h:499: internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
My gcc version is 3.2.1. I will be attaching preprocessed source in a comment to
this bug (there doesn't seem to be a file attach button on the main bug page).
--
Summary: Segmentation fault compiling xine-lib-1-rc2
Product: gcc
Version: 3.2.1
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: oremanj at get-linux dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i386-pc-linux-gnu
GCC host triplet: i386-pc-linux-gnu
GCC target triplet: i386-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13344
next reply other threads:[~2003-12-07 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 20:07 oremanj at get-linux dot org [this message]
2003-12-07 20:11 ` [Bug c/13344] " oremanj at get-linux dot org
2003-12-07 20:12 ` oremanj at get-linux dot org
2003-12-07 22:31 ` 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=20031207200709.13344.oremanj@get-linux.org \
--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).