From: Mike Stump <mrs@windriver.com>
To: amylaar@cygnus.co.uk, ghazi@caip.rutgers.edu
Cc: gcc@gcc.gnu.org, gdr@codesourcery.com
Subject: Re: Silently checking whether diagnostics would occur
Date: Wed, 13 Sep 2000 17:38:00 -0000 [thread overview]
Message-ID: <200009140038.RAA02308@kankakee.wrs.com> (raw)
> From: Joern Rennecke <amylaar@cygnus.co.uk>
> To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
> Date: Thu, 14 Sep 2000 00:38:09 +0100 (BST)
> I can see it now. Somewhere down the line, someone uses this
> format checking in another utility function. That function gets
> called by another utility function under certain circumstances.
> That function is then used by some piece of format-checking code.
> [ ... ]
You show an amazing predictive abilities...
:-)
For those not familiar with the compiler internals, this is a good
description of the variables named current_function_*, and the ones
that aren't, that that had been in the compiler and how the code
changed over time. That code is slightly cleaner today, but still
suffers in various ways.
next reply other threads:[~2000-09-13 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 17:38 Mike Stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-15 11:25 Kaveh R. Ghazi
2000-09-15 11:12 Kaveh R. Ghazi
2000-09-14 8:31 Kaveh R. Ghazi
2000-09-14 8:42 ` Michael Meissner
2000-09-14 10:47 ` Joseph S. Myers
2000-09-14 12:37 ` Joern Rennecke
2000-09-14 7:43 Kaveh R. Ghazi
2000-09-13 14:33 Kaveh R. Ghazi
2000-09-13 20:37 ` Michael Meissner
2000-09-13 8:50 Kaveh R. Ghazi
2000-09-13 13:51 ` Michael Meissner
2000-09-13 16:37 ` Joern Rennecke
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=200009140038.RAA02308@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=amylaar@cygnus.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=gdr@codesourcery.com \
--cc=ghazi@caip.rutgers.edu \
/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).