From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Diego Novillo <dnovillo@google.com>,
Olatunji Ruwase <tjruwase@google.com>,
gcc@gcc.gnu.org
Subject: Re: [plugin] Directory for plugins distributed with gcc
Date: Wed, 15 Jul 2009 20:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0907152045210.25214@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4A5E3F2B.9010409@gnu.org>
On Wed, 15 Jul 2009, Paolo Bonzini wrote:
> On 07/15/2009 09:36 PM, Joseph S. Myers wrote:
> > Before moving something out to a plugin (if we think that is technically
> > appropriate for the particular code in question) we should have a way to
> > build code, set up to be built as a plugin, into the compiler so that the
> > -fplugin options find the built-in code, in a way that does not depend on
> > plugins otherwise being supported on the host system; maybe somewhere in
> > the source tree to put sources for plugins that get built into the
> > compiler, or a configure option to point to such sources.
>
> It would be easy to switch from libdl to libltdl (which is independent from
> libtool, and can be built as a host module from the toplevel makefile), and
> use libtool -dlpreopen if this is desired.
Unless libltdl can be statically linked in, using it is a bad idea for
other reasons as previously discussed at length.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-07-15 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com>
2009-07-15 18:43 ` Diego Novillo
2009-07-15 18:51 ` Olatunji Ruwase
2009-07-15 19:14 ` Diego Novillo
2009-07-15 19:36 ` Joseph S. Myers
2009-07-15 20:43 ` Paolo Bonzini
2009-07-15 20:53 ` Joseph S. Myers [this message]
2009-07-15 21:16 ` Basile STARYNKEVITCH
2009-07-15 21:43 ` Paolo Bonzini
2009-07-16 13:09 ` Rafael Espindola
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.0907152045210.25214@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=tjruwase@google.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).