public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/9720: segmentation fault compiling allegro
@ 2003-05-14 21:13 bangerth
  0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2003-05-14 21:13 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, nobody, thyng2k

Synopsis: segmentation fault compiling allegro

State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Wed May 14 21:13:17 2003
State-Changed-Why:
    No feedback. This should bring us now to less than 1600 PRs. Whee (as Jeff would say :-)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9720


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c/9720: segmentation fault compiling allegro
@ 2003-02-16 22:07 ebotcazou
  0 siblings, 0 replies; 3+ messages in thread
From: ebotcazou @ 2003-02-16 22:07 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, nobody, thyng2k

Synopsis: segmentation fault compiling allegro

State-Changed-From-To: open->feedback
State-Changed-By: ebotcazou
State-Changed-When: Sun Feb 16 22:07:37 2003
State-Changed-Why:
    Is the problem reproducible, i.e does the compiler crash at
    the very same point if you restart the build? I experienced
    this sort of problem while building Allegro with the same
    configuration as yours on one box, but had no problems at
    all on another one.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9720


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c/9720: segmentation fault compiling allegro
@ 2003-02-16 21:46 thyng2k
  0 siblings, 0 replies; 3+ messages in thread
From: thyng2k @ 2003-02-16 21:46 UTC (permalink / raw)
  To: gcc-gnats


>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:


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-05-14 21:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-14 21:13 c/9720: segmentation fault compiling allegro bangerth
  -- strict thread matches above, loose matches on Subject: below --
2003-02-16 22:07 ebotcazou
2003-02-16 21:46 thyng2k

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).