public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Klaus Grue <grue@diku.dk>
To: Brian Dessent <brian@dessent.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Dynamic compilation using gcc
Date: Thu, 20 Mar 2008 14:59:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0803201527070.17362@tyr.diku.dk> (raw)
In-Reply-To: <47E2693F.586737C3@dessent.net>

Dear Brian,

Thanks a lot for your answers and background information.

> No, nothing like [a C API] exists...
> dlopen has to mmap() the file...
> You could of course create the file in a tmpfs filesystem...
> I don't see what's so bad about using files.
> unlinking an open file is the standard technique...

I agree. Using files is not that bad. In fact, with the information you 
gave it seems to be the way to go. Thanks a lot. Your answers will save me 
a lot of time searching for something which does not exist.

Cheers,
Klaus

      reply	other threads:[~2008-03-20 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  9:54 Klaus Grue
2008-03-20 13:40 ` Brian Dessent
2008-03-20 14:59   ` Klaus Grue [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=Pine.LNX.4.64.0803201527070.17362@tyr.diku.dk \
    --to=grue@diku.dk \
    --cc=brian@dessent.net \
    --cc=gcc-help@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).