From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10311 invoked by alias); 15 Jul 2009 20:53:52 -0000 Received: (qmail 10302 invoked by uid 22791); 15 Jul 2009 20:53:52 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_FAIL X-Spam-Check-By: sourceware.org Received: from mx20.gnu.org (HELO mx20.gnu.org) (199.232.41.8) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Jul 2009 20:53:46 +0000 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MRBTz-000493-Ji for gcc@gcc.gnu.org; Wed, 15 Jul 2009 16:53:43 -0400 Received: (qmail 23068 invoked from network); 15 Jul 2009 20:47:02 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 15 Jul 2009 20:47:02 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.69) (envelope-from ) id 1MRBNU-0007XC-Sd; Wed, 15 Jul 2009 20:47:00 +0000 Date: Wed, 15 Jul 2009 20:53:00 -0000 From: "Joseph S. Myers" To: Paolo Bonzini cc: Diego Novillo , Olatunji Ruwase , gcc@gcc.gnu.org Subject: Re: [plugin] Directory for plugins distributed with gcc In-Reply-To: <4A5E3F2B.9010409@gnu.org> Message-ID: References: <4A5E3F2B.9010409@gnu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00291.txt.bz2 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