search for: _significantly_

...onses are correlated, and thus that the rating task makes sense to people. Is there a standard approach to this? With only 2 people, the correlation coefficient between their responses would be an interpretable number, (though probably there is some stronger way to assess whether the results are _significantly_ correlated). With N>2 people, there is the correlation matrix, but it does not give a nice single number. Thinking, the determinant of the matrix of response vectors might be a possibility, since it will be low if the rows are correlated. Though, it should be normalized somehow to be interpre...

...all-back Well, we use fixed-point mode by default in Firefox for both Firefox OS and Fennec (Firefox on Android). The reason is that, although there is some NEON-class hardware where float does finally appear to be a little bit faster (e.g., recent A9's), there are still plenty where it is _significantly_ slower. So if you're going to pick one version to run on many devices, fixed-point has much better worst-case performance.

...reproducing all the things that are required/used from an ELF shared object during linking -- symbol type, binding-type, visibility, version, alignment (!), .gnu.warning messages, various important "SHT_NOTE" sections, and whatever other things I've forgotten about, will need to be a _significantly_ different format than what Apple has as their "TBD" format. Apple's format also has a bunch of special cases in it to make it easier to use for their platform, but a rather less generic tool. E.g., symbols starting with "_OBJC_CLASS_$" are recorded in the "objc-classes&...

...ll, we use fixed-point mode by default in Firefox for both Firefox OS and > Fennec (Firefox on Android). The reason is that, although there is some NEON- > class hardware where float does finally appear to be a little bit faster (e.g., > recent A9's), there are still plenty where it is _significantly_ slower. So if > you're going to pick one version to run on many devices, fixed-point has much > better worst-case performance. -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please n...

Hello there, I'm a little afraid of writing here, hope I don't make any mistake doing so. I'm trying for days and searching the web too, but no obvious solution, no reply from the specialized forum I wrote in. Here is the situation: I would like to have a lighter security inside our domain, without changing when going outside. By "lighter security" I mean at least, no

...nto nice tight loops. 12. The LICM pass can now sink computations out the bottom of loops in addition to hoisting them out the top. This reduces the amount of computation in loops and reduces register pressure. 13. The "-basicaa" alias analysis pass (the default) is now _significantly_ more precise in many common cases (see PR86). 14. The startup time of the LLVM JIT has been improved quite a bit for programs that have lots of globals with pointers to functions (such as C++ vtables). For example, running "ll-opt --help" (LLVM opt, compiled with LLVM) sped...

I am making some progress on my Centos 5 notebook build. So I am looking at Firefox and Thunderbird 2.0. Should I install them? Or is Redhat correct that there is nothing improved here and wait for 3.0? (well I have not even had a chance to look at Thunderbird 2.0, that is new)? I have the install steps we covered here back on 2/2/07; but are there rpms? I did not find anything over at

..., as LLVM provides features to make such external implementations possible and in some rare cases (calling conventions) it includes project specific patches to allow such projects to use a vanilla LLVM installation. This intrinsic was proposed in the very same light. I think it would be nice to _significantly_ facilitate the development of optimizers that target GPGPU accelerators. Yabin's project would use this, but I am convinced a wider audience could use this. A design that handles multiple bitcode files does not seem like a good option. It would require large changes to all projects that wan...

Hi, I am working on DSP module of Ne10. I see there are fixed-point and floating-point FFT inside Opus. Is fixed-point FFT only a fall back for CPU without VFP? On ARMv7-A and ARMv8-A, benchmark result shows that fixed-point (int32) and floating-point (float32) FFT have similar performance. I guess fixed-point version is not often used on these platforms. Is it worth the effort to NEON-optimize

Benifits of TBD: 1) It's human readable and diffs on TBDs correspond to changes in the ABI. Diffs can be automatically added to review processes to ensure that changes to the ABI are reviewed. The TBDs also document your precise ABI. 2) The size is smaller which means they can be shipped in an SDK instead of binaries to reduce the size of an SDK 3) Stubs are producible from TBDs (or should be)

On Mon, Apr 9, 2018 at 10:11 PM, John Ericson via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Regardless of any of that, given that TBD files _are_ an integral part > of the apple platform, supporting them is certainly a necessity in order to > have a working apple linker. So, if making LLD work for Apple/MachO is the > justification for adding TBD support to LLVM, that

On May 8, 2012, at 2:08 AM, Tobias Grosser wrote: > On 05/08/2012 05:13 AM, Evan Cheng wrote: >> Sorry Tobias, I'm not in favor of this change. From what I can tell, this enables some features which can implemented via other means. It adds all kinds of complexity to LLVM and I'm also highly concerned about bitcode that can embed illegal (or worse malicious) code using this