This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/36260] New: Audit intrinsic.texi and check whether keyword= names match


See http://gcc.gnu.org/ml/fortran/2008-05/msg00207.html

Currently, the keywords used in intrinsic.texi don't match intrinsic.c.
(So far for all non-vendor extensions, intrinsic.c was correct.)

    TODO:
    - FSTAT: Fix intrinsic.{texi,c} argument-name mismatch
    - FREE: Fix intrinsic.{texi,c} argument-name mismatch
    - Everything after LINK needs to be audited
    and the problems mentioned at c.l.f. need to be fixed*

- LINK needs to be fixed. Currently there is a mismatch of the keywords between
the subroutine and function version (in intrinsic.c) and neither of them
matches intrinsic.texi.

*
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/07bc8e6635971853
- MOVE_ALLOC(SRC, DEST)   should be   MOVE_ALLOC(FROM, TO)
- loc(ARRAY), nint(A), write(*,*) real(A), sizeof(I)


-- 
           Summary: Audit intrinsic.texi and check whether keyword= names
                    match
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]