public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	tau@logos.t.u-tokyo.ac.jp
Subject: Re: c/7026: compiler dies with "internal compiler error"
Date: Fri, 14 Jun 2002 01:46:00 -0000	[thread overview]
Message-ID: <20020614054942.20327.qmail@sources.redhat.com> (raw)

Synopsis: compiler dies with "internal compiler error"

State-Changed-From-To: open->closed
State-Changed-By: davem
State-Changed-When: Thu Jun 13 22:49:41 2002
State-Changed-Why:
    Flat stack frames are unsupported with the v9 abi.
    The bug is that the compiler allows this combination
    of flags, it was never intended to be supported.
    In fact we intend to remove flat frame support in
    the Sparc backend by the time 3.2 is released.

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


                 reply	other threads:[~2002-06-14  5:49 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=20020614054942.20327.qmail@sources.redhat.com \
    --to=davem@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=tau@logos.t.u-tokyo.ac.jp \
    /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).