--- Comment #54 from jason at gcc dot gnu dot org 2009-07-29 21:09 ---
Thanks for the testcase, the patch I just checked in should fix it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #53 from jason at gcc dot gnu dot org 2009-07-29 20:36 ---
Subject: Bug 14912
Author: jason
Date: Wed Jul 29 20:35:40 2009
New Revision: 150223
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150223
Log:
PR c++/14912
* cp-tree.h (enum tsubst_flags): Ad
--- Comment #52 from arekm at pld-linux dot org 2009-07-26 10:38 ---
btw. this patch backported to gcc 4.4 [1] causes build problems with -g flags
like: https://svn.boost.org/trac/boost/ticket/3287
I just tested gcc trunk and the problem is the same.
How to test? On linux x86_64 (it's
--- Comment #51 from jason at gcc dot gnu dot org 2009-04-09 20:30 ---
Patch applied for 4.5.
--
jason at gcc dot gnu dot org changed:
What|Removed |Added
Sta
--- Comment #50 from jason at gcc dot gnu dot org 2009-04-05 19:29 ---
Subject: Bug 14912
Author: jason
Date: Sun Apr 5 19:29:02 2009
New Revision: 145566
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=145566
Log:
PR c++/14912
* error.c (count_non_default_templa
--- Comment #49 from jason at gcc dot gnu dot org 2009-04-05 06:06 ---
I think it's best to just leave the default arguments in when pretty-printing a
function template specialization, as in the string example; otherwise we won't
know what _Alloc in the function parameter list means.
Ju
--- Comment #48 from pluto at agmk dot net 2009-03-23 19:00 ---
with the latest patch applied on top of 4.4-svn i get
following diagnostic for simple code snippet:
$ cat 14912-2.cpp
#include
std::string s = 7;
$ /opt/gcc44/bin/g++ -c -Wall -O2 14912-2.cpp
14912-2.cpp:2: error: invalid
--- Comment #47 from jason at gcc dot gnu dot org 2009-03-03 18:55 ---
Created an attachment (id=17392)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17392&action=view)
updated patch that fixes ICE
Here's an update of the patch that fixes the ICE; we need to set
processing_templat
--- Comment #46 from hjl dot tools at gmail dot com 2009-03-02 21:59
---
(In reply to comment #42)
> Created an attachment (id=16389)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16389&action=view) [edit]
> internal-error-testcase
>
I got
gnu-6:pts/4[294]> ./xgcc -B./ -S /tmp/
--- Comment #45 from pluto at agmk dot net 2009-03-02 21:04 ---
bug ping...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #44 from pluto at agmk dot net 2008-09-25 13:20 ---
i can reproduce this internal error on both 4.3.1 and 4.3-head.
here's a backtrace:
Breakpoint 1, error_recursion (context=0x10aeb40) at
../../gcc-4_3-branch/gcc/diagnostic.c:637
637 if (context->lock < 3)
(gdb) p *co
--- Comment #43 from b0ntrict0r at yandex dot ru 2008-09-23 14:31 ---
(In reply to comment #42)
> Created an attachment (id=16389)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16389&action=view) [edit]
> internal-error-testcase
>
Hm... I can reproduce it with gcc 4.3.2 and canno
--- Comment #42 from pluto at agmk dot net 2008-09-23 10:13 ---
Created an attachment (id=16389)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16389&action=view)
internal-error-testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #41 from pluto at agmk dot net 2008-09-23 10:12 ---
and the lastest patch causes internal error in cc1plus in my codebase:
$
/local/devel/toolchain43/x86_64-gnu-linux.host64.diag/bin/x86_64-gnu-linux-g++
smsSimClock.ii -c -std=gnu++0x
Internal compiler error: Error reportin
--- Comment #40 from pluto at agmk dot net 2008-09-22 21:54 ---
(In reply to comment #39)
> Created an attachment (id=16380)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16380&action=view) [edit]
> Updated fixed
>
1). still there is a warning:
../../gcc/cp/error.c: In function
--- Comment #39 from b0ntrict0r at yandex dot ru 2008-09-22 15:12 ---
Created an attachment (id=16380)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16380&action=view)
Updated fixed
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #38 from pluto at agmk dot net 2008-09-22 09:21 ---
(In reply to comment #37)
> Created an attachment (id=16361)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16361&action=view) [edit]
> Updated patch
>
> Could someone test updated patch?
>
it doesn't build.
../../g
--- Comment #37 from b0ntrict0r at yandex dot ru 2008-09-19 12:22 ---
Created an attachment (id=16361)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16361&action=view)
Updated patch
Could someone test updated patch?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #36 from pluto at agmk dot net 2007-10-15 14:04 ---
could someone update this patch for 4.3?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Comment #35 from pcarlini at suse dot de 2007-10-12 11:04 ---
*** Bug 33747 has been marked as a duplicate of this bug. ***
--
pcarlini at suse dot de changed:
What|Removed |Added
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-27 03:16 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| (In reply to comment #31)
|
| > >Patched:
| > >test.cc: In membe
--- Additional Comments From dave at boost-consulting dot com 2005-03-27
01:52 ---
This is obviously becoming personal. I wanted a record of my technical concerns
in the bug database, but as the tone has changed I don't think it's appropriate
to continue this here. I will reply to Gaby
--- Additional Comments From giovannibajo at libero dot it 2005-03-27
00:56 ---
(In reply to comment #31)
> >Patched:
> >test.cc: In member function 'void A::foo() [with T = int]':
> >test.cc:14: instantiated from here
> >test.cc:9: error: 'class std::vector' has no member
named '
--- Additional Comments From bangerth at dealii dot org 2005-03-26 22:57
---
Giovanni, in your example in comment #27, you get this:
>Patched:
>test.cc: In member function 'void A::foo() [with T = int]':
>test.cc:14: instantiated from here
>test.cc:9: error: 'class std::vector' h
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 19:52 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From giovannibajo at libero dot it 2005-03-26
19:26 ---
Another comparison:
---
#include
template
struct A
{
std::vector v;
void foo(void)
{ v.doesnotexist(); }
};
void foo(void)
{
A a;
a.foo();
}
-
--- Additional Comments From giovannibajo at libero dot it 2005-03-26
19:24 ---
OK, before I clean up the patch, I'll post an example. For this code:
--
#include
#include
#include
std::map > m;
void bar(void)
{
std::vector k;
m.insert
--- Additional Comments From dave at boost-consulting dot com 2005-03-26
16:14 ---
This is obviously becoming personal. I wanted a record of my technical concerns
in the bug database, but as the tone has changed I don't think it's appropriate
to continue this here. I will reply to Gaby
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 15:55 ---
Subject: Re: Do not print default template arguments in error messages
"dave at boost-consulting dot com" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From dave at boost-consulting dot c
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 15:40 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From dave at boost-consulting dot com 2005-03-26
12:57 ---
Subject: Re: Do not print default template arguments in error messages
"gdr at integrable-solutions dot net" <[EMAIL PROTECTED]> writes:
> --- Additional Comments From gdr at integrable-solutions do
--- Additional Comments From giovannibajo at libero dot it 2005-03-26
11:59 ---
Subject: Re: Do not print default template arguments in error messages
gdr at integrable-solutions dot net <[EMAIL PROTECTED]> wrote:
The first patch will deal with just removal of default
argume
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 04:13 ---
Subject: Re: Do not print default template arguments in error messages
"dave at boost-consulting dot com" <[EMAIL PROTECTED]> writes:
[...]
| Please, I'm begging you not to go down this road. GCC i
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 04:06 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-26 04:04 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From dave at boost-consulting dot com 2005-03-26
02:01 ---
Subject: Re: Do not print default template arguments in error messages
"gdr at integrable-solutions dot net" <[EMAIL PROTECTED]> writes:
> --- Additional Comments From gdr at integrable-solutions do
--- Additional Comments From giovannibajo at libero dot it 2005-03-26
00:35 ---
(In reply to comment #12)
> Look at the most general template and same_type_p() with any default
> type.
How can it work? The default parameter can be dependent on previous template
parameters. For insta
--- Additional Comments From giovannibajo at libero dot it 2005-03-26
00:30 ---
(In reply to comment #14)
> | The first patch will deal with just removal of default
> | arguments, and I believe that the less intrusive and clean solution is to
> | display in the "with" clause.
> pleas
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-25 22:11 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| I cannot fix all the diagnostic problems in GCC with a single patc
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-25 22:09 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-25 22:09 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| The first non-trivial issue is that, in order to print "std::vecto
--- Additional Comments From gdr at integrable-solutions dot net
2005-03-25 22:06 ---
Subject: Re: Do not print default template arguments in error messages
"giovannibajo at libero dot it" <[EMAIL PROTECTED]> writes:
| --- Additional Comments From giovannibajo at libero dot it 20
--- Additional Comments From giovannibajo at libero dot it 2005-03-24
02:15 ---
(In reply to comment #9)
> Doesn't sound right to me. [...]
> GCC ought to have a heuristic based on the lengths of the version with
> the "with" clause and the version with a full argument substitution, to
--- Additional Comments From dave at boost-consulting dot com 2005-03-23
12:55 ---
Doesn't sound right to me.
I think you should either show vector or include A in the "with" clause of
vector. I'm sort of inclined to the former; Don't forget that parameter
names are not always so sho
--- Additional Comments From giovannibajo at libero dot it 2005-03-23
11:01 ---
or maybe:
test.cc: In member function `void A::foo() [with T = int, int N =
, int X = ]':
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14912
--- Additional Comments From giovannibajo at libero dot it 2005-03-23
10:51 ---
The first non-trivial issue is that, in order to print "std::vector"
instead of "std::vector >", we need to do the template
substitution at error printing time, and check if the resulting substitution
matc
--- Additional Comments From dave at boost-consulting dot com 2005-03-23
04:55 ---
"should GCC try and remember which arguments were really specified in the
template-id (hard to do), or a simple check of equalness between the argument
and the default parameter would suffice?"
GCC shou
--- Additional Comments From giovannibajo at libero dot it 2005-03-23
02:44 ---
I'll try to do this. This is a simple testcase:
---
template
struct A
{
typedef typename T::x x;
};
void foo(void)
{
A a;
}
---
test.cc: At global scope:
48 matches
Mail list logo
