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/31298] New: Uninitialized variable in f951 (in read_module) Date: Wed, 21 Mar 2007 15:15:00 -0000 [thread overview] Message-ID: <bug-31298-13404@http.gcc.gnu.org/bugzilla/> (raw) valgrind finds when compiling gfortran.dg/use_6.f90 the following unitinitalized variables: ==29473== Conditional jump or move depends on uninitialised value(s) ==29473== at 0x43DD76: read_module (module.c:733) ==29473== by 0x43E664: gfc_use_module (module.c:4201) ==29473== by 0x443DC7: accept_statement (parse.c:1256) ==29473== by 0x444854: parse_spec (parse.c:1902) ==29473== by 0x445C95: parse_progunit (parse.c:2901) ==29473== by 0x445F01: gfc_parse_file (parse.c:3239) ==29473== by 0x46423D: gfc_be_parse_file (f95-lang.c:307) ==29473== by 0x679573: toplev_main (toplev.c:1050) ==29473== by 0x52BE943: (below main) (in /lib64/libc-2.5.so) Analogusly for use_5.f90. -- Summary: Uninitialized variable in f951 (in read_module) Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31298
next reply other threads:[~2007-03-21 15:15 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-21 15:15 burnus at gcc dot gnu dot org [this message] 2007-03-28 1:39 ` [Bug fortran/31298] " jvdelisle at gcc dot gnu dot org 2007-03-28 3:21 ` jvdelisle at gcc dot gnu dot org 2007-03-31 21:51 ` burnus at gcc dot gnu dot org 2007-04-15 19:20 ` burnus at gcc dot gnu dot org 2007-04-18 9:18 ` burnus at gcc dot gnu dot org 2007-05-22 12:32 ` fxcoudert at gcc dot gnu dot org 2007-05-22 12:45 ` burnus at gcc dot gnu dot org 2007-06-23 13:41 ` [Bug fortran/31298] Uninitialized variable in f951 (in read_module) / renaming operator in USE burnus at gcc dot gnu dot org 2007-08-14 21:17 ` burnus at gcc dot gnu dot org 2007-08-17 8:14 ` [Bug fortran/31298] F2003: use mod, operator(+) => operator(.userOp.) not supported burnus at gcc dot gnu dot org 2007-08-17 15:10 ` patchapp at dberlin dot org 2007-08-26 18:37 ` burnus at gcc dot gnu dot org 2007-08-26 18:43 ` burnus at gcc dot gnu dot org 2008-01-15 15:33 ` burnus at gcc dot gnu dot org 2008-03-14 16:46 ` rguenth at gcc dot gnu dot org 2009-11-01 18:06 ` burnus 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=bug-31298-13404@http.gcc.gnu.org/bugzilla/ \ --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).