public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: falk@whoi.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c/6197: gcc3.0.3 error: it says:Internal compiler error in subst_stack_regs_pat, at reg-stack.c:1397
Date: Sun, 07 Apr 2002 18:38:00 -0000	[thread overview]
Message-ID: <20020408013851.15381.qmail@sources.redhat.com> (raw)

Synopsis: gcc3.0.3 error: it says:Internal compiler error in subst_stack_regs_pat, at reg-stack.c:1397

State-Changed-From-To: open->analyzed
State-Changed-By: rodrigc
State-Changed-When: Sun Apr  7 18:38:51 2002
State-Changed-Why:
    Problem reproduced.
    Compiling with -Wall yields many warnings:
    
    sediment.c: In function `sediment_fall_velocity':
    sediment.c:72: warning: implicit declaration of function `sqrt'
    sediment.c:75: warning: implicit declaration of function `printf'
    sediment.c:79: warning: no return statement in function returning non-void
    sediment.c: In function `rhs_sediment_eq':
    sediment.c:125: warning: left-hand operand of comma expression has no
    effect
    sediment.c: In function `update_sediment_bc':
    sediment.c:155: warning: unused variable `kvtop'
    sediment.c: In function `sediment_fall_velocity':
    sediment.c:79: warning: control reaches end of non-void function
    sediment.c:79: Internal compiler error in subst_stack_regs_pat, at reg-stack.c:1441
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

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


             reply	other threads:[~2002-04-08  1:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-07 18:38 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-05 16:16 falk

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=20020408013851.15381.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=falk@whoi.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).