public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15032] [gfortran] gfc_conv_constant Assertion failure Date: Wed, 21 Apr 2004 12:37:00 -0000 [thread overview] Message-ID: <20040421122503.9834.qmail@sources.redhat.com> (raw) In-Reply-To: <20040420213915.15032.Tobias.Schlueter@physik.uni-muenchen.de> ------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-21 12:25 ------- (In reply to comment #3) > Note you cannot just attach with valgrind as the GC in GCC will throw it off, you can use --enable- > checking=valgrind to enabled the use of valgrind. Ok, I built with --enable-checking=valgrind and ran 'valgrind f951 t2.f90' and 'valgrind f951 < t2.f90'. I'm not sure if that's the right way, as there is no documentation on how to use valgrind together with the compiler. See PR15039. I'll attach the output below. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15032
next prev parent reply other threads:[~2004-04-21 12:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-20 21:47 [Bug fortran/15032] New: " Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-20 21:55 ` [Bug fortran/15032] " Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-20 23:47 ` pinskia at gcc dot gnu dot org 2004-04-20 23:51 ` pinskia at gcc dot gnu dot org 2004-04-21 0:32 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-21 12:37 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [this message] 2004-05-17 1:53 ` tobi at gcc dot gnu dot org 2004-05-26 23:14 ` pinskia at gcc dot gnu dot org 2004-07-12 10:24 ` [Bug fortran/15032] " tobi 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=20040421122503.9834.qmail@sources.redhat.com \ --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).