public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: mdupont777@yahoo.com (James Michael DuPont)
Cc: Joe.Buck@synopsys.COM (Joe Buck), gcc@gnu.org
Subject: Re: XML dumping and GraphViz/VCG in the GCC ast-optimizer-branch
Date: Tue, 15 Oct 2002 13:13:00 -0000	[thread overview]
Message-ID: <200210151915.g9FJF5I22148@piper.synopsys.com> (raw)
In-Reply-To: <20021015180452.73666.qmail@web13303.mail.yahoo.com> from "James Michael DuPont" at Oct 15, 2002 11:04:52 AM


> Now, if we look at the problem of communication, how can the gcc safely
> communicate the asts to the vcg for layout. 

You'll have to assume, I think, that anything gcc can write anyone can
use.

> Now, I am not a laywer, but 
> I think that if we can show that if the data is put into such a form
> that it is indended for transport between modules, and a third party
> takes that data a runs off with it, we can then say that they got
> between two statically linked modules . Maybe that will offer some
> protection against non-free modules getting in between?

I think it would be hard to make such an argument if what is communicated
is basically just information about the structure of the user's own code.
But this list is not the best place for such discussions.

  reply	other threads:[~2002-10-15 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  7:34 James Michael DuPont
2002-10-15 11:06 ` Joe Buck
2002-10-15 11:19   ` James Michael DuPont
2002-10-15 11:37     ` Joe Buck
2002-10-15 11:48       ` James Michael DuPont
2002-10-15 13:13         ` Joe Buck [this message]
2002-10-19  4:31         ` Zack Weinberg
2002-10-15 18:03     ` Joseph S. Myers
2002-10-16  2:38       ` James Michael DuPont
2002-10-15  7:45 Robert Dewar
2002-10-15  7:53 ` James Michael DuPont
2002-10-15  8:28 Robert Dewar
2002-10-15 11:04 ` James Michael DuPont

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=200210151915.g9FJF5I22148@piper.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=Joe.Buck@synopsys.COM \
    --cc=gcc@gnu.org \
    --cc=mdupont777@yahoo.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).