public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Gary Thomas <g.thomas@opengroup.org>
Cc: egcs@cygnus.com, Michael Meissner <meissner@cygnus.com>,
	David Edelsohn <dje@watson.ibm.com>
Subject: Re: Another code generation bug in EGCS-1.0.1
Date: Mon, 09 Feb 1998 01:07:00 -0000	[thread overview]
Message-ID: <5517.887015036@hurl.cygnus.com> (raw)
In-Reply-To: <XFMail.980208101002.g.thomas@opengroup.org>

  In message < XFMail.980208101002.g.thomas@opengroup.org >you write:
  > Content-Type: text/plain; charset=us-ascii
  > 
  > EGCS-1.0.1 (and GCC-2.8.0) can generate bad code when configured
  > for PowerPC and SYSV4-ABI (Linux/PPC).  In this configuration, the
  > stack is managed differently when varargs are present (a stack space
  > optimization).  However, for inlined functions that end up not
  > generated inline and nested functions, this optimization is lost and
  > the generated functions generate incorrect preamble code which will
  > destroy the runtime stack.
  > 
  > Code exists in the current version to try and address this for the nested
  > functions case, but it was a little wrong (patch to "function.c").  Also,
  > the case of inline functions was not present at all.
  > 
  > A patch is attached which solves both problems.
Can you please send a testcase which exposes this problem?

Thanks,
jeff

  reply	other threads:[~1998-02-09  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-08  1:02 Gary Thomas
1998-02-09  1:07 ` Jeffrey A Law [this message]
1998-02-09  2:14   ` Gary Thomas

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=5517.887015036@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=dje@watson.ibm.com \
    --cc=egcs@cygnus.com \
    --cc=g.thomas@opengroup.org \
    --cc=meissner@cygnus.com \
    /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).