gcc-9-20200925 is now available

2020-09-25 Thread GCC Administrator via Gcc
Snapshot gcc-9-20200925 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20200925/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

[PATCH v3] : Add nitems()

2020-09-25 Thread Alejandro Colomar via Gcc
'nitems()' calculates the length of an array in number of items. It is safe: if a pointer is passed to the macro (or function, in C++), the compilation is broken due to: - In >= C11: _Static_assert() - In C89, C99: Negative anonymous bitfield - In C++: The template requires an array Some BSDs a

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Alejandro Colomar via Gcc
On 2020-09-25 19:39, Jonathan Wakely wrote: > Yes, I'm aware of all the rationale. I already said that it makes > sense in C++ where you have generic code. I am not convinced that it's > necessary to add to when all it does is a cast from > size_t to ptrdiff_t. > While I would prefer a signed

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Jonathan Wakely via Gcc
On 25/09/20 18:30 +0200, Alejandro Colomar via Libstdc++ wrote: I have a similar number of ARRAY_SIZE() and ARRAY_SSIZE(). I could have '#define snitems(arr) ((ptrdiff_t)nitems(arr))' in my projects, but is it really necessary? The barrier for adding something to glibc headers should be a LOT h

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Jonathan Wakely via Gcc
On 25/09/20 18:30 +0200, Alejandro Colomar via Libstdc++ wrote: Hello Jonathan, On 2020-09-25 16:48, Jonathan Wakely wrote: Do you really need to provide snitems? Users can use (ptrdiff_t)nitems if needed, can't they? They can, but that adds casts in the code, which makes longer lines that a

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Alejandro Colomar via Gcc
Hello Jonathan, On 2020-09-25 16:48, Jonathan Wakely wrote: > Do you really need to provide snitems? > > Users can use (ptrdiff_t)nitems if needed, can't they? They can, but that adds casts in the code, which makes longer lines that are somewhat harder to read. To avoid that, users may sometimes

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Jonathan Wakely via Gcc
On 25/09/20 16:10 +0200, Alejandro Colomar wrote: On 2020-09-25 15:20, Alejandro Colomar wrote: 'nitems()' calculates the length of an array in number of items. It is safe: if a pointer is passed to the macro (or function, in C++), the compilation is broken due to: - In >= C11: _Static_asser

Re: [PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Alejandro Colomar via Gcc
On 2020-09-25 15:20, Alejandro Colomar wrote: > 'nitems()' calculates the length of an array in number of items. > It is safe: if a pointer is passed to the macro (or function, in C++), > the compilation is broken due to: > - In >= C11: _Static_assert() > - In C89, C99: Negative anonymous b

[PATCH v2] : Add nitems() and snitems() macros

2020-09-25 Thread Alejandro Colomar via Gcc
'nitems()' calculates the length of an array in number of items. It is safe: if a pointer is passed to the macro (or function, in C++), the compilation is broken due to: - In >= C11: _Static_assert() - In C89, C99: Negative anonymous bitfield - In C++: The template requires an array 'snitems()'

Re: On IPA-PTA field sensitivity and pointer expressions

2020-09-25 Thread Richard Biener via Gcc
On Fri, Sep 25, 2020 at 2:27 PM Erick Ochoa wrote: > > > > On 25/09/2020 13:30, Richard Biener wrote: > > On Fri, Sep 25, 2020 at 9:05 AM Erick Ochoa > > wrote: > >> > >> Hi, > >> > >> I am working on an alias analysis using the points-to information > >> generated during IPA-PTA. If we look at t

Re: On IPA-PTA field sensitivity and pointer expressions

2020-09-25 Thread Erick Ochoa
On 25/09/2020 13:30, Richard Biener wrote: On Fri, Sep 25, 2020 at 9:05 AM Erick Ochoa wrote: Hi, I am working on an alias analysis using the points-to information generated during IPA-PTA. If we look at the varmap varinfo_t array in gcc/tree-ssa-struct.c, most of the constraint variable i

Re: On IPA-PTA field sensitivity and pointer expressions

2020-09-25 Thread Richard Biener via Gcc
On Fri, Sep 25, 2020 at 9:05 AM Erick Ochoa wrote: > > Hi, > > I am working on an alias analysis using the points-to information > generated during IPA-PTA. If we look at the varmap varinfo_t array in > gcc/tree-ssa-struct.c, most of the constraint variable info structs > contain a non-null decl f

Re: [patch, doc] Update people who can review gfortran patches

2020-09-25 Thread Tobias Burnus
On 9/25/20 8:02 AM, Thomas Koenig via Fortran wrote: for review of its patches, gfortran relies on a group of people who can approve patches.  Unfortuntately, many of them are not active. Others, who have the capability and who have acted as de facto approvers (without anybody minding) are missi

On IPA-PTA field sensitivity and pointer expressions

2020-09-25 Thread Erick Ochoa
Hi, I am working on an alias analysis using the points-to information generated during IPA-PTA. If we look at the varmap varinfo_t array in gcc/tree-ssa-struct.c, most of the constraint variable info structs contain a non-null decl field which points to a valid tree in gimple (which is an SSA