[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2021-10-24 Thread sandra at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

sandra at gcc dot gnu.org changed:

   What|Removed |Added

 CC||sandra at gcc dot gnu.org

--- Comment #8 from sandra at gcc dot gnu.org ---
Still present on master, so no, this bug hasn't spontaneously fixed itself. 
:-(

[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2019-12-13 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

kargl at gcc dot gnu.org changed:

   What|Removed |Added

 CC||kargl at gcc dot gnu.org

--- Comment #7 from kargl at gcc dot gnu.org ---
(In reply to nightstrike from comment #6)
> I still get this on gcc 9.1

You forgot to attach your patch.  I have over
the years that bugs tend to to spontaneously 
fix themselves.

[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2019-12-13 Thread nightstrike at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

nightstrike  changed:

   What|Removed |Added

 CC||nightstrike at gmail dot com

--- Comment #6 from nightstrike  ---
I still get this on gcc 9.1

[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2015-11-10 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111
Bug 49111 depends on bug 64861, which changed state.

Bug 64861 Summary: Possible wrong code with BIND(C) and PRIVATE + slightly 
bogus warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64861

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |DUPLICATE

[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2015-11-10 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

Dominique d'Humieres  changed:

   What|Removed |Added

 CC||burnus at gcc dot gnu.org

--- Comment #5 from Dominique d'Humieres  ---
*** Bug 64861 has been marked as a duplicate of this bug. ***

[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2013-12-29 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

Dominique d'Humieres dominiq at lps dot ens.fr changed:

   What|Removed |Added

   Keywords||diagnostic
   Priority|P3  |P4
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2013-12-29
 Ever confirmed|0   |1
   Severity|normal  |enhancement

--- Comment #4 from Dominique d'Humieres dominiq at lps dot ens.fr ---
Still present at r206227.


[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2012-10-12 Thread craig.powers at gmail dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111



Craig Powers craig.powers at gmail dot com changed:



   What|Removed |Added



 CC||craig.powers at gmail dot

   ||com



--- Comment #3 from Craig Powers craig.powers at gmail dot com 2012-10-12 
20:53:53 UTC ---

I see the accessibility denoted by PRIVATE/PUBLIC as conceptually different

from the accessibility denoted by BIND(C).  In addition to the fact that

BIND(C) does not distinguish an import from an export, there is also the

consideration that one might wish to hide the C-callable routine (marked with

BIND(C)) from other Fortran code by also marking it PRIVATE.



I'm in the process of producing a Fortran interface to a C library, and I find

that there are some instances where I want to declare the import as PRIVATE and

then provide a wrapper routine to take care of the Fortran-to-C stuff that is

mechanical e.g. converting a Fortran array.



Because my Fortran is a little rusty, and this is my first time making any

extended use of the BIND(C) features, the warning made me concerned that I

hadn't accomplished what I intended to accomplish.



I see this warning as far more likely to be a spurious complaint about valid

and intended usage than to be a useful hint about something unintended.


[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2011-05-22 Thread jwmwalrus at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

--- Comment #1 from John jwmwalrus at gmail dot com 2011-05-22 16:14:48 UTC 
---
Created attachment 24328
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24328
Test case


[Bug fortran/49111] Unnecessary warning for private interfaces having the BIND(C) attribute

2011-05-22 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49111

Tobias Burnus burnus at gcc dot gnu.org changed:

   What|Removed |Added

  Attachment #24328|application/octet-stream|text/plain
  mime type||

--- Comment #2 from Tobias Burnus burnus at gcc dot gnu.org 2011-05-22 
17:04:39 UTC ---
Comment on attachment 24328
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=24328
Test case

(In reply to comment #0)
 gfortran warns about the private symbol 'strerror' being given a binding 
 label.
 
 In sections 5.3.2 and 5.3.5 of the Fortran 2008 standard, there seems to be no
 restriction between the BIND and PRIVATE attributes ---[...] and therefore no
 warning should be issued by the gfortran.

The Fortran standard only states whether something is valid or not - not
whether a compiler should issue a warning or not.

The idea is that having PRIVATE (making it inaccessible from outside the module
by direct means) and having a C binding (make it available out side) are in a
way opposite concepts - and thus possible unintended.

However, for an INTERFACE - as opposed to a module procedure - a warning indeed
does not make much sense.