public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39489] [4.3 regression] write_atom(): Writing negative integer Date: Tue, 12 May 2009 22:06:00 -0000 [thread overview] Message-ID: <20090512220552.15948.qmail@sourceware.org> (raw) In-Reply-To: <bug-39489-17466@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from burnus at gcc dot gnu dot org 2009-05-12 22:05 ------- Some more data: ==16952== Conditional jump or move depends on uninitialised value(s) ==16952== at 0x4470FC: write_atom (module.c:1339) ==16952== by 0x4472DD: mio_integer (module.c:1450) ==16952== by 0x447DAC: mio_typespec (module.c:1870) ==16952== by 0x449710: mio_symbol (module.c:3048) That are lines such as: mio_integer (&ts->is_c_interop); -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39489
next prev parent reply other threads:[~2009-05-12 22:06 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 9:43 [Bug fortran/39489] New: Error in module with gfortran 4.3 in 32 bit processors n dot pinhao at netvisao dot pt 2009-03-18 9:47 ` [Bug fortran/39489] " dominiq at lps dot ens dot fr 2009-03-18 10:01 ` dfranke at gcc dot gnu dot org 2009-03-18 15:07 ` n dot pinhao at netvisao dot pt 2009-03-18 15:08 ` n dot pinhao at netvisao dot pt 2009-03-18 15:44 ` dominiq at lps dot ens dot fr 2009-03-18 16:35 ` [Bug fortran/39489] [4.3 Regression] write_atom(): Writing negative integer dfranke at gcc dot gnu dot org 2009-03-18 17:45 ` n dot pinhao at netvisao dot pt 2009-03-18 17:48 ` n dot pinhao at netvisao dot pt 2009-03-19 8:24 ` n dot pinhao at netvisao dot pt 2009-03-31 15:59 ` [Bug fortran/39489] [4.3 regression] " jsm28 at gcc dot gnu dot org 2009-04-22 13:26 ` rguenth at gcc dot gnu dot org 2009-04-28 11:46 ` burnus at gcc dot gnu dot org 2009-05-12 22:06 ` burnus at gcc dot gnu dot org [this message] 2009-07-05 9:07 ` fxcoudert 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=20090512220552.15948.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: linkBe 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).