Re: [C++ Patch] Another bunch of location fixes

On Mon, Sep 16, 2019 at 5:22 AM Paolo Carlini wrote: > > On 15/09/19 16:22, Jason Merrill wrote: > > On 9/12/19 9:41 AM, Paolo Carlini wrote: > >> + if (!valid_array_size_p (dname > >> + ? declarator->id_loc : input_location, > > > > Use the id_loc local variable? > > This d

Re: [C++ Patch] Another bunch of location fixes

Hi, On 15/09/19 16:22, Jason Merrill wrote: On 9/12/19 9:41 AM, Paolo Carlini wrote: +  if (!valid_array_size_p (dname +   ? declarator->id_loc : input_location, Use the id_loc local variable? This diagnostic is inside the loop over declarator->declarator. Eventually, o

Re: [C++ Patch] Another bunch of location fixes

On 9/12/19 9:41 AM, Paolo Carlini wrote: + if (!valid_array_size_p (dname + ? declarator->id_loc : input_location, Use the id_loc local variable? OK with that change. Jason

[C++ Patch] Another bunch of location fixes

Hi, nothing special here, various bits I missed so far or in the past meant to test more thoroughly. Thanks, Paolo. // /cp 2019-09-12 Paolo Carlini * decl.c (grokdeclarator): Use declspecs->locations and declarator->id_loc in a few error messages.

Re: [C++ Patch] Another bunch of location fixes for decl.c/decl2.c functions

OK. On Thu, Jun 14, 2018 at 10:48 AM, Paolo Carlini wrote: > Hi, > > tested x86_64 linux. > > Thanks, Paolo. > > /// >

[C++ Patch] Another bunch of location fixes for decl.c/decl2.c functions

Hi, tested x86_64 linux. Thanks, Paolo. /// /cp 2018-06-14 Paolo Carlini * decl.c (duplicate_decls): Use DECL_SOURCE_LOCATION in OPT_Wshadow warning_at. (grokfndecl): Consistently use the location_t argument in literal operator diagnostic