public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5040: g++-3.0.2: -O causes variables from different stack frames to overlap
Date: Mon, 08 Apr 2002 13:06:00 -0000	[thread overview]
Message-ID: <20020408200601.25329.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5040; it has been noted by GNATS.

From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: rth@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gcc-bugs@gcc.gnu.org, jeremy.barnes@idilia.com
Cc:  
Subject: Re: optimization/5040: g++-3.0.2: -O causes variables from different stack frames to overlap
Date: Mon, 8 Apr 2002 22:00:57 +0000

 Hi,
 
 Yes, please send me your testcase. I have a few comments so far.
 
 - Your report is against gcc3.0-c++-3.0.2-1mdk under Mandrake Linux 8.1. This 
 is odd as we never provided any gcc-3.0.2 in any x86 distribution. Mixing 
 Cooker packages and stable packages is generally not a good idea. Or have you 
 upgraded to Cooker or MDK 8.2 since ?
 
 - 3.0.2-1mdk is mainly based on RH-3.0.1 release 4. I would have expected 
 problems with later releases such as 3.0.3-0.1mdk with several other patches 
 coming in. But your original test case does work gcc-3.0.4.
 
 - 3.1-0.2mdk is a prerelease snapshot as of 2002/04/01 plus the following 
 patches from Red Hat: compat with older 2.96-RH and binutils, and backport of 
 the visibility attribute.
 
 Bye,
 Gwenole.


             reply	other threads:[~2002-04-08 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 13:06 Gwenole Beauchesne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  7:46 Gwenole Beauchesne
2002-04-08 13:06 Richard Henderson
2002-04-08 12:26 Jeremy Barnes
2002-04-03 17:20 rth
2002-04-03 14:09 rth
2002-04-03 10:36 Richard Henderson
2002-04-03  8:26 Jeremy Barnes
2002-04-03  1:41 rth
2001-12-06 13:36 jeremy.barnes

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=20020408200601.25329.qmail@sources.redhat.com \
    --to=gbeauchesne@mandrakesoft.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rth@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).