Re: 'walk_stmt_load_store_addr_ops' for non-'gimple_assign_single_p (stmt)'

2021-03-16 Thread Thomas Schwinge
Hi! Thanks, Michael, and again Richard for your quick responses. On 2021-03-16T15:25:10+, Michael Matz wrote: > On Tue, 16 Mar 2021, Thomas Schwinge wrote: > >> >>Indeed, given (Fortran) 'zzz = 1', we produce GIMPLE: >> >> >> >>gimple_assign >> >> >> >>..., and calling 'walk_stmt_load_s

Re: 'walk_stmt_load_store_addr_ops' for non-'gimple_assign_single_p (stmt)'

2021-03-16 Thread Michael Matz
Hello, On Tue, 16 Mar 2021, Thomas Schwinge wrote: > >>Indeed, given (Fortran) 'zzz = 1', we produce GIMPLE: > >> > >>gimple_assign > >> > >>..., and calling 'walk_stmt_load_store_addr_ops' on that, I see, as > >>expected, the 'visit_store' callback invoked, with 'rhs' and 'arg': > >>''. > >

Re: 'walk_stmt_load_store_addr_ops' for non-'gimple_assign_single_p (stmt)'

2021-03-16 Thread Richard Biener via Gcc
On Tue, Mar 16, 2021 at 4:02 PM Thomas Schwinge wrote: > > Hi! > > Richard, thanks for your answer. I'll need to look into this more; two > questions already: > > On 2021-03-15T20:17:17+0100, Richard Biener via Gcc wrote: > > On March 15, 2021 7:31:46 PM GMT+01:00, Thomas Schwinge > > wrote: >

Re: 'walk_stmt_load_store_addr_ops' for non-'gimple_assign_single_p (stmt)'

2021-03-16 Thread Thomas Schwinge
Hi! Richard, thanks for your answer. I'll need to look into this more; two questions already: On 2021-03-15T20:17:17+0100, Richard Biener via Gcc wrote: > On March 15, 2021 7:31:46 PM GMT+01:00, Thomas Schwinge > wrote: >>First time I'm using this API -- so the error certainly may be on my >>

Re: Question on special constraint variables in points-to analysis

2021-03-16 Thread Richard Biener via Gcc
On Tue, Mar 16, 2021 at 1:16 PM Erick Ochoa via Gcc wrote: > > Hello, > > I'm currently working on improving my understanding of the implementation > of the intraprocedural points-to analysis in GCC. I have already read the > papers by Daniel Berlin and have been looking at the source for some tim

Question on special constraint variables in points-to analysis

2021-03-16 Thread Erick Ochoa via Gcc
Hello, I'm currently working on improving my understanding of the implementation of the intraprocedural points-to analysis in GCC. I have already read the papers by Daniel Berlin and have been looking at the source for some time, but I understand that those references are a little bit old and migh

Re: printf: Ambiguous warning

2021-03-16 Thread Jonathan Wakely via Gcc
On Tue, 16 Mar 2021 at 10:47, Rene Kita wrote: > > On Tue, Mar 16, 2021 at 11:26:29AM +0100, Jakub Jelinek wrote: > > On Tue, Mar 16, 2021 at 11:20:05AM +0100, Rene Kita wrote: > > > % gcc -Wall -Wpedantic main.c > > > main.c: In function 'main': > > > main.c:10:16: warning: format '%hn' expects a

GCC 11.0.1 Status Report (2021-03-16)

2021-03-16 Thread Richard Biener
Status == GCC trunk which eventually will become GCC 11 is still in regression and documentation fixes only mode (Stage 4). If history should repeat itself then a first release candidate of GCC 11 will be released mid April. For this to happen we need to resolve the remaining 17 P1 regress

Re: printf: Ambiguous warning

2021-03-16 Thread Rene Kita
On Tue, Mar 16, 2021 at 11:26:29AM +0100, Jakub Jelinek wrote: > On Tue, Mar 16, 2021 at 11:20:05AM +0100, Rene Kita wrote: > > % gcc -Wall -Wpedantic main.c > > main.c: In function 'main': > > main.c:10:16: warning: format '%hn' expects argument of type 'short int *', > > but argument 2 has type

Re: printf: Ambiguous warning

2021-03-16 Thread Jakub Jelinek via Gcc
On Tue, Mar 16, 2021 at 11:20:05AM +0100, Rene Kita wrote: > (Please keep me CC'd, I'm not subscribe to the list) > > Here is a minimal example: > #include > > int > main() > { > unsigned short n; > unsigned short *p; > p = &n; > > printf("p: %hn\n", p); > } > > > % gcc -Wall -Wpedant

printf: Ambiguous warning

2021-03-16 Thread Rene Kita
(Please keep me CC'd, I'm not subscribe to the list) Here is a minimal example: #include int main() { unsigned short n; unsigned short *p; p = &n; printf("p: %hn\n", p); } % gcc -Wall -Wpedantic main.c main.c: In function 'main': main.c:10:16: warning: format '%hn' expects argument of

Re: Failing in generated file options.c

2021-03-16 Thread Jonathan Wakely via Gcc
On Tue, 16 Mar 2021, 08:53 Martin Liška, wrote: > On 3/16/21 3:39 AM, Gary Oblock via Gcc wrote: > > > > > > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and contains information > that is confidential and proprietary t

Re: Failing in generated file options.c

2021-03-16 Thread Martin Liška
On 3/16/21 3:39 AM, Gary Oblock via Gcc wrote: Guys, I checked out a fresh copy of the GCC sources today, applied somebodies patch to it and voila! options.c:13591:2: error: #error Report option property is dropped #error Report option property is dropped I built this the same minimally convo

Failing in generated file options.c

2021-03-16 Thread Erick Ochoa via Gcc
Hi Gary, the options.c file is generated from the gcc/common.opt file. Report was a keyword that could be given to optimization options but which was dropped sometime in December I think. The patches I sent you should have the keyword Report dropped. Are you applying your sources already? If not,

Re: Failing in generated file options.c

2021-03-16 Thread Andrew Pinski via Gcc
On Mon, Mar 15, 2021 at 7:41 PM Gary Oblock via Gcc wrote: > > Guys, > > I checked out a fresh copy of the GCC sources today, applied somebodies > patch to it and voila! > > options.c:13591:2: error: #error Report option property is dropped #error > Report option property is dropped > > I built t