Define JNIEXPORT as visibility default with GCC?

[Daniel D. Daugherty]

I couldn't find a 'jdk' repo relevant bug for this issue so I filed:

     8008509: 6588413 changed JNIEXPORT visibility for GCC on HSX, jdk's
              jni_md.h needs similar change
     http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8008509
     https://jbs.oracle.com/bugs/browse/JDK-8008509

Coleen did the original work on 6588413 so I added her to the "interest
list" for the new bug. The need for an update to the jdk repo's jni_md.h
file was raised during the code review for 6588413, but that detail appears
to have been dropped.

Dan



On 2/19/13 1:20 PM, Jeremy Manson wrote:
> Since the proposed change is user-visible (i.e., not just for building 
> the JDK, but also for building pretty much every JNI blob in 
> existence), wouldn't you want the correct check anyway?  Does the JDK 
> have rules about which version of gcc you are allowed to use to build 
> JNI?
>
> Jeremy
>
>
> On Mon, Feb 18, 2013 at 1:36 AM, Florian Weimer <fweimer at redhat.com 
> <mailto:fweimer at redhat.com>> wrote:
>
>     On 02/17/2013 11:55 PM, David Holmes wrote:
>
>         On 16/02/2013 2:46 AM, Florian Weimer wrote:
>
>             On 02/15/2013 05:41 PM, Jeremy Manson wrote:
>
>                 Can we just blacklist 4.1.2 explicitly?
>
>
>             Folks, per README-build.html, the minimum GCC version is
>             4.2 on MacOS X
>             and 4.3 everywhere else.  Do we really have to bother with
>             4.1.2 at this
>             point?
>
>
>         There are ports that still use these older gcc versions.
>
>
>     Oh.  Perhaps this information can be added to README-builds.html?
>
>
>     -- 
>     Florian Weimer / Red Hat Product Security Team
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/attachments/20130219/728588ae/attachment.html