Build failure in fixincludes on x86_64

2021-05-26 Thread Uros Bizjak via Gcc
The build currently fails to build for me on x86_64 in fixincludes:

/home/uros/gcc-build/./gcc/xgcc -B/home/uros/gcc-build/./gcc/
-B/usr/local/x86_64-pc-linux-gnu/bin/
-B/usr/local/x86_64-pc-linux-gnu/lib/ -isystem
/usr/local/x86_64-pc-linux-gnu/include -isystem
/usr/local/x86_64-pc-linux-gnu/sys-include-c -g -O2 -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wmissing-format-attribute
-Wno-overlength-strings -pedantic -Wno-long-long   -DHAVE_CONFIG_H -I.
-I../../git/gcc/fixincludes -I../include
-I../../git/gcc/fixincludes/../include
../../git/gcc/fixincludes/fixtests.c
during GIMPLE pass: evrp
../../git/gcc/fixincludes/fixtests.c: In function ‘run_test’:
../../git/gcc/fixincludes/fixtests.c:155:1: internal compiler error:
in operator[], at vec.h:890
 155 | }
 | ^
0x7e4ed0 vec::operator[](unsigned int)
   ../../git/gcc/gcc/vec.h:890
0x7e509e vec::operator[](unsigned int)
   ../../git/gcc/gcc/tree.h:3366
0x7e509e vec::operator[](unsigned int)
   ../../git/gcc/gcc/vec.h:1461
0x7e509e range_def_chain::register_dependency(tree_node*, tree_node*,
basic_block_def*)
   ../../git/gcc/gcc/gimple-range-gori.cc:179
0x1825ffc fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
   ../../git/gcc/gcc/gimple-range.cc:439
0x18292c5 fold_using_range::fold_stmt(irange&, gimple*, fur_source&, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:376
0x18295e2 gimple_ranger::fold_range_internal(irange&, gimple*, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:1067
0x18295e2 gimple_ranger::range_of_stmt(irange&, gimple*, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:1097
0x18256ca gimple_ranger::range_of_expr(irange&, tree_node*, gimple*)
   ../../git/gcc/gcc/gimple-range.cc:980
0x1825e07 fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
   ../../git/gcc/gcc/gimple-range.cc:431
0x18292c5 fold_using_range::fold_stmt(irange&, gimple*, fur_source&, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:376
0x18295e2 gimple_ranger::fold_range_internal(irange&, gimple*, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:1067
0x18295e2 gimple_ranger::range_of_stmt(irange&, gimple*, tree_node*)
   ../../git/gcc/gcc/gimple-range.cc:1097
0x18256ca gimple_ranger::range_of_expr(irange&, tree_node*, gimple*)
   ../../git/gcc/gcc/gimple-range.cc:980
0x110a121 range_query::value_of_expr(tree_node*, gimple*)
   ../../git/gcc/gcc/value-query.cc:86
0x1834491 hybrid_folder::value_of_expr(tree_node*, gimple*)
   ../../git/gcc/gcc/gimple-ssa-evrp.c:235
0xfb9d33 substitute_and_fold_engine::replace_uses_in(gimple*)
   ../../git/gcc/gcc/tree-ssa-propagate.c:575
0xfba04c substitute_and_fold_dom_walker::before_dom_children(basic_block_def*)
   ../../git/gcc/gcc/tree-ssa-propagate.c:845
0x17fb85f dom_walker::walk(basic_block_def*)
   ../../git/gcc/gcc/domwalk.c:309
0xfb94d5 substitute_and_fold_engine::substitute_and_fold(basic_block_def*)
   ../../git/gcc/gcc/tree-ssa-propagate.c:987
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.
make: *** [Makefile:76: fixtests.o] Error 1

Is this known failure?

Uros.


Re: Build failure in fixincludes on x86_64

2021-05-26 Thread Richard Earnshaw via Gcc




On 26/05/2021 13:22, Uros Bizjak via Gcc wrote:

The build currently fails to build for me on x86_64 in fixincludes:

/home/uros/gcc-build/./gcc/xgcc -B/home/uros/gcc-build/./gcc/
-B/usr/local/x86_64-pc-linux-gnu/bin/
-B/usr/local/x86_64-pc-linux-gnu/lib/ -isystem
/usr/local/x86_64-pc-linux-gnu/include -isystem
/usr/local/x86_64-pc-linux-gnu/sys-include-c -g -O2 -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wmissing-format-attribute
-Wno-overlength-strings -pedantic -Wno-long-long   -DHAVE_CONFIG_H -I.
-I../../git/gcc/fixincludes -I../include
-I../../git/gcc/fixincludes/../include
../../git/gcc/fixincludes/fixtests.c
during GIMPLE pass: evrp
../../git/gcc/fixincludes/fixtests.c: In function ‘run_test’:
../../git/gcc/fixincludes/fixtests.c:155:1: internal compiler error:
in operator[], at vec.h:890
  155 | }
  | ^


Same failure on arm.

R.


0x7e4ed0 vec::operator[](unsigned int)
../../git/gcc/gcc/vec.h:890
0x7e509e vec::operator[](unsigned int)
../../git/gcc/gcc/tree.h:3366
0x7e509e vec::operator[](unsigned int)
../../git/gcc/gcc/vec.h:1461
0x7e509e range_def_chain::register_dependency(tree_node*, tree_node*,
basic_block_def*)
../../git/gcc/gcc/gimple-range-gori.cc:179
0x1825ffc fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
../../git/gcc/gcc/gimple-range.cc:439
0x18292c5 fold_using_range::fold_stmt(irange&, gimple*, fur_source&, tree_node*)
../../git/gcc/gcc/gimple-range.cc:376
0x18295e2 gimple_ranger::fold_range_internal(irange&, gimple*, tree_node*)
../../git/gcc/gcc/gimple-range.cc:1067
0x18295e2 gimple_ranger::range_of_stmt(irange&, gimple*, tree_node*)
../../git/gcc/gcc/gimple-range.cc:1097
0x18256ca gimple_ranger::range_of_expr(irange&, tree_node*, gimple*)
../../git/gcc/gcc/gimple-range.cc:980
0x1825e07 fold_using_range::range_of_range_op(irange&, gimple*, fur_source&)
../../git/gcc/gcc/gimple-range.cc:431
0x18292c5 fold_using_range::fold_stmt(irange&, gimple*, fur_source&, tree_node*)
../../git/gcc/gcc/gimple-range.cc:376
0x18295e2 gimple_ranger::fold_range_internal(irange&, gimple*, tree_node*)
../../git/gcc/gcc/gimple-range.cc:1067
0x18295e2 gimple_ranger::range_of_stmt(irange&, gimple*, tree_node*)
../../git/gcc/gcc/gimple-range.cc:1097
0x18256ca gimple_ranger::range_of_expr(irange&, tree_node*, gimple*)
../../git/gcc/gcc/gimple-range.cc:980
0x110a121 range_query::value_of_expr(tree_node*, gimple*)
../../git/gcc/gcc/value-query.cc:86
0x1834491 hybrid_folder::value_of_expr(tree_node*, gimple*)
../../git/gcc/gcc/gimple-ssa-evrp.c:235
0xfb9d33 substitute_and_fold_engine::replace_uses_in(gimple*)
../../git/gcc/gcc/tree-ssa-propagate.c:575
0xfba04c substitute_and_fold_dom_walker::before_dom_children(basic_block_def*)
../../git/gcc/gcc/tree-ssa-propagate.c:845
0x17fb85f dom_walker::walk(basic_block_def*)
../../git/gcc/gcc/domwalk.c:309
0xfb94d5 substitute_and_fold_engine::substitute_and_fold(basic_block_def*)
../../git/gcc/gcc/tree-ssa-propagate.c:987
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.
make: *** [Makefile:76: fixtests.o] Error 1

Is this known failure?

Uros.



Re: Build failure in fixincludes on x86_64

2021-05-26 Thread Andreas Schwab
On Mai 26 2021, Uros Bizjak via Gcc wrote:

> The build currently fails to build for me on x86_64 in fixincludes:

https://gcc.gnu.org/pipermail/gcc-patches/2021-May/571274.html

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."


RE: [EXTERNAL] Re: State of AutoFDO in GCC

2021-05-26 Thread Eugene Rozenfeld via Gcc
3.0.0 is the latest supported version on Ubuntu 18.04. I verified that the 
build works on Ubuntu 20.04 with  protobuf-compiler and libprotobuf-dev version 
3.6.1.3.

Eugene

-Original Message-
From: Wei Mi  
Sent: Tuesday, May 25, 2021 8:07 PM
To: Eugene Rozenfeld 
Cc: Andi Kleen ; Hongtao Yu ; Xinliang David 
Li ; Jan Hubicka ; gcc@gcc.gnu.org; Wenlei 
He 
Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC

I checked the source of protobuf 3.0.0 and it didn't contain the operator[] in 
RepeatedField. Need to install a newer version of protobuf.

Thanks,
Wei.

On Tue, May 25, 2021 at 1:49 PM Eugene Rozenfeld 
 wrote:
>
> Both are 3.0.0-9.1ubuntu1:
>
> eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list 
> protobuf-compiler Listing... Done protobuf-compiler/bionic,now 
> 3.0.0-9.1ubuntu1 amd64 [installed] 
> eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list 
> libprotobuf-dev Listing... Done libprotobuf-dev/bionic,now 
> 3.0.0-9.1ubuntu1 amd64 [installed]
>
> -Original Message-
> From: Wei Mi 
> Sent: Tuesday, May 25, 2021 9:17 AM
> To: Eugene Rozenfeld 
> Cc: Andi Kleen ; Hongtao Yu ; Xinliang 
> David Li ; Jan Hubicka ; 
> gcc@gcc.gnu.org; Wenlei He 
> Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC
>
> It looks like some version problem about protobuf-compiler and 
> libprotobuf-dev. Could you check what is the installed version on your end 
> for those two packages and see if they are consistent?
>
> On my platform, they are both 3.12.4.
>
> On Tue, May 25, 2021 at 12:01 AM Eugene Rozenfeld 
>  wrote:
> >
> > That eliminates the previous error but there is a new one:
> >
> > eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [3/199] 
> > Building CXX object 
> > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quip
> > pe
> > r/perf_reader.cc.o
> > FAILED: 
> > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> > /usr/bin/c++   -I../third_party/perf_data_converter/src 
> > -I../third_party/perf_data_converter/src/quipper -I../ 
> > -I../third_party/glog/src -I../third_party/abseil -I../util -I. 
> > -Ithird_party/glog -std=gnu++1z -MD -MT 
> > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> >  -MF 
> > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o.d
> >  -o 
> > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> >  -c ../third_party/perf_data_converter/src/quipper/perf_reader.cc
> > ../third_party/perf_data_converter/src/quipper/perf_reader.cc: In member 
> > function 'bool 
> > quipper::PerfReader::ReadCPUTopologyMetadata(quipper::DataReader*, size_t)':
> > ../third_party/perf_data_converter/src/quipper/perf_reader.cc:1518:46: 
> > error: no match for 'operator[]' (operand types are 'const 
> > google::protobuf::RepeatedField' and 'int')
> >  nrcpus = proto_uint32_metadata.data()[0];
> >
> > -Original Message-
> > From: Wei Mi 
> > Sent: Monday, May 24, 2021 8:54 PM
> > To: Eugene Rozenfeld 
> > Cc: Andi Kleen ; Hongtao Yu ; 
> > Xinliang David Li ; Jan Hubicka 
> > ; gcc@gcc.gnu.org; Wenlei He 
> > Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC
> >
> > It isn't exposed on my platform either. Looks like a bug in 
> > perf_data_converter (i.e., quipper). Could you try adding #include 
> >  in 
> > third_party/perf_data_converter/src/quipper/huge_page_deducer.cc and see if 
> > it fixes the problem? If it works, I will need to file a bug against 
> > perf_data_converter.
> >
> > Thanks,
> > Wei.
> >
> > On Mon, May 24, 2021 at 8:33 PM Eugene Rozenfeld 
> >  wrote:
> > >
> > > That fixed the error I saw before but the build still fails. The 
> > > errors start with
> > >
> > >
> > >
> > > eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja
> > >
> > > [2/217] Building CXX object
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/qu
> > > ip
> > > pe
> > > r/huge_page_deducer.cc.o
> > >
> > > FAILED:
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/qu
> > > ip
> > > pe
> > > r/huge_page_deducer.cc.o
> > >
> > > /usr/bin/c++   -I../third_party/perf_data_converter/src 
> > > -I../third_party/perf_data_converter/src/quipper -I../ 
> > > -I../third_party/glog/src -I../third_party/abseil -I../util -I. 
> > > -Ithird_party/glog -std=gnu++1z -MD -MT 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o
> > >  -MF 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o.d
> > >  -o 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o
> > >  -c ../third_party/perf_data_converter/src/quipper/huge_page_deducer.cc
> > >
> > > ../third_party/perf_data_converter/src/quipper/huge_page_deducer.cc:
> > > 14
> > > 4:26: error: 'unordered_map' in namespace 'std' does not name a 
> > > template type
> > >
> > >

Re: [EXTERNAL] Re: State of AutoFDO in GCC

2021-05-26 Thread Wei Mi via Gcc
Thanks. Good to know the build works with newer protobuf.

Wei.

On Wed, May 26, 2021 at 4:40 PM Eugene Rozenfeld
 wrote:
>
> 3.0.0 is the latest supported version on Ubuntu 18.04. I verified that the 
> build works on Ubuntu 20.04 with  protobuf-compiler and libprotobuf-dev 
> version 3.6.1.3.
>
> Eugene
>
> -Original Message-
> From: Wei Mi 
> Sent: Tuesday, May 25, 2021 8:07 PM
> To: Eugene Rozenfeld 
> Cc: Andi Kleen ; Hongtao Yu ; Xinliang 
> David Li ; Jan Hubicka ; gcc@gcc.gnu.org; 
> Wenlei He 
> Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC
>
> I checked the source of protobuf 3.0.0 and it didn't contain the operator[] 
> in RepeatedField. Need to install a newer version of protobuf.
>
> Thanks,
> Wei.
>
> On Tue, May 25, 2021 at 1:49 PM Eugene Rozenfeld 
>  wrote:
> >
> > Both are 3.0.0-9.1ubuntu1:
> >
> > eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list
> > protobuf-compiler Listing... Done protobuf-compiler/bionic,now
> > 3.0.0-9.1ubuntu1 amd64 [installed]
> > eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list
> > libprotobuf-dev Listing... Done libprotobuf-dev/bionic,now
> > 3.0.0-9.1ubuntu1 amd64 [installed]
> >
> > -Original Message-
> > From: Wei Mi 
> > Sent: Tuesday, May 25, 2021 9:17 AM
> > To: Eugene Rozenfeld 
> > Cc: Andi Kleen ; Hongtao Yu ; Xinliang
> > David Li ; Jan Hubicka ;
> > gcc@gcc.gnu.org; Wenlei He 
> > Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC
> >
> > It looks like some version problem about protobuf-compiler and 
> > libprotobuf-dev. Could you check what is the installed version on your end 
> > for those two packages and see if they are consistent?
> >
> > On my platform, they are both 3.12.4.
> >
> > On Tue, May 25, 2021 at 12:01 AM Eugene Rozenfeld 
> >  wrote:
> > >
> > > That eliminates the previous error but there is a new one:
> > >
> > > eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [3/199]
> > > Building CXX object
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quip
> > > pe
> > > r/perf_reader.cc.o
> > > FAILED: 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> > > /usr/bin/c++   -I../third_party/perf_data_converter/src 
> > > -I../third_party/perf_data_converter/src/quipper -I../ 
> > > -I../third_party/glog/src -I../third_party/abseil -I../util -I. 
> > > -Ithird_party/glog -std=gnu++1z -MD -MT 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> > >  -MF 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o.d
> > >  -o 
> > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o
> > >  -c ../third_party/perf_data_converter/src/quipper/perf_reader.cc
> > > ../third_party/perf_data_converter/src/quipper/perf_reader.cc: In member 
> > > function 'bool 
> > > quipper::PerfReader::ReadCPUTopologyMetadata(quipper::DataReader*, 
> > > size_t)':
> > > ../third_party/perf_data_converter/src/quipper/perf_reader.cc:1518:46: 
> > > error: no match for 'operator[]' (operand types are 'const 
> > > google::protobuf::RepeatedField' and 'int')
> > >  nrcpus = proto_uint32_metadata.data()[0];
> > >
> > > -Original Message-
> > > From: Wei Mi 
> > > Sent: Monday, May 24, 2021 8:54 PM
> > > To: Eugene Rozenfeld 
> > > Cc: Andi Kleen ; Hongtao Yu ;
> > > Xinliang David Li ; Jan Hubicka
> > > ; gcc@gcc.gnu.org; Wenlei He 
> > > Subject: Re: [EXTERNAL] Re: State of AutoFDO in GCC
> > >
> > > It isn't exposed on my platform either. Looks like a bug in 
> > > perf_data_converter (i.e., quipper). Could you try adding #include 
> > >  in 
> > > third_party/perf_data_converter/src/quipper/huge_page_deducer.cc and see 
> > > if it fixes the problem? If it works, I will need to file a bug against 
> > > perf_data_converter.
> > >
> > > Thanks,
> > > Wei.
> > >
> > > On Mon, May 24, 2021 at 8:33 PM Eugene Rozenfeld 
> > >  wrote:
> > > >
> > > > That fixed the error I saw before but the build still fails. The
> > > > errors start with
> > > >
> > > >
> > > >
> > > > eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja
> > > >
> > > > [2/217] Building CXX object
> > > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/qu
> > > > ip
> > > > pe
> > > > r/huge_page_deducer.cc.o
> > > >
> > > > FAILED:
> > > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/qu
> > > > ip
> > > > pe
> > > > r/huge_page_deducer.cc.o
> > > >
> > > > /usr/bin/c++   -I../third_party/perf_data_converter/src 
> > > > -I../third_party/perf_data_converter/src/quipper -I../ 
> > > > -I../third_party/glog/src -I../third_party/abseil -I../util -I. 
> > > > -Ithird_party/glog -std=gnu++1z -MD -MT 
> > > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o
> > > >  -MF 
> > > > CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o.d
> > > >  -o 
> > 

Re: Build failure in fixincludes on x86_64

2021-05-26 Thread Gerald Pfeifer
On Wed, 26 May 2021, Richard Earnshaw via Gcc wrote:
>> ../../git/gcc/fixincludes/fixtests.c: In function ‘run_test’:
>> ../../git/gcc/fixincludes/fixtests.c:155:1: internal compiler error:
>> in operator[], at vec.h:890
>>   155 | }
>>   | ^
> Same failure on arm.

Same failure on x86 (32-bit, i586-unknown-freebsd11.4).

Gerald


shutterstock

2021-05-26 Thread Perspective via Gcc
Dear Sir,
There are more than 700 illustrations here, find the railway station you
need.
*https://www.shutterstock.com/g/Amjad+Hossain?rid=230688451&utm_medium=email&utm_source=ctrbreferral-link
*

Best Regards
Amjad Hossain
CEO Perspective
House 503, Unit(402) Road 9,DOHS,
Baridhara, Dhaka, Bangladesh
Mobile: +88-01711015924
amzaddes...@gmail.com



Best Regards


*Amjad Hossain*
   CEO
Perspective | House 503, Unit(402) Road 9,DOHS, Baridhara, Dhaka, Bangladesh
   |   Mobile: +88-0162-1407006 | amzaddes...@gmail.com |
perspectivedr...@gmail.com | http://www.perspective-bd.com

[image: beacon]