On 01/08/2010 05:00 PM, HyperQuantum wrote:
> Right?
>
Right, fixed.
Thanks,
Paolo.
In the list of changes for GCC 4.5 there's the following example:
#include
int main()
{
vector v;
for (int k = 0; k > 1024; ++k)
v.insert(v.begin(), k);
}
The declaration of v needs the 'std::' qualification, and the loop
test should use '<' instead of '>'.
Right?
On Fri, Jan 8, 2010 at 3:34 PM, Ian Lance Taylor wrote:
> "Paulo J. Matos" writes:
>
>> I just noticed that the pro_and_epilogue pass in gcc3.4.3 for certain
>> functions is ran multiple times with sibcalls enabled. Why is that?
>>
>> What I did was to put a printf on the epilogue and sibcall_epi
"Paulo J. Matos" writes:
> I just noticed that the pro_and_epilogue pass in gcc3.4.3 for certain
> functions is ran multiple times with sibcalls enabled. Why is that?
>
> What I did was to put a printf on the epilogue and sibcall_epilogue
> pattern so that during compilation it prints the name of
Hi all,
I just noticed that the pro_and_epilogue pass in gcc3.4.3 for certain
functions is ran multiple times with sibcalls enabled. Why is that?
What I did was to put a printf on the epilogue and sibcall_epilogue
pattern so that during compilation it prints the name of the function
currently gen
On Thu, Jan 7, 2010 at 5:29 PM, Dave Korn
wrote:
> Paulo J. Matos wrote:
>
>> The problem with this is that I only want to sibcall when it happens
>> to reduce my code size.
>>
>> I noticed (in the internals manual) we cannot actually fallback to a
>> normal call once we decide to sibcall through
Hi, all
I want to know every instructions an application runs.
So , first , I need to konw every basic blocks' frequency.
I'd like to use -fprofile-generate and -fprofile-use get basic block counts.
As GCC collect the profile information at pass-tree-profile,
I wander whither the instrumentat
