public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: <andreas@florath.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: Re: c++/10060: ICE on huge file (300k lines)
Date: Mon, 12 May 2003 21:16:00 -0000	[thread overview]
Message-ID: <20030512211601.28958.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/10060; it has been noted by GNATS.

From: <andreas@florath.net>
To: giovannibajo@libero.it, andreas@florath.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: Re: c++/10060: ICE on huge file (300k lines)
Date: Tue,  6 May 2003 11:58:02 +0200

 Hello!
 
 	I just downloaded the latest gcc snapshot (gcc version 3.3
 20030428 (prerelease)).  When trying to compile the 100000 version,
 the error changed to
 
 > g++ -pipe -ggdb -o t t.cc
 {standard input}: Assembler messages:
 {standard input}:597943: Warning: end of file not at end of a line;
 newline inserted
 {standard input}:599806: Error: unknown pseudo-op: `.g'
 g++: Internal error: Segmentation Fault (program cc1plus)
 Please submit a full bug report.
 See <URL:http://gcc.gnu.org/bugs.html> for instructions.
 
 I'm now trying to figure out the smallest number when this error
 occurs: it's somewhat between 65536 (which compiles) and 100000 (which
 failes).  Please give me some time, because it takes some hours to
 compile.
 
 If you need some additional information (assembler output, core file
 :-) ...) feel free to ask. [Also one step I want to do is to check the
 size of the assembler output - maybe a problem with large files
 >4G????]
 
 	Best Regards
 
 	Andreas Florath
 	andreas@florath.net
 
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10060


                 reply	other threads:[~2003-05-12 21:16 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=20030512211601.28958.qmail@sources.redhat.com \
    --to=andreas@florath.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).