Robert Dewar wrote: > >Right, so it seems quite appropriate to have two representations for > >source locations, one for the Ada tree, which is completely independent > >of the tree IL, and one for the back end. That probably means that back > >end messages will lose the generic instantiation information, but that's > >not terrible.
On Sun, May 14, 2006 at 03:32:49PM -0700, Per Bothner wrote: > First, the mapped source_location values can encode nested context. > This is used for the C/C++ include file context. I think it is quite > possible to use the same mechanism for generic instantiation > information. It would seem that C++ templates would have the same issues as Ada generic instantiation, right?
