similar to: [LLVMdev] Options on code generator

Dimitry Andric <dimitry <at> andric.com> writes: > > On 2010-06-15 18:28, Sunay Ismail wrote: > > I read on web that llvm compiles itself with clang, but could not find the > > instruction to achieve that. I try "./configure CC=clang CXX=clang" but get link > > errors. > > Try using CXX=clang++ instead. Always use clang++ for C++ code. :)

I read on web that llvm compiles itself with clang, but could not find the instruction to achieve that. I try "./configure CC=clang CXX=clang" but get link errors. How can I do it?

On 2010-06-15 18:28, Sunay Ismail wrote: > I read on web that llvm compiles itself with clang, but could not find the > instruction to achieve that. I try "./configure CC=clang CXX=clang" but get link > errors. Try using CXX=clang++ instead. Always use clang++ for C++ code. :)

Hello all! I have found following empty files that get installed (v3.4rc2) : docs/llvm/html/Dummy.html include/clang/Driver/CC1Options.h What is the story behind them? Or were they just forgotten? Can we (someone) remove these? Cheers, Gabor

In crossbow, each mac_srs has a kernel thread called "mac_rx_srs_poll_ring" to poll the hardware and crossbow will wakeup this thread to poll packets from the hardware automatically. Does crossbow provide any method to disable the polling mechanism, for example disabling the this kernel thread? Thanks Zhihui -------------- next part -------------- An HTML attachment was scrubbed... URL:

Team, We are trying to install Crossbow on VirtualBox. Siva first tried it on Linux and reported it in Hyderabad Open Solaris User Group alias. http://opensolaris.org/os/project/hosug/ Today both of us tried it on VirtualBox running on OpenSolaris. Both attempts have the same results. a. Selecting Solaris Developer Express during boot process exits the installation. See this picture:

I have an OpenLDAP backend, Samba knows how to talk to it, my Samba users are stored in LDAP and file shares work fine authenticating to the LDAP server. I tried executing smbldap-useradd -w server02 on the command-line and got the following error: failed to perform search; Can't contact LDAP server at /usr/lib/perl5/vendor_perl/5.8.7/smbldap_tools.pm line 362, <DATA> line 283. Error

Hi. After running with the crossbow bits for a while, I discovered that the network management port on my T1000 wasn''t working properly (no link light). When logging in on the serial management port and running "resetsc", I got this: --->8--- ALOM POST 1.0 Dual Port Memory Test, PASSED. TTY External - Internal Loopback Test TTY External - Internal Loopback Test, PASSED.

I recently updated to snv_125 and now bridged networks for my VirtualBox guests can''t move any network traffic. I''ve tried both VirtualBox 3.0.4 and 3.0.8 with no success. Any ideas? Thanks, Gordon -- This message posted from opensolaris.org

Recently I found that the mac_srs_rx_poll_ring thread may never stop in kernel, please see the following mpstat, cpu 2 is in 100% kernel usage, but no syscalls and no interrupts. CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 0 0 0 0 300 100 0 0 1 0 0 0 0 0 0 100 1 14 0 0 134 68 134 1

Howdy, I just finished reading through the Crossbow presentation: http://blogs.sun.com/sunay/resource/crossbow.pdf And have one question. If you create a virtual NIC with dladm: $ dladm create-vnic -d bge0 -m 0:1:2:3:4:5 -b 10000 1 Can you then add vnic1 directly to the zone? e.g.: zonecfg -z zone1 zonecfg:zone1> create zonecfg:zone1> set zonepath=/zones/zone1 zonecfg:zone1> add net

I''ve been thinking about hardware that has multiple transmit rings ("tx resources"). We really should have a way to expose this up to the stack. And ideally, the stack should guarantee that a given flow will always be sent down using the same hardware tx resource. I''ve heard that crossbow will deliver this, but I can''t find evidence of it in the crossbow

Hi, I maintain a driver for a 10GbE nic which supports multiple hardware tx/rx rings. We can steer rx packets into rings using the "standard" NDIS6 Toeplitz hashing on TCP port numbers, IP addresses, etc. We can also steer packets based on MAC address. Would this NIC be considered to be capable of supporting crossbow? Also, can crossbow do things like steer outgoing packets to the

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 |

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:

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

Guys, OK, now that we have the new core contributors squared away, we can go back to finishing the contributors list. There were some people who got added and then there is existing contributors list. I think Darren''s suggestion to wait to add new core contributors is fine (let the new constitution settle down and we can in the meanwhile have a more inclusive look at both rather than

On Fri, Jan 15, 2016 at 11:05 AM, Ismail Donmez <ismail at i10z.com> wrote: > Hi, > > On Fri, Jan 15, 2016 at 12:59 AM, Chris Bieneman <beanz at apple.com> wrote: >> I’m kinda scared that you’re using it. What are you trying to accomplish >> that you are using it? Generally having LLVM split among that many >> dynamically loaded libraries results in

I decided to take a stab at 6601421 dladm set-linkprop should support multiple -p options along with some related linkprop fixes, but when I looked into dladm.c, was surprised to find that "dladm_parse_props()" is called from do_create_aggr and do_create_vlan in addition to the expected (by me, at least) do_create_vnic *linkprop functions. What happened here? Why do we pass in

Hi folks, I'm hitting the below assertion failure when compiling this small piece of C code (repro.c, attached). My command line is: bin/clang --target=aarch64-linux-gnu -c -O2 repro.c clang is built from top of trunk as of this morning. It only happens at -O2, and it doesn't happen with the default target (x86_64). I tried to reproduce using just 'llc -O2' but didn't