public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dann at godzilla dot ics dot uci dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/23872] .t02.original dump weirdness
Date: Tue, 13 Sep 2005 20:45:00 -0000 [thread overview]
Message-ID: <20050913204529.9369.qmail@sourceware.org> (raw)
In-Reply-To: <20050913202428.23872.dann@godzilla.ics.uci.edu>
------- Additional Comments From dann at godzilla dot ics dot uci dot edu 2005-09-13 20:45 -------
The fact that the dump is different depending on function order or compilation
flags seems to point to either an uninitialized variable or some memory corruption.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23872
next prev parent reply other threads:[~2005-09-13 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 20:24 [Bug middle-end/23872] New: " dann at godzilla dot ics dot uci dot edu
2005-09-13 20:28 ` [Bug c/23872] " pinskia at gcc dot gnu dot org
2005-09-13 20:45 ` dann at godzilla dot ics dot uci dot edu [this message]
[not found] <bug-23872-1008@http.gcc.gnu.org/bugzilla/>
2005-12-28 6:04 ` pinskia at gcc dot gnu dot org
2007-08-16 14:40 ` manu at gcc dot gnu dot org
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=20050913204529.9369.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).