From: Joe Buck <Joe.Buck@synopsys.COM>
To: xing xing <xing_82@hotmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: To gcc steering committee
Date: Mon, 29 Nov 2004 17:59:00 -0000 [thread overview]
Message-ID: <20041129093802.B1687@synopsys.com> (raw)
In-Reply-To: <BAY22-F17D75A35EDAAE2F244FEB882BA0@phx.gbl>; from xing_82@hotmail.com on Fri, Nov 26, 2004 at 04:51:02PM +0800
On Fri, Nov 26, 2004 at 04:51:02PM +0800, xing xing wrote:
> Hello gcc steering committe:
>
> Is gcc steering committe intrested in add a verification component to
> gcc, as software verification technology plays a fast-developing area to
> guarantee software reliability.
Can you be more specific about what you mean? Are you thinking of
something along the lines of Dawson Engler's work, or the Microsoft
SLAM project?
http://metacomp.stanford.edu/
http://research.microsoft.com/slam/
In any case, technical evaluation of any proposed new features happens
on this list. The SC has to decide whether to accept features that take
GCC in a new direction, but that would come later.
prev parent reply other threads:[~2004-11-29 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 10:27 xing xing
2004-11-29 17:59 ` Joe Buck [this message]
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=20041129093802.B1687@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=xing_82@hotmail.com \
/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).