Hi Sun,
The -phase:p option seems doesn't make things any better, it still reports the
same error message.
-Xiaohua
________________________________
From: Sun Chan <sun.c...@gmail.com>
To: C. Bergström <cbergst...@pathscale.com>
Cc: open64-devel@lists.sourceforge.net
Sent: Fri, February 11, 2011 3:08:01 PM
Subject: Re: [Open64-devel] should we close bug588 as user error?
this issue has come up multiple times, even for other compilers in
another large company. Its about being able to build Linux at all opt
levels.
Xiaohua,
can you do an experiment, please use the following options "-O0
-phase:p" and see if the compile will go through.
Thx!
Sun
2011/2/12 "C. Bergström" <cbergst...@pathscale.com>:
> Suneel Jain wrote:
>> I thought that this reliance on the compiler doing dead code
>> elimination at all optimization levels is all over the Linux
>> kernel code.
>>
>> My recommendation would be to do this kind of dead code
>> elimination at -O0 in Open64. That will provide greater compatibility
>> with gcc.
>>
> Is there any benefit outside of gcc compatibility? What are the
> disadvantages? This broadly impacts *all* code that is/will be built
> with -O0 over 1 bad line of code. Someone should make a concise and
> clear decision about at which point compatibility makes sense. This
> seems like a knee jerk decision
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Open64-devel mailing list
> Open64-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/open64-devel
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
