On Tue, May 10, 2011 at 4:20 PM, Ian Lance Taylor wrote:
> fanqifei writes:
>
Which file or fucntion should I look into? Maybe I can work around in 4.3.2
>>>
>>> Look into tree-ssa-alias.c and tree-ssa-structalias.c
>>>
What change in 4.5 fixed it?
>>>
>>> A complete rewrite of the abov
fanqifei writes:
>>> Which file or fucntion should I look into? Maybe I can work around in 4.3.2
>>
>> Look into tree-ssa-alias.c and tree-ssa-structalias.c
>>
>>> What change in 4.5 fixed it?
>>
>> A complete rewrite of the above ...
>>
>> Richard.
> So is there easy way to work around in 4.3.2
>> Which file or fucntion should I look into? Maybe I can work around in 4.3.2
>
> Look into tree-ssa-alias.c and tree-ssa-structalias.c
>
>> What change in 4.5 fixed it?
>
> A complete rewrite of the above ...
>
> Richard.
So is there easy way to work around in 4.3.2 to disable the randomization?
On Tue, May 10, 2011 at 1:43 PM, fanqifei wrote:
> On Tue, May 10, 2011 at 6:23 PM, Richard Guenther
> wrote:
>> On Tue, May 10, 2011 at 12:08 PM, fanqifei wrote:
>>> Hi all,
>>>
>>> I am poring gcc 4.3.2 for a micro-controller and use it to compile C
>>> source code.
>>> I found that gcc is ver
On Tue, May 10, 2011 at 6:23 PM, Richard Guenther
wrote:
> On Tue, May 10, 2011 at 12:08 PM, fanqifei wrote:
>> Hi all,
>>
>> I am poring gcc 4.3.2 for a micro-controller and use it to compile C
>> source code.
>> I found that gcc is very sensitive to small changes in C source code
>> even if the
On Tue, May 10, 2011 at 12:08 PM, fanqifei wrote:
> Hi all,
>
> I am poring gcc 4.3.2 for a micro-controller and use it to compile C
> source code.
> I found that gcc is very sensitive to small changes in C source code
> even if the change doesn't affect any function of the source code.
> For exam
Hi all,
I am poring gcc 4.3.2 for a micro-controller and use it to compile C
source code.
I found that gcc is very sensitive to small changes in C source code
even if the change doesn't affect any function of the source code.
For example, a source file foo.c includes a header file foo.h.
If one ma