similar to: Use case of undef

Sanjoy, You have changed the subject. We still need real world examples showing how taking advantage of “undef” results in beneficial optimization. My belief is that they don’t exist, my reasoning is this: real world programmers are likely to run UBSan before compiling (or if they don’t they should), therefore it is highly unlikely that any “undef” will actually exist during

All, These discussions seem to be based on the premise that there is a need for the compiler to exploit undefined behavior for performance optimization reasons. So far the only beneficial optimization I am aware of that relies on some form of “undefined” is Dan Gohman’s original project for LP64 targets of promoting i32 induction variables to i64 and hoisting sign-extension out of the

Hi, I know this is the wrong forum for this kind of question and is only ephemerally related to xapian, but maybe someone here knows and will save me some digging. Given a google PR of, say, .15 for page A of site x.com, does google "radiate" any of that PR goodness onto any other pages of site x.com? Irrespective of whether page A links to any other pages in site x.com. In other

Can't I upload the 3PCC firmware ? available from the Cisco website? Actually it came with sip88xx.... firmware. Regards . On Fri, 2 Dec 2016, 10:38 p.m. Steve Davies, <davies147 at gmail.com> wrote: > Hi, > > You have to buy the 3PCC version for this to work. Once you have this, > they work very much like the Cisco SPA handsets. > > I also ended up with a non-3PCC

Dear All, I've had a lot of progress on my 6502 family target, but I've hit a bit of a stumbling block wherein some passes inadvertently cause malformed final instruction listings. It's not necessarily llvm's fault, though. An example: %a<def> = COPY %w04 asl_a_16_once %a<imp-def>, %n_flag<imp-def,dead>, %z_flag<imp-def,dead>,

Hi, I'm using the lattice function 'barchart' to make a series of 4 histograms. Currently, the y-axis values are graphed in order of the y-axis variable. I'd like to have the y-axis values sorted in ascending order of the x-axis values so that the longest bar horizontally is on top of the graph (in it's seciton) and the shortest bar is on the bottom. I can do this in

No, the disable-xmldoc doesn't disable the whole doc creating procedure. Is there a way to disable it completely? Regarding the issue... Of course, I Can open a ticket, just I don't know about what exactly. I want to compile it without doc generate to make the asterisk module loads up fine. On Dec 4, 2016 8:41 PM, "Joshua Colp" <jcolp at digium.com> wrote: > On Sun,

Hi, I tried to run the make progdocs, but the first time, it said, I have no doxygen installed. So I compiled the latest release and reconfigure the asterisk. And after it, ut sucessfully started to build the docs. But it took a lot of time, So finally I aborted the process... Is there a way to disable doc creating? The --disable-xmldoc is enough? Thanks! On Dec 2, 2016 3:36 PM, "Joshua

Actually now I have the phones with SIP firmware. I will try with 3pcc firmware along with XML files. Or any idea if we have CUCM application can we change the firmware. am ready to buy the developer edition. Regards . On Mon, 5 Dec 2016, 3:34 p.m. Steve Davies, <davies147 at gmail.com> wrote: > I tried... repeatedly... I failed. I bought some 3PCC phones, and they > just worked.

Hello LLVMDev, I'm George, an intern for Google who will be working on LLVM. Currently, I'm starting to implement a set-based Alias Analysis algorithm for LLVM, which looks like it may be more accurate than Steensgard's, and can be constructed in approximately nlog(n) time and linear space (n = number of memory locations; queries happen in constant time). It will most likely be

Here's the failing tests for rc2 on SLES11.3 (glibc 2.11, libstdc++4.7). I've done some amount of triaging what some critical elements of the failures are. Unabridged log is attached. Failing Tests (94): LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool LLVM-Unit ::

Hello, Is there any exist LLVM Target (backend) that support PC relative load and store? If so, what exactly is the instruction? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191204/c345ac5c/attachment.html>

FYI found this example while reading: https://github.com/jameysharp/corrode/issues/30#issuecomment-231969365 and compared it with current gcc 6.2, clang 3.9 gcc 6.2 result is quite small - clang 3.9 produces much much more code for this example https://godbolt.org/g/uWxr8F is that a missing optimization opportunity or just wrong behavior of the optimizer?

Dear everyone, There's still plenty of time left, but I'd like to get the schedule set before folks start disappearing for the holidays. Note that this release will also switch us to the new versioning scheme where the major version is incremented for each major release (i.e., when the 4.0 branch is created, trunk will become 5.0). If you'd like to help providing binaries and

Hello all, I am willing to do "eliminating the void type" project. Is there anyone working on it? === Overview === The general concept is to replaced void with {}. And 'ret void' is a synonym of 'ret {} {}.' === Further Implementation Details === 1. Deleting VoidTyID 2. Deleting LLVMVoidTypeKind (one-to-one relation between VoidTyID and LLVMVoidTypeKind) 3. Use

This patch fixes lines with 4 spaces instead of 1 tab char. -------------- next part -------------- A non-text attachment was scrubbed... Name: cpu_h_tabs.patch Type: application/octet-stream Size: 1909 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/flac-dev/attachments/20161204/b59e5b70/attachment.obj>

This patch removes check for OS SSE support. (I assume that all OSes that are usable today support SSE, so this complicated check in cpu.c is not needed). -------------- next part -------------- A non-text attachment was scrubbed... Name: remove_OS_SSE_check.patch Type: application/octet-stream Size: 8206 bytes Desc: not available URL:

Hello all, I noticed Eliminating the 'void' type<http://nondot.org/sabre/LLVMNotes/EliminatingVoid.txt>in Random LLVM notes. I am wondering to know what's the meaning of "eliminating" the void type. Is it means the goal is deleting VoidTyID from TypeID enumeration in Type.h? And what Type::getVoidTy() returned is a pointer to a {}? Thanks Mitnick -------------- next

Hello Chris, The general concept is to replace void with {}. Void is a weird type in > that it is only allowed as the return value of functions and as the type of > instructions like store. It seems better (though also not particularly > high priority) to eliminate it to make the type system more consistent. > > -Chris > I also noticed a sentence "We can even make

Hello Chris The general concept is to replace void with {}. Void is a weird type in >> that it is only allowed as the return value of functions and as the type of >> instructions like store. It seems better (though also not particularly >> high priority) to eliminate it to make the type system more consistent. >> > MVT::isVoid and Type::VoidTyID (getVoidTy) have