public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Posseldt <matthi@gmx.li>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/4943: pointer address corruption in function call
Date: Mon, 04 Nov 2002 07:46:00 -0000	[thread overview]
Message-ID: <20021104154608.14939.qmail@sources.redhat.com> (raw)

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

From: Matthias Posseldt <matthi@gmx.li>
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
 
 


             reply	other threads:[~2002-11-04 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  7:46 Matthias Posseldt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-04 10:56 bangerth
2001-11-20 17:54 cbenna

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=20021104154608.14939.qmail@sources.redhat.com \
    --to=matthi@gmx.li \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).