Displaying 5 results from an estimated 5 matches for "diassembling".
Did you mean:
disassembling
2014 Apr 07
9
[LLVMdev] 3.4.1 Release Plans
Hi Robert,
Can you ping the code owners about these patches. It might be good
to write a separate email per code owner and cc the appropriate -commits
list.
Thanks,
Tom
On Wed, Apr 02, 2014 at 06:16:44PM +0400, Robert Khasanov wrote:
> Hi Tom,
>
> I would like to nominate the following patches to be backported to 3.4.1
>
> Clang:
> 1. r204742 - Zinovy Nis <zinovy.nis at
2012 Feb 14
3
ftrace_enabled set to 1 on bootup, slow downs with CONFIG_FUNCTION_TRACER in virt environments?
Hey,
I was running some benchmarks (netserver/netperf) where the init script just launched
the netserver and nothing else and was concerned to see the performance not up to par.
This was an HVM guest running with PV drivers.
If I compile the kernel without CONFIG_FUNCTION_TRACER it is much better - but it was
my understanding that the tracing code does not impact the machine unless it is
2014 Apr 08
2
[LLVMdev] 3.4.1 Release Plans
On Tue, Apr 08, 2014 at 04:08:13PM +0400, Robert Khasanov wrote:
> Hi Reid,
>
> Would you approve your patches r203146 and r202774 to be backported to
> 3.4.1? They fix stability issues in x86 asm.
>
Hi Robert,
I was able to merge r203146, but it used a c++11 feature:
std::string::back() which I replaced with
std::string::at(std::string::size() - 1).
r202774 was not merged,
2003 Nov 03
1
Intel Performance Primitives
Hey all,
For those of you who are really worried about asterisk performance, I
thought I might alert you to a "toy" you might play around with. The Intel
Performance Primitives contain a number of optimized functions for use in
digital signal processing that could help with echo cancellation, codec
transformations, etc. I don't have any idea how useful this would be in
Real
2014 Mar 26
19
[LLVMdev] 3.4.1 Release Plans
Hi,
We are now about halfway between the 3.4 and 3.5 releases, and I would
like to start preparing for a 3.4.1 release. Here is my proposed release
schedule:
Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch.
April 9 - April 18: Testing Phase
April 18: 3.4.1 Release
How you can help:
- If you have any bug fixes you think should be included to 3.4.1, send
me an