Yes, Thanks for the information!
On Fri, Aug 22, 2014 at 1:53 PM, Jian-Xin Lai <laij...@gmail.com> wrote:
> This is a issue in 5.0 and fixed in trunk if compiled with the latest GCC
> compiler. Here is the diff for rev 3941:
> Index: lego.cxx
> ===================================================================
> --- lego.cxx (revision 3940)
> +++ lego.cxx (revision 3941)
> @@ -390,13 +390,13 @@
> static void Delete_All_Distr_Pragmas () {
>
> for (INT i=0; i<da_stack->Elements(); i++) {
> DISTR_INFO* dinfo = da_stack->Bottom_nth(i);
> - INT i;
> - for (i=0; i<dinfo->Num_Dact(); i++) {
> - DISTR_ARRAY* dact = dinfo->Get_Dact(i);
> + INT j;
> + for (j=0; j<dinfo->Num_Dact(); j++) {
> + DISTR_ARRAY* dact = dinfo->Get_Dact(j);
> Delete_Distr_Pragmas (dact);
> }
> - for (i=0; i<dinfo->Num_Gen_Redistr(); i++) {
> - DISTR_ARRAY* dact = dinfo->Get_Gen_Redistr(i);
> + for (j=0; j<dinfo->Num_Gen_Redistr(); j++) {
> + DISTR_ARRAY* dact = dinfo->Get_Gen_Redistr(j);
> Delete_Distr_Pragmas (dact);
> }
> }
>
> Basically, it renames the inner i into j.
>
>
>
> 2014-08-22 11:59 GMT+08:00 Nancy <nancydream...@gmail.com>:
>>
>> Hi Christopher,
>>
>> > nihao Nancy - I would encourage you to try to fix the errors yourself.
>> > Somewhere in a makefile will be "CG:all_sched" that you can grep for and
>> > remove. This error is caused by gcc not understanding the flag.
>>
>> I do not find the CG:all_sched under my build-open64 directory, maybe
>> hardcode in sourcecode. I use "make V=1" , remove that parameter
>> manually to build that .o for a walk around.
>>
>> A new ISSUE:
>> C++
>> /home/nancy/work/build-open64/osprey/targdir/lno//home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx
>> In file included from /usr/include/c++/4.8/ext/hash_map:60:0,
>> from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/common/com/strtab.h:146,
>> from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/common/com/symtab.h:75,
>> from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/common/com/pu_info.h:52,
>> from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx:46:
>> /usr/include/c++/4.8/backward/backward_warning.h:32:2: warning:
>> #warning This file includes at least one deprecated or antiquated
>> header which may be removed without further notice at a future date.
>> Please use a non-deprecated interface with equivalent functionality
>> instead. For a listing of replacement headers and interfaces, consult
>> the file backward_warning.h. To disable this warning use
>> -Wno-deprecated. [-Wcpp]
>> #warning \
>> ^
>> In file included from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lnopt_main.h:708:0,
>> from
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx:54:
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/common/com/config_lno.h:397:1:
>> warning: ‘typedef’ was ignored in this declaration [enabled by
>> default]
>> };
>> ^
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx:
>> In function ‘void Delete_All_Distr_Pragmas()’:
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx:393:9:
>> error: redeclaration of ‘INT i’
>> INT i;
>> ^
>>
>> /home/nancy/work/build-open64/osprey/../../open64-5.0/./osprey/be/lno/lego.cxx:391:12:
>> error: ‘INT i’ previously declared here
>> for (INT i=0; i<da_stack->Elements(); i++) {
>> ^
>> make[3]: *** [lego.o] 错误 1
>> make[3]:正在离开目录 `/home/nancy/work/build-open64/osprey/targdir/lno'
>> make[2]: *** [default] 错误 2
>> make[2]:正在离开目录 `/home/nancy/work/build-open64/osprey/targdir/lno'
>> make[1]: *** [lno.so] 错误 2
>> make[1]:正在离开目录 `/home/nancy/work/build-open64'
>> make: *** [build] 错误 2
>>
>>
>>
>> > Alternatively, you may want to figure out why gcc is being used when the
>> > build expects opencc.
>> The frond-end of open64 is GCC-4.2.0. Is that the correct answer?
>>
>>
>> > Furthermore, this project is basically dead and understanding your goals
>> > may
>> > help others point you in the right direction. If you're doing research
>> > or
>> > paid work for IA64 - you may not have any other reasonable choice. If
>> > however you're targeting another platform there may be other options.
>> I'm a newcomer in compiler area with huge passion. There's an opened
>> open64 backend job opportunity in my city. I hope I can join them,
>> just make some preparation. I known LLVM is more popular and active,
>> but lack of job opportunity here. I think join a local professional
>> team very important for my grow. No matter it is GCC, LLVM, Open64 or
>> any others. I think each of them have special strongpoint and
>> weakness. The same main principle but different trade-offs
>> implementation make them special and beautiful just the way they are.
>>
>> --
>> Best Regards,
>> Yu Rong Tan
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds. Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Open64-devel mailing list
>> Open64-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/open64-devel
>
>
>
>
> --
> Regards,
> Lai Jian-Xin
--
Best Regards,
Yu Rong Tan
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
