public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rearnsha@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rhofmann@rayed.de
Subject: Re: c++/9205: GCC3.2 arm prolog stack frame use before allocation with -Os
Date: Tue, 07 Jan 2003 10:44:00 -0000	[thread overview]
Message-ID: <20030107104451.22101.qmail@sources.redhat.com> (raw)

Synopsis: GCC3.2 arm prolog stack frame use before allocation with -Os

State-Changed-From-To: open->feedback
State-Changed-By: rearnsha
State-Changed-When: Tue Jan  7 02:44:50 2003
State-Changed-Why:
    Please can you try the patch mentioned in the following message and let me know if it solves the problem:
    http://gcc.gnu.org/ml/gcc-patches/2002-07/msg00787.html

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


             reply	other threads:[~2003-01-07 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 10:44 rearnsha [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  7:52 giovannibajo
2003-01-06 22:56 rhofmann

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=20030107104451.22101.qmail@sources.redhat.com \
    --to=rearnsha@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=rhofmann@rayed.de \
    /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).