public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian_harvey at bigpond dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64324] New: Deferred character specific functions not permitted in generic operator interface
Date: Tue, 16 Dec 2014 04:23:00 -0000	[thread overview]
Message-ID: <bug-64324-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64324

            Bug ID: 64324
           Summary: Deferred character specific functions not permitted in
                    generic operator interface
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ian_harvey at bigpond dot com

gfortran built from current trunk rejects the following with "Error: User
operator procedure ‘tostring’ at (1) cannot be assumed character length"

MODULE m
  IMPLICIT NONE
  INTERFACE OPERATOR(.ToString.)
    MODULE PROCEDURE tostring
  END INTERFACE OPERATOR(.ToString.)
CONTAINS
  FUNCTION tostring(arg)
    INTEGER, INTENT(IN) :: arg
    CHARACTER(:), ALLOCATABLE :: tostring
    tostring = '42'
  END FUNCTION tostring
END MODULE m


(The procedure has deferred length, not assumed length.)


$ gfortran -v -c 2014-12-16\ ToString.f90
Using built-in specs.
COLLECT_GCC=gfortran
Target: x86_64-unknown-linux-gnu
Configured with: .././src/configure --prefix=/home/MEGMS2/ian/usr/gcc-5.0.0
--enable-languages=c,c++,fortran --enable-libgomp --enable-checking=release
Thread model: posix
gcc version 5.0.0 20141215 (experimental) (GCC) 

COLLECT_GCC_OPTIONS='-v' '-c' '-mtune=generic' '-march=x86-64'
 /home/MEGMS2/ian/usr/gcc-5.0.0/libexec/gcc/x86_64-unknown-linux-gnu/5.0.0/f951
2014-12-16 ToString.f90 -quiet -dumpbase 2014-12-16 ToString.f90 -mtune=generic
-march=x86-64 -auxbase 2014-12-16 ToString -version -fintrinsic-modules-path
/home/MEGMS2/ian/usr/gcc-5.0.0/lib/gcc/x86_64-unknown-linux-gnu/5.0.0/finclude
-o /tmp/cctex4Ju.s
GNU Fortran (GCC) version 5.0.0 20141215 (experimental)
(x86_64-unknown-linux-gnu)
    compiled by GNU C version 5.0.0 20141215 (experimental), GMP version 6.0.0,
MPFR version 3.1.2, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran (GCC) version 5.0.0 20141215 (experimental)
(x86_64-unknown-linux-gnu)
    compiled by GNU C version 5.0.0 20141215 (experimental), GMP version 6.0.0,
MPFR version 3.1.2, MPC version 1.0.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
2014-12-16 ToString.f90:7:2:

   FUNCTION tostring(arg)
  1
Error: User operator procedure ‘tostring’ at (1) cannot be assumed character
length
>From gcc-bugs-return-470831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 16 06:23:18 2014
Return-Path: <gcc-bugs-return-470831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10538 invoked by alias); 16 Dec 2014 06:23:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10487 invoked by uid 55); 16 Dec 2014 06:23:12 -0000
From: "jasonwucj at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64217] LRA: generate wrong liveness info after r217947 for clobber in jump_insn
Date: Tue, 16 Dec 2014 06:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jasonwucj at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jasonwucj at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64217-4-9MC19tm4kv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64217-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64217-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg01838.txt.bz2
Content-length: 442

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd217

--- Comment #3 from Chung-Ju Wu <jasonwucj at gcc dot gnu.org> ---
Author: jasonwucj
Date: Tue Dec 16 06:22:35 2014
New Revision: 218774

URL: https://gcc.gnu.org/viewcvs?rev!8774&root=gcc&view=rev
Log:
    PR target/64217
    * config/nds32/nds32.md (casesi_internal): Add '=r' for clobber
    register constraint.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/nds32/nds32.md


             reply	other threads:[~2014-12-16  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  4:23 ian_harvey at bigpond dot com [this message]
2014-12-21 11:01 ` [Bug fortran/64324] " dominiq at lps dot ens.fr

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=bug-64324-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).