RetroSearch Browse

Tue Apr 9 09:01:40 PDT 2013 · http://mail.openjdk.java.net/pipermail/jdk8-dev/2013-April/002275.html

On Tue, Apr 9, 2013 at 8:39 AM, David DeHaven <david.dehaven at oracle.com>wrote:

>
> > [ cc'ing awt-dev@ ]
> >
> > Probably gcc can't process typedefs with visibility attributes
> specified, hence the changes to AWT. Generally they look good.
>
> It's not necessary for those typedefs as those types are not being used to
> define exported functions. The way it was being used in awt_LoadLibrary.c
> doesn't make any sense. It shouldn't be used for typedefs at all, it's used
> to mark a specific function for export which has nothing to do with the
> functions signature.
>
>
Right.  Use of JNIEXPORT in a typedef is a bug, essentially. (Except that
the semantics of JNIEXPORT and JNICALL are not actually documented anywhere
AFAIK; I'm using the "obvious" semantics of JNIEXPORT)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.openjdk.java.net/pipermail/jdk8-dev/2013-April/002275.html below:

Define JNIEXPORT as visibility default with GCC?