From: Robert Dewar <dewar@gnat.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Joe Buck <Joe.Buck@synopsys.COM>, Geert Bosch <bosch@gnat.com>,
Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Question/proposal for USE_MAPPED_LOCATION and Ada
Date: Wed, 06 Oct 2004 23:30:00 -0000 [thread overview]
Message-ID: <41647ED8.4080307@gnat.com> (raw)
In-Reply-To: <200410070115.36397.stevenb@suse.de>
Steven Bosscher wrote:
> On Thursday 07 October 2004 01:03, Robert Dewar wrote:
>
>>I would think so, but I am not aware of the capability in C++
>>of having an error message refer to the template location and
>>to chain of locations where the template is instantiated.
>>Perhaps I just don't know :-)
>
>
> C++ gives you something like this:
>
> /usr/include/g++-2/stl_deque.h:747: warning: comparison between signed and unsigned
> /usr/include/g++-2/stl_deque.h: In method `void deque<int,__default_alloc_template<true,0>,0>::reserve_map_at_front<int, alloc, 0>(unsigned int = 1)':
> /usr/include/g++-2/stl_deque.h:1219: instantiated from `deque<int,__default_alloc_template<true,0>,0>::new_elements_at_front<int, alloc, 0>(unsigned int)'
> /usr/include/g++-2/stl_deque.h:609: instantiated from `deque<int,__default_alloc_template<true,0>,0>::reserve_elements_at_front<int, alloc, 0>(unsigned int)'
> /usr/include/g++-2/stl_deque.h:947: instantiated from `deque<int,__default_alloc_template<true,0>,0>::insert<__deque_iterator<int,const int &,const int &,0>>(__deque_iterator<int,int &,int *,0>, __deque_iterator<int,const int &,const int &,0>, __deque_iterator<int,const int &,const int &,0>, forward_iterator_tag)'
> /usr/include/g++-2/stl_deque.h:508: instantiated from `deque<int,__default_alloc_template<true,0>,0>::insert<__deque_iterator<int,const int &,const int &,0>>(__deque_iterator<int,int &,int *,0>, __deque_iterator<int,const int &,const int &,0>, __deque_iterator<int,const int &,const int &,0>)'
> /usr/include/g++-2/stl_deque.h:424: instantiated from `deque<int,__default_alloc_template<true,0>,0>::operator =<int, alloc, 0>(const deque<int,__default_alloc_template<true,0>,0> &)'
> t.cc:3: instantiated from here
> /usr/include/g++-2/stl_deque.h:638: warning: comparison between signed and unsigned
>
> Is that what you mean with "chain of locations"?
Yes, indeed, sorry, I was not aware of this, last time I tried, I did not get this.
SO, that means that it should be possible to map the Ada into the same kind of
structure. Is there no provision for column numbers? That seems a pity.
>
> Gr.
> Steven
next prev parent reply other threads:[~2004-10-06 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 21:07 Richard Kenner
2004-10-06 22:03 ` Geert Bosch
2004-10-06 22:21 ` Steven Bosscher
2004-10-06 23:04 ` Robert Dewar
2004-10-06 23:09 ` Joe Buck
2004-10-06 23:16 ` Robert Dewar
2004-10-06 23:25 ` Steven Bosscher
2004-10-06 23:30 ` Robert Dewar [this message]
2004-10-07 2:31 ` James A. Morrison
2004-10-07 6:24 ` Robert Dewar
2004-10-06 23:26 Richard Kenner
2004-10-07 11:21 ` Giovanni Bajo
2004-10-07 15:42 Richard Kenner
2004-10-07 16:01 ` Giovanni Bajo
2004-10-07 18:28 ` Robert Dewar
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=41647ED8.4080307@gnat.com \
--to=dewar@gnat.com \
--cc=Joe.Buck@synopsys.COM \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=stevenb@suse.de \
/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).