public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "octoploid at yandex dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59730] New: ICE: in type_dependent_expression_p, at cp/pt.c:19969 Date: Wed, 08 Jan 2014 20:09:00 -0000 [thread overview] Message-ID: <bug-59730-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59730 Bug ID: 59730 Summary: ICE: in type_dependent_expression_p, at cp/pt.c:19969 Product: gcc Version: 4.8.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: octoploid at yandex dot com markus@x4 /tmp % cat test.ii template <typename> void declval(); template <typename> void forward(); template <typename> class D; template <typename _Functor, typename... _Bound_args> class D <_Functor(_Bound_args...)> { template <typename... _Args, decltype(declval<_Functor>)> void operator()(...) { 0(forward<_Args>...); } }; markus@x4 /tmp % /usr/x86_64-pc-linux-gnu/gcc-bin/4.8.3/g++ -std=c++11 -O0 -c test.ii test.ii: In member function ‘void D<_Functor(_Bound_args ...)>::operator()(...)’: test.ii:8:24: internal compiler error: in type_dependent_expression_p, at cp/pt.c:19969 0(forward<_Args>...); ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. markus@x4 /tmp % /usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/g++ -std=c++11 -O0 -c test.ii test.ii: In member function ‘void D<_Functor(_Bound_args ...)>::operator()(...)’: test.ii:8:24: internal compiler error: in type_dependent_expression_p, at cp/pt.c:19496 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. markus@x4 /tmp % /usr/x86_64-pc-linux-gnu/gcc-bin/4.9.0/g++ -std=c++11 -O0 -c test.ii markus@x4 /tmp % >From gcc-bugs-return-439696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 08 20:38:30 2014 Return-Path: <gcc-bugs-return-439696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 6386 invoked by alias); 8 Jan 2014 20:38:29 -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 6355 invoked by uid 48); 8 Jan 2014 20:38:24 -0000 From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59720] [OOP] class/extends, multiple generic assignment Date: Wed, 08 Jan 2014 20:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gmx dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: janus at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59720-4-sUB4ufBHbx@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59720-4@http.gcc.gnu.org/bugzilla/> References: <bug-59720-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-01/txt/msg00838.txt.bz2 Content-length: 1244 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY720 --- Comment #9 from Harald Anlauf <anlauf at gmx dot de> --- (In reply to janus from comment #8) > (In reply to Harald Anlauf from comment #7) > > Thanks for checking, Harald. So XLF and NAG agree with gfortran on comment > 6. That's the easy part (since the interpretation of these cases is > explicitly given in the standard). Apparently ifort and pgfortran are buggy > in this area. > > Could you also check what XLF and NAG report on comment 1 (which is a > somewhat more questionable case)? Here we go: % xlf2008 pr59720.f90 ** kleiner === End of Compilation 1 =="pr59720.f90", line 42.44: 1514-699 (S) Procedure "ass_gf" must have a nonoptional dummy argument that corresponds by position in the argument list to a dummy argument not present in procedure "ass_en", present and type incompatible, present with different kind type parameters, or present with a different rank. % nagfor pr59720.f90 NAG Fortran Compiler Release 5.3.2(951) Error: pr59720.f90, line 65: Ambiguous specific type-bound procedures ASSIGN2 and ASSIGN for type-bound generic ASSIGNMENT(=) in type MYTYPE Errors in declarations, no further processing for GROSSER Apparently both agree with gfortran ;-)
next reply other threads:[~2014-01-08 20:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-08 20:09 octoploid at yandex dot com [this message] 2014-01-08 21:11 ` [Bug c++/59730] " jakub at gcc dot gnu.org 2014-01-08 22:43 ` paolo.carlini at oracle dot com 2014-01-09 17:46 ` paolo at gcc dot gnu.org 2014-01-09 17:46 ` paolo.carlini at oracle dot com 2014-01-10 16:17 ` jason at gcc dot gnu.org 2014-01-10 18:46 ` paolo at gcc dot gnu.org 2014-01-10 18:48 ` paolo.carlini at oracle dot com
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-59730-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: linkBe 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).