public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60531] New: template function not resolved when comparing functions
Date: Fri, 14 Mar 2014 20:38:00 -0000 [thread overview]
Message-ID: <bug-60531-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60531
Bug ID: 60531
Summary: template function not resolved when comparing
functions
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: harald at gigawatt dot nl
template <typename T> void f();
int main() { f<int> == f<int>; }
is rejected with
test.cc: In function ‘int main()’:
test.cc:2:24: error: invalid operands of types ‘<unresolved overloaded function
type>’ and ‘<unresolved overloaded function type>’ to binary ‘operator==’
int main() { f<int> == f<int>; }
I see no reason why this would be invalid, and it is accepted by all other
compilers I was able to test (clang, Intel, Sun, MSVC), but it is rejected by
GCC at least as far back as 4.3.
>From gcc-bugs-return-446338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 21:29:41 2014
Return-Path: <gcc-bugs-return-446338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14979 invoked by alias); 14 Mar 2014 21:29:40 -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 14934 invoked by uid 55); 14 Mar 2014 21:29:36 -0000
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60392] Problem with TRANSPOSE and CONTIGUOUS dummy arguments
Date: Fri, 14 Mar 2014 21:29: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.2
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikael at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60392-4-TmCyf3AuHT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60392-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-03/txt/msg01207.txt.bz2
Content-length: 664
http://gcc.gnu.org/bugzilla/show_bug.cgi?id`392
--- Comment #7 from Mikael Morin <mikael at gcc dot gnu.org> ---
Author: mikael
Date: Fri Mar 14 21:28:59 2014
New Revision: 208581
URL: http://gcc.gnu.org/viewcvs?rev 8581&root=gcc&view=rev
Log:
fortran/
PR fortran/60392
* trans-array.c (gfc_conv_array_parameter): Don't reuse the descriptor
if it has transposed dimensions.
testsuite/
PR fortran/60392
* gfortran.dg/transpose_4.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/transpose_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
next reply other threads:[~2014-03-14 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 20:38 harald at gigawatt dot nl [this message]
2014-03-15 12:06 ` [Bug c++/60531] " harald at gigawatt dot nl
2021-01-19 16:36 ` ppalka at gcc dot gnu.org
2021-07-28 5:18 ` pinskia at gcc dot gnu.org
2021-08-12 2:14 ` pinskia at gcc dot gnu.org
2021-08-12 2:15 ` pinskia at gcc dot gnu.org
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-60531-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).