public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/3687: GCC 3.0 error
@ 2001-12-02 15:55 rodrigc
0 siblings, 0 replies; 4+ messages in thread
From: rodrigc @ 2001-12-02 15:55 UTC (permalink / raw)
To: LiquidPC, gcc-bugs, gcc-gnats, gcc-prs, nobody, rodrigc
Synopsis: GCC 3.0 error
State-Changed-From-To: feedback->closed
State-Changed-By: rodrigc
State-Changed-When: Sun Dec 2 15:55:22 2001
State-Changed-Why:
No feedback.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3687&database=gcc
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c/3687: GCC 3.0 error
@ 2001-12-02 15:56 rodrigc
0 siblings, 0 replies; 4+ messages in thread
From: rodrigc @ 2001-12-02 15:56 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c/3687; it has been noted by GNATS.
From: rodrigc@gcc.gnu.org
To: LiquidPC@LiquidPC.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org
Cc:
Subject: Re: c/3687: GCC 3.0 error
Date: 2 Dec 2001 23:55:22 -0000
Synopsis: GCC 3.0 error
State-Changed-From-To: feedback->closed
State-Changed-By: rodrigc
State-Changed-When: Sun Dec 2 15:55:22 2001
State-Changed-Why:
No feedback.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3687&database=gcc
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: c/3687: GCC 3.0 error
@ 2001-09-08 11:01 rodrigc
0 siblings, 0 replies; 4+ messages in thread
From: rodrigc @ 2001-09-08 11:01 UTC (permalink / raw)
To: LiquidPC, gcc-bugs, gcc-prs, nobody, rodrigc
Synopsis: GCC 3.0 error
State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Sat Sep 8 11:01:53 2001
State-Changed-Why:
Your bug does not contain preprocessed source.
Can you submit preprocessed source code for your problem,
as described in http://gcc.gnu.org/bugs.html
Also, can you try gcc 3.0.1 and see if the problem is
fixed in that version?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3687&database=gcc
^ permalink raw reply [flat|nested] 4+ messages in thread
* c/3687: GCC 3.0 error
@ 2001-07-14 8:36 LiquidPC
0 siblings, 0 replies; 4+ messages in thread
From: LiquidPC @ 2001-07-14 8:36 UTC (permalink / raw)
To: gcc-gnats
>Number: 3687
>Category: c
>Synopsis: GCC 3.0 error
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Sat Jul 14 08:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: LiquidPC
>Release: Configured with: ../gcc-3.0/configure --prefix=/usr --enable-shared --with-gnu-ld --enable-threads --verbose --target=i386-slackware-linux --host=i386-slackware-linux
>Organization:
>Environment:
AMD k5 116mhz 20 MB RAM, Slackware Linux 8.0
>Description:
make[3]: Entering directory /usr/src/linux/drivers/pci'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i586 -c -o names.o names.c
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions.
{standard input}: Assembler messages:
{standard input}:14117: Warning: end of file in string: inserted '"'
make[3]: *** [names.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [_subdir_pci] Error 2
make: *** [_dir_drivers] Error 2
>How-To-Repeat:
>Fix:
none.
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-12-02 23:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-02 15:55 c/3687: GCC 3.0 error rodrigc
-- strict thread matches above, loose matches on Subject: below --
2001-12-02 15:56 rodrigc
2001-09-08 11:01 rodrigc
2001-07-14 8:36 LiquidPC
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).