From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15056 invoked by alias); 4 Nov 2002 15:46:10 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 14976 invoked by uid 71); 4 Nov 2002 15:46:08 -0000 Date: Mon, 04 Nov 2002 07:46:00 -0000 Message-ID: <20021104154608.14939.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Matthias Posseldt Subject: Re: c/4943: pointer address corruption in function call Reply-To: Matthias Posseldt X-SW-Source: 2002-11/txt/msg00157.txt.bz2 List-Id: The following reply was made to PR c/4943; it has been noted by GNATS. From: Matthias Posseldt To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, cbenna@iol.it Cc: Subject: Re: c/4943: pointer address corruption in function call Date: Mon, 4 Nov 2002 16:37:10 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4943 I have found this issue in GCC 3.2 release and have a simple 2kb testcase C file and compile parameter/output analysis. If anyone is interested I would like to share the knowledge I won about this bug. I could reproduce it with two linux (ver 2.4.19) gcc 3.2 (release) machines, one Athlon XP, one Pentium 3. Ciao, Matthias