search for: subport

Hello I have serious problem with zhone z-plex 10 the device sometimes get red alarm on some channel and then the device suddenly shutdown. I try to unplugged the power chord and plug again, but the device still didn't up. I have to wait for long time to get this device up again. How can i fix this problem, so i can get this device immediately? Eris Riswanto

...rk in progress, but if I should file bugs, please let me know. > > This is probably not a very good idea because clang evolves in lock-step with LLVM. Unless the installed LLVM is the same revision as the clang you are building, They match revision. We just need to split the build into two subports to break dependency cycles, and I'm hoping to avoid rebuilding the core libraries a second time. > things are likely to not work due to internal API changes. The option you cite is more likely intended for when you build clang in a directory separate from LLVM (rather than when it is in ll...

On Wed, Jul 24, 2013 at 10:11 AM, Jeremy Huddleston Sequoia < jeremyhu at apple.com> wrote: > I recently took a stab at changing the MacPorts llvm-3.4 port from the > configure-based build system to the cmake-based build system. > Thanks for working on this! > 4) Building clang using installed llvm > > It looks like there is some support for building clang against an

...olved with a really simple hack. Consider a switch on i16 that codegens to a branch tree. This turns into a bunch of small blocks: the first zext's the value then does an unsigned comparison against the range typically, and each subsequent block does an unsigned comparison against the subportion of the range. The problem is that right now, the subsequent comparisons just see that the i16 value is promoted, which means the top bits are unknown. This means that each block ends up doing tons of redundant "and"s to clear out the top bits before their comparison. This i...

I know that this has been discussed (at least in passing) a few times on the list, but I couldn't locate a bug for it. Have any architectural plans been made for it? Are there architectural roadblocks with the current LLVM infrastructure that will complicate the process? What has demotivated the implementation of this so far (is it not that big a benefit on important targets, too

I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system. There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at bugs.llvm.org: 1) libclang_rt It looks like the cmake build is missing some runtime