public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aspertame Man <AspertameMan@att.net>
To: gcc@gnu.org
Subject: A possible super feature to add to gcc
Date: Sun, 05 Dec 2010 20:30:00 -0000	[thread overview]
Message-ID: <1291581040.2886.6.camel@netbook> (raw)


 Back in the 1970's when we ran fortran on an IBM machine we had this
 really powerful command called CALL FDUMP that if inserted into a
 program would send the names and values of every variable, at the time
 of its call, to a printer or file. In my opinion this was much more
 useful at times than a symbolic debugger, in scientific number crunching
 applications.
 
  If gcc does not have a similar function call I feel there would be
 people using gcc in the scientific community that very well might
 appreciate CALL FDUMP being resurrected. 



             reply	other threads:[~2010-12-05 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 20:30 Aspertame Man [this message]
2010-12-05 20:41 ` Basile Starynkevitch
2010-12-05 23:04 ` Joern Rennecke
2010-12-06 11:49   ` Aspertame Man
2010-12-06 11:52     ` Richard Kenner
2010-12-06 12:20     ` Andreas Schwab
2010-12-06 16:44 ` Frank Ch. Eigler

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=1291581040.2886.6.camel@netbook \
    --to=aspertameman@att.net \
    --cc=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).