public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: "cohenarthur at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/113499] crab1 fails to link when configuring with --disable-plugin
Date: Fri, 12 Apr 2024 15:22:23 +0000	[thread overview]
Message-ID: <bug-113499-35322-wijJUC4afh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113499-35322@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499

--- Comment #6 from Arthur Cohen <cohenarthur at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> (In reply to Thomas Schwinge from comment #4)
> > If I understood Arthur correctly, GCC/Rust is going to effectively require
> > 'dlopen' (and therefore '--enable-plugin'?), so that means, if the latter's
> > not available we have to auto-disable Rust language front end if enabled
> > '--enable-languages=all' vs. raise a 'configure'-time error if enabled via
> > explicit '--enable-languages=rust'?
> 
> Not sure - --enable-plugin is not about dlopen, it's about exporting all
> GCCs internal symbols for use by a dlopened shared module.  Is the
> macro processing requiring this or is it rather self-contained?
> 
> Being able to dlopen() is something different.

No, it does not require this and is rather self contained. Macro expansion
needs to be able to dlopen() compiled Rust libraries, which contain a specific
type of function our frontend calls as a macro. So we always need to dlopen().

Is there anything similar in other frontends? If so, how does it work on such
platforms which do not support dlopen()?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-12 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19  6:55 [Bug rust/113499] New: " rguenth at gcc dot gnu.org
2024-01-19  7:05 ` [Bug rust/113499] " rguenth at gcc dot gnu.org
2024-01-19  7:08 ` rguenth at gcc dot gnu.org
2024-02-09 13:33 ` rguenth at gcc dot gnu.org
2024-02-09 13:35 ` rguenth at gcc dot gnu.org
2024-03-18 11:20 ` tschwinge at gcc dot gnu.org
2024-03-18 12:33 ` rguenth at gcc dot gnu.org
2024-04-12 15:22 ` cohenarthur at gcc dot gnu.org [this message]
2024-04-12 18:07 ` xry111 at gcc dot gnu.org
2024-04-15  6:21 ` rguenth at gcc dot gnu.org

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=bug-113499-35322-wijJUC4afh@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-rust@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).