From: Jose Da Silva <digital@joescat.com>
To: gcc-help@gcc.gnu.org
Subject: updates to the visibility webpage
Date: Sat, 1 Jan 2022 12:57:19 -0800 [thread overview]
Message-ID: <202201011257.19269.digital@joescat.com> (raw)
Hi,
I think the https://gcc.gnu.org/wiki/Visibility could be updated a little.
Right now it shows
#if defined _WIN32 || defined __CYGWIN__
but I think it could be upgraded further with
#if defined (_WIN32) || defined (__CYGWIN__) || (_WIN64) || defined
(__CYGWIN64__)
I have more information here if you want to look through it which was used
to get libuninameslist library working:
https://github.com/fontforge/libuninameslist/issues/25
and patch applied if it helps:
https://github.com/fontforge/libuninameslist/commit/3d042076034801caaffc138ef13ce0af9bac61d5
Thanks,
Hope everyone has a Happy New Year!
Joe Da Silva
reply other threads:[~2022-01-01 20:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202201011257.19269.digital@joescat.com \
--to=digital@joescat.com \
--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).