public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <bug-11685-4@http.gcc.gnu.org/bugzilla/>
@ 2013-10-14 16:34 ` paolo.carlini at oracle dot com
2014-10-13 10:34 ` flast at flast dot jp
2014-10-13 11:59 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 12+ messages in thread
From: paolo.carlini at oracle dot com @ 2013-10-14 16:34 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|gcc-bugs at gcc dot gnu.org |
--- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> ---
We need an updated testcase for this.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <bug-11685-4@http.gcc.gnu.org/bugzilla/>
2013-10-14 16:34 ` [Bug c++/11685] typeinfo is not demangled in error messages paolo.carlini at oracle dot com
@ 2014-10-13 10:34 ` flast at flast dot jp
2014-10-13 11:59 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 12+ messages in thread
From: flast at flast dot jp @ 2014-10-13 10:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
Kohei Takahashi <flast at flast dot jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |flast at flast dot jp
--- Comment #9 from Kohei Takahashi <flast at flast dot jp> ---
In GCC 4.8.3, we get following error.
$ g++ foo.cpp
foo.cpp:4:50: error: call to non-constexpr function ‘int get_uuidof(const
std::type_info&)’
template< class T ,int i = get_uuidof( typeid(T) ) >
^
foo.cpp:8:19: note: in template argument for type ‘int’
template TBoaz<int>;
^
foo.cpp:8:20: error: expected unqualified-id before ‘;’ token
template TBoaz<int>;
So, we can simply close this issue, can't we?
>From gcc-bugs-return-463912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 13 11:39:39 2014
Return-Path: <gcc-bugs-return-463912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2987 invoked by alias); 13 Oct 2014 11:39:39 -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 2945 invoked by uid 48); 13 Oct 2014 11:39:34 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63504] [5 Regression] Issues found by --enable-checking=valgrind
Date: Mon, 13 Oct 2014 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: trippels at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-63504-4-8BpowqzAJS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63504-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63504-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-10/txt/msg00933.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc504
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |emsr at gcc dot gnu.org
--- Comment #8 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Issue 4) started with r215752.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <bug-11685-4@http.gcc.gnu.org/bugzilla/>
2013-10-14 16:34 ` [Bug c++/11685] typeinfo is not demangled in error messages paolo.carlini at oracle dot com
2014-10-13 10:34 ` flast at flast dot jp
@ 2014-10-13 11:59 ` manu at gcc dot gnu.org
2 siblings, 0 replies; 12+ messages in thread
From: manu at gcc dot gnu.org @ 2014-10-13 11:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Kohei Takahashi from comment #9)
> So, we can simply close this issue, can't we?
I think so. Thanks for noticing!
>From gcc-bugs-return-463916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 13 12:13:46 2014
Return-Path: <gcc-bugs-return-463916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29746 invoked by alias); 13 Oct 2014 12:13:45 -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 29684 invoked by uid 48); 13 Oct 2014 12:13:41 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63521] The AArch64 backend doesn't define REG_ALLOC_ORDER.
Date: Mon, 13 Oct 2014 12:13: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: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha 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-63521-4-nXw9AsmrG4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63521-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-10/txt/msg00937.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?idc521
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Ideally, a port should not need to define reg_alloc_order; it's rather a blunt
instrument.
Better would be for the register allocator to have a better understanding of
which registers are being used for parameter passing in the current routine so
that it can pick from the remaining call-clobbered list.
^ permalink raw reply [flat|nested] 12+ messages in thread
[parent not found: <bug-11685-6528@http.gcc.gnu.org/bugzilla/>]
[parent not found: <20030727171012.11685.pinskia@gcc.gnu.org>]
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
@ 2003-08-23 1:00 ` dhazeghi at yahoo dot com
2003-08-29 12:48 ` gdr at gcc dot gnu dot org
` (4 subsequent siblings)
5 siblings, 0 replies; 12+ messages in thread
From: dhazeghi at yahoo dot com @ 2003-08-23 1:00 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
dhazeghi at yahoo dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|3.4 |---
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
2003-08-23 1:00 ` dhazeghi at yahoo dot com
@ 2003-08-29 12:48 ` gdr at gcc dot gnu dot org
2003-08-29 12:50 ` pinskia at physics dot uc dot edu
` (3 subsequent siblings)
5 siblings, 0 replies; 12+ messages in thread
From: gdr at gcc dot gnu dot org @ 2003-08-29 12:48 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
------- Additional Comments From gdr at gcc dot gnu dot org 2003-08-29 12:48 -------
I don't know what to do with this PR. Demangling the typeid as part of
diagnostic messages would mean that now the demangler is part of the compiler,
which in some sense is unacceptable. On the other hand, there should be room
for improvement.
does the rporter object to classifying this an enhancement, and nto a bug
proper?
-- Gaby
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
2003-08-23 1:00 ` dhazeghi at yahoo dot com
2003-08-29 12:48 ` gdr at gcc dot gnu dot org
@ 2003-08-29 12:50 ` pinskia at physics dot uc dot edu
2003-08-29 12:57 ` gdr at gcc dot gnu dot org
` (2 subsequent siblings)
5 siblings, 0 replies; 12+ messages in thread
From: pinskia at physics dot uc dot edu @ 2003-08-29 12:50 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
------- Additional Comments From pinskia at physics dot uc dot edu 2003-08-29 12:50 -------
Subject: Re: typeinfo is not demangled in error messages
>
> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
>
>
>
> ------- Additional Comments From gdr at gcc dot gnu dot org 2003-08-29 12:48 -------
> I don't know what to do with this PR. Demangling the typeid as part of
> diagnostic messages would mean that now the demangler is part of the compiler,
> which in some sense is unacceptable. On the other hand, there should be room
> for improvement.
>
> does the rporter object to classifying this an enhancement, and nto a bug
> proper?
Yes that is fine.
>
> -- Gaby
>
>
>
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
` (2 preceding siblings ...)
2003-08-29 12:50 ` pinskia at physics dot uc dot edu
@ 2003-08-29 12:57 ` gdr at gcc dot gnu dot org
2003-08-29 14:51 ` bangerth at dealii dot org
2003-08-29 19:36 ` gdr at integrable-solutions dot net
5 siblings, 0 replies; 12+ messages in thread
From: gdr at gcc dot gnu dot org @ 2003-08-29 12:57 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
gdr at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
` (3 preceding siblings ...)
2003-08-29 12:57 ` gdr at gcc dot gnu dot org
@ 2003-08-29 14:51 ` bangerth at dealii dot org
2003-08-29 19:36 ` gdr at integrable-solutions dot net
5 siblings, 0 replies; 12+ messages in thread
From: bangerth at dealii dot org @ 2003-08-29 14:51 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
------- Additional Comments From bangerth at dealii dot org 2003-08-29 14:51 -------
Gaby, there might be a simpler way: the message reads
`get_uuidof(const std::type_info&)((&_ZTIi))'
i.e. function_name(type of argument)((value of argument)). If we just omit the value of
the argument, then this would already be enough. I find the format quite confusing
anyway.
W.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] typeinfo is not demangled in error messages
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
` (4 preceding siblings ...)
2003-08-29 14:51 ` bangerth at dealii dot org
@ 2003-08-29 19:36 ` gdr at integrable-solutions dot net
5 siblings, 0 replies; 12+ messages in thread
From: gdr at integrable-solutions dot net @ 2003-08-29 19:36 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
------- Additional Comments From gdr at integrable-solutions dot net 2003-08-29 19:36 -------
Subject: Re: typeinfo is not demangled in error messages
"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| Gaby, there might be a simpler way: the message reads
| `get_uuidof(const std::type_info&)((&_ZTIi))'
| i.e. function_name(type of argument)((value of argument)). If we
| just omit the value of the argument, then this would already be
| enough. I find the format quite confusing anyway.
I agree on the confusing looking of the message.
However, we cannot omit the argument because it is the value of the
function that is being used. What we can avoid, however, is getting
the mangled name. I believe this is just another case of the
front-end being too eager.
-- Gaby
^ permalink raw reply [flat|nested] 12+ messages in thread
* [Bug c++/11685] New: typeinfo is not demangled in error messages
@ 2003-07-27 17:10 pinskia at physics dot uc dot edu
2003-07-28 3:45 ` [Bug c++/11685] " pinskia at physics dot uc dot edu
2003-07-30 15:22 ` ehrhardt at mathematik dot uni-ulm dot de
0 siblings, 2 replies; 12+ messages in thread
From: pinskia at physics dot uc dot edu @ 2003-07-27 17:10 UTC (permalink / raw)
To: gcc-bugs
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11685
Summary: typeinfo is not demangled in error messages
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pinskia at physics dot uc dot edu
CC: gcc-bugs at gcc dot gnu dot org,gdr at gcc dot gnu dot
org
Code:
#include <typeinfo>
int get_uuidof( const std::type_info& inf );
template< class T ,int i = get_uuidof( typeid(T) ) >
struct TBoaz{
} ;
template TBoaz<int>;
Gives the following error:
prnew10.cc:8: error: non-constant `get_uuidof(const std::type_info&)((&_ZTIi))'
cannot be used as template argument
Notice _ZTIi is not demangled to typeid(int).
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2014-10-13 11:59 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-11685-4@http.gcc.gnu.org/bugzilla/>
2013-10-14 16:34 ` [Bug c++/11685] typeinfo is not demangled in error messages paolo.carlini at oracle dot com
2014-10-13 10:34 ` flast at flast dot jp
2014-10-13 11:59 ` manu at gcc dot gnu.org
[not found] <bug-11685-6528@http.gcc.gnu.org/bugzilla/>
2005-12-11 23:24 ` pinskia at gcc dot gnu dot org
[not found] <20030727171012.11685.pinskia@gcc.gnu.org>
2003-08-23 1:00 ` dhazeghi at yahoo dot com
2003-08-29 12:48 ` gdr at gcc dot gnu dot org
2003-08-29 12:50 ` pinskia at physics dot uc dot edu
2003-08-29 12:57 ` gdr at gcc dot gnu dot org
2003-08-29 14:51 ` bangerth at dealii dot org
2003-08-29 19:36 ` gdr at integrable-solutions dot net
2003-07-27 17:10 [Bug c++/11685] New: " pinskia at physics dot uc dot edu
2003-07-28 3:45 ` [Bug c++/11685] " pinskia at physics dot uc dot edu
2003-07-30 15:22 ` ehrhardt at mathematik dot uni-ulm dot de
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).