From: Ian Lance Taylor <iant@google.com>
To: Arindam <arindam.mukerjee@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Restricting symbol binding within shared object
Date: Thu, 21 Aug 2008 04:43:00 -0000 [thread overview]
Message-ID: <m3pro3safs.fsf@google.com> (raw)
In-Reply-To: <d85a51ff0808201230w78c1bb0axf19a1b443088a79b@mail.gmail.com> (Arindam's message of "Thu\, 21 Aug 2008 01\:00\:34 +0530")
Arindam <arindam.mukerjee@gmail.com> writes:
>> With a newer version of gcc you can use visibility attributes. That
>> is probably your best approach here.
>>
>> http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/Function-Attributes.html#Function-Attributes
>>
>> search for
>> visibility ("visibility_type")
>>
>
> Cool ... so this mimics the Windows __declspec(dllexport) kind of
> declarations. I know that newer versions of Sun Studio have
> essentially the same functionality (albeit with a less obnoxious
> syntax). I need to figure out if aCC on HP-UX has something similar
> too. Is this a new thing on ELF format?
It works for Mach-O (used on Mac OS) as well.
Ian
prev parent reply other threads:[~2008-08-20 20:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:12 Arindam
2008-08-19 16:58 ` special comments handling in the C compiler Tim Wang
2008-08-22 1:52 ` extern "C" From command line Seyran Avanesyan
2008-08-22 2:12 ` Brian Dessent
2008-08-23 1:38 ` Seyran Avanesyan
2008-08-23 2:37 ` Brian Dessent
2008-08-23 2:46 ` Seyran Avanesyan
2008-08-22 2:04 ` 64-bit gcc Seyran Avanesyan
2008-08-22 11:01 ` Brian Dessent
2008-08-22 20:09 ` Seyran Avanesyan
2008-08-22 22:32 ` Brian Dessent
2008-08-22 22:45 ` Seyran Avanesyan
2008-08-23 2:31 ` Brian Dessent
2008-08-23 2:45 ` NightStrike
2008-08-23 2:49 ` Seyran Avanesyan
2008-08-23 3:18 ` Brian Dessent
2008-08-23 2:00 ` NightStrike
2008-08-23 2:13 ` Seyran Avanesyan
2008-08-19 18:49 ` Restricting symbol binding within shared object Ian Lance Taylor
2008-08-20 19:36 ` Arindam
2008-08-21 4:43 ` Ian Lance Taylor [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=m3pro3safs.fsf@google.com \
--to=iant@google.com \
--cc=arindam.mukerjee@gmail.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).