similar to: PSA: llvm::cl now supports subcommands

Done: http://llvm.org/viewvc/llvm-project/cfe/branches/release_36/docs/ReleaseNotes.rst?view=markup#l113 We've been technically able to self-host for a some time, but now it's simple as 'CC=clang-cl CXX=clang-cl cmake'. =D On Wed, Feb 25, 2015 at 3:00 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > Nice. This should probably go to on the release notes :-)

Over the weekend I had a random urge to make clang-cl be able to self host. As of r230539, this should now be possible. Steps to try this out: 1) Run vcvarsall.bat, same as you would for an MSVC hosted build. 2) set CC=CXX=clang-cl (make sure it's in your path 3) Run CMake as you normally would, no special flags needed. 4) There is no 4, that's it! Currently LLD will not build, so if

Ok just tried on Win 7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is

FWIW, this test is passing for me on Windows 7 with Visual Studio 2015 (debug build). 59> Running all regression tests 59> -- Testing: 23734 tests, 32 threads -- 59> 59> Testing Time: 634.19s 59> Expected Passes : 22821 59> Expected Failures : 160 59> Unsupported Tests : 753 59> lit.py: lit.cfg:195: note: using clang:

Ah, I see this was addressed in 250386 - though might be nice to address across the whole project rather than this particular inclusion. Though maybe we've few enough inclusions that it's not too bad. On Fri, Oct 16, 2015 at 2:51 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Thu, Oct 15, 2015 at 2:17 AM, David Majnemer via llvm-commits < > llvm-commits at

Hi, This might be interesting since it seems to be the only LLVM test failing with VS 2015: FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) ******************** TEST 'LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** Script: -- llvm-pdbdump -symbols C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb |

Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = "usbhid-ups" ?? ?port =

Likely because 2.6.3 is not a current release. 2.7.2 (or 3?) is rhe current version, and it makes little sense to backport changes. Nut is a trivial compile . . . 'Use the source, Luke . . .' - Tim On October 17, 2014 6:05:35 PM CDT, Derek Harding <derek at lagham.org.uk> wrote: >Hi, > >Back in 2011, it was reported that Liebert PSA devices persist in >reporting OB

[FAQ on USB-connected UPSes] > Remember: this is brand new *experimental* software and is probably > very broken. Do us a favor and report successes or failures to > the mailing lists. No problem ... : UPS: Liebert PowerSure PSA 500 NUT: Version 2.0.2 Kernel: 2.6.11.5, with CONFIG_USB_HID, CONFIG_USB_HIDINPUT, and CONFIG_USB_HIDDEV compiled in (statically)

Hi, Back in 2011, it was reported that Liebert PSA devices persist in reporting OB (On Battery) when using usbhid-ups regardless of the actual state. Pier Paolo did some work (2011) which reportedly solved the issue. However, that doesn't seem to have reached mainstream and I now face the same problem. I'm using NUT 2.6.3 with a new Liebert PSA 1500Va that only ever reports OB and

Anyone have any advice what I need to do next? Regards, Paul. -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+paul=smithp.co.uk at lists.alioth.debian.org] On Behalf Of Charles Lepple Sent: 02 August 2013 11:36 To: nut-upsuser list Subject: [Nut-upsuser] Fwd: Liebert PSA UPS problem. Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA

This patch adds support for the following ups to liebert-hid.c: $ lsusb | grep Liebert Bus 007 Device 005: ID 10af:0001 Liebert Corp. PowerSure PSA UPS Using this patch, I'm able to obtain information about the ups via upsc: $ upsc upsname battery.charge: 100 battery.runtime: 1012 battery.type: PbAc battery.voltage: 1172 battery.voltage.nominal: 12 driver.name: usbhid-ups

Hi all, This is just a PSA that as of r302752, 3 parallel algorithms (for_each, for_each_n, and sort) are available in llvm/Support/Parallel.h. Effort was made to match the C++ Parallelism TS N4507 [ http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4507.pdf] as closely as possible, but some aspects were intentionally omitted. No support is added for the executor proposal N4406 [

I guess it's kind of a natural response on my part, working professionally in software. T-Shooting step one: Get current and see if the problem persists. If it does,then step rwo: debug. 2+ years is forever in software, noting that 2.6.3 was mid 2012 . . . - Tim On October 17, 2014 9:38:15 PM CDT, Charles Lepple <clepple at gmail.com> wrote: >On Oct 17, 2014, at 8:31 PM, Tim Dawson

Begin forwarded message: > From: "Paul Smith" > Subject: Liebert PSA UPS problem. > Date: July 31, 2013 4:42:33 PM EDT > To: <nut-upsuser at lists.alioth.debian.org> > > Hi all, > A brief summary: > > I have a new Liebert PSA UPS which I wanted to help support my FreeNAS box (a FreeBSD 8 variant). Unfortunately the nut-ups implementation here for

Hi all, several bots are currently experiencing an svn tree conflict when updating Updating '.': Skipped 'utils/lit/lit/llvm' -- Node remains in conflict Skipped 'utils/lit/lit/llvm' -- Node remains in conflict U utils/lit/lit/TestRunner.py U utils/lit/lit/util.py U test/lit.cfg U test/lit.site.cfg.in U cmake/modules/AddLLVM.cmake Updated to revision 313467. Summary of

Jochen Bern wrote: > > Peter Selinger wrote: > > have you been able to get your Liebert UPS to work? If I am correct, > > it should work with the newhidups Belkin subdriver. Could you please > > post your results? I am curious to know if this works or doesn't - and > > if yes, we should add permanent support for Liebert into NUT. > > I'm sorry, but

This is the last post in the old thread: http://lists.alioth.debian.org/pipermail/nut-upsuser/2011-February/006651.html I'm marginally reluctant to install a non-standard release on a customer server because I may not be the next person to have to work on it, however, I do agree the most recent is usually the first port-of-call. Since it seems the fix didn't get followed through,

http://netsystemsresearch.com/ dovecot.log.1.bz2:Jan 05 17:28:15 pop3-login: Info: Disconnected (no auth attempts in 3 secs): user=<>, rip=169.54.233.124, lip=MYIP, TLS handshaking: Disconnected, session=<z/L0OVxFetOpNul8> Their "research" pokes your email ports. Block if you want or participate in the (cough cough) research. IP addresses and opt-out email address on

I downloaded latest source and it compiles ok but the original usbhid-ups.c is unchanged. Pier changed other files, too, and I don't know the changes needed. Simply substituting the modified (as per 2011) usbhid-ups gives a failed connection to the ups. So I have tried a little. I'll uninstall 2.6.3 and try to install 2.7.2 from a fresh compile. Thanks for the responses so far :-) --