public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105397] C++ modules vs -fvisibility option
Date: Wed, 21 Dec 2022 11:32:38 +0000	[thread overview]
Message-ID: <bug-105397-4-2x4jMKpEKg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105397-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
the import places attributes at the end.

so 
import module Foo [[....]];

it would seem to be symmetrical to have:

export import Foo [[...]];
export module Foo [[...]];

but, ts present, (if I read it correctly) it seems that the WD says

export [[...]] module Foo;
export [[...]] int bar ();

which would then be weird with export [[...]] import Foo [[...]];

      parent reply	other threads:[~2022-12-21 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 17:46 [Bug c++/105397] New: Cannot export module initializer symbols with `-fvisibility=hidden` bugzilla.gcc at me dot benboeckel.net
2022-06-09 13:47 ` [Bug c++/105397] " redbeard0531 at gmail dot com
2022-12-08 20:43 ` [Bug c++/105397] C++ modules vs -fvisibility option bugzilla.gcc at me dot benboeckel.net
2022-12-21 11:32 ` iains at gcc dot gnu.org [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=bug-105397-4-2x4jMKpEKg@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).