public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: thyng2k@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: c/9720: segmentation fault compiling allegro
Date: Sun, 16 Feb 2003 21:46:00 -0000	[thread overview]
Message-ID: <20030216214216.10094.qmail@sources.redhat.com> (raw)


>Number:         9720
>Category:       c
>Synopsis:       segmentation fault compiling allegro
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 16 21:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     gcc
>Release:        gcc-3.2
>Organization:
>Environment:
Reading specs from C:/DEV-CPP/BIN/../lib/gcc-lib/mingw32/3.2/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=
mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable
-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared
Thread model: win32
gcc version 3.2 (mingw special 20020817-1)

Win98Se / Athlon XP 1800 / 192MB SDRAM / gforce MX400 / K7S5A MoBo .
>Description:
C:\Dev-Cpp\allegro>make
Compiling Allegro for MinGW32, optimised. Please wait...
gcc -DALLEGRO_SRC -Wall -Wno-unused -mcpu=pentium -O2 -funroll-loops -ffast-math
  -fomit-frame-pointer -fno-strength-reduce -I. -I./include -o obj/mingw32/alleg
/blit.o -c src/blit.c
src/blit.c: In function `dither_blit':
src/blit.c:358: 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.
C:\DEV-CPP\BIN\MAKE.EXE: *** [obj/mingw32/alleg/blit.o] Error 1
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2003-02-16 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 21:46 thyng2k [this message]
2003-02-16 22:07 ebotcazou
2003-05-14 21: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=20030216214216.10094.qmail@sources.redhat.com \
    --to=thyng2k@hotmail.com \
    --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).