From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17990 invoked by alias); 10 Jun 2010 20:04:44 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 17979 invoked by uid 22791); 10 Jun 2010 20:04:43 -0000 X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4C114221.7000500@redhat.com> Date: Thu, 10 Jun 2010 20:04:00 -0000 From: sami wagiaalla User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 MIME-Version: 1.0 To: archer@sourceware.org Subject: Re: Template function support References: <4C11323B.9030302@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2010-q2/txt/msg00041.txt.bz2 > I thought perhaps you'd have a new LOC_TEMPLATE, then add a new symbol > with that class. Then when you do a lookup for "foo" you can tell that > it is a "phony" symbol that represents a template. Finally, the > symbol's value union could have a new field that points to all the > instantiations. > > Alternatively such a symbol could just store a type that has a new > TYPE_CODE_. I'm not sure whether this would be any better. > > I'm not sure that this is sane and/or easily implemented. > Thanks for the pointers! I don't know which way I'll go. The TYPE_CODE approach was the only thing I came up with, but I will look into both. > Sami> + return c != NULL&& strchr (name, '>')> c; > > I don't think you really need that second clause there. > This is to avoid matching things like operator< operator<=, and operator<<. Come to think of it the second clause should be strchr (c, '>') != NULL > I didn't look too closely at all of it. Make sure that psymbol changes > don't poison the bcache, and that lookups that find a name like this > don't do the wrong thing elsewhere in gdb. > Will do. I am not sure I understand this mechanism well, but I'll figure it out. Thanks, Sami