Re: c++: Module-specific error and tree dumping

2020-12-09 Thread David Malcolm via Gcc-patches
On Wed, 2020-12-09 at 16:07 -0500, Nathan Sidwell wrote: > On 12/9/20 3:41 PM, David Malcolm wrote: > > On Wed, 2020-12-09 at 15:20 -0500, Nathan Sidwell wrote: > > > With modules, we need the ability to name 'foos' in different > > > modules. > > > The idiom for that is a trailing '@modulename' su

Re: c++: Module-specific error and tree dumping

2020-12-09 Thread Nathan Sidwell
On 12/9/20 3:41 PM, David Malcolm wrote: On Wed, 2020-12-09 at 15:20 -0500, Nathan Sidwell wrote: With modules, we need the ability to name 'foos' in different modules. The idiom for that is a trailing '@modulename' suffix. Out of curiosity, is this idiom shared with other compilers? (or in th

Re: c++: Module-specific error and tree dumping

2020-12-09 Thread David Malcolm via Gcc-patches
On Wed, 2020-12-09 at 15:20 -0500, Nathan Sidwell wrote: > With modules, we need the ability to name 'foos' in different > modules. > The idiom for that is a trailing '@modulename' suffix. Out of curiosity, is this idiom shared with other compilers? (or in the standard) > This adds that > t

c++: Module-specific error and tree dumping

2020-12-09 Thread Nathan Sidwell
With modules, we need the ability to name 'foos' in different modules. The idiom for that is a trailing '@modulename' suffix. This adds that to the error printing routines. I also augment the tree dumping machinery to show module-specific metadata. gcc/cp/ * error.c (dump_module