search for: dxxxx

...rest of LLVM there might > be ways to make it less painful. FWIW, here is what I do, and I know not > everyone wants to use `arc`. Ina script this could potentially reduce > the pain. Again, this is not meant to tell you it is simple or your > problems are not real. > > arc patch DXXXX > git pull --rebase origin master > arc amend > arcfilter // see below > git llvm push master > > > arcfilter () { git log -1 --pretty=%B | awk '/Reviewers:|Subscribers:/{p=1} /Reviewed By:|Differential Revision:/{p=0} !p && !/^Summary:/' | git commit -...

...>> be ways to make it less painful. FWIW, here is what I do, and I know not >> everyone wants to use `arc`. Ina script this could potentially reduce >> the pain. Again, this is not meant to tell you it is simple or your >> problems are not real. >> >> arc patch DXXXX >> git pull --rebase origin master >> arc amend >> arcfilter // see below >> git llvm push master >> >> >> arcfilter () { git log -1 --pretty=%B | awk '/Reviewers:|Subscribers:/{p=1} /Reviewed By:|Differential Revision:/{p=0} !p && !/^S...

I want to share a little LLVM experiment. I tried LLVM on one of my bigger Qt 3.x based projects. I used llvm from SVN trunk (r39999) and SVN llvm-gcc-4.01 (r370) and did compile every file with /usr/src/llvm/dist/bin/g++ -c -pipe -g \ -Wall -Wextra -Wno-sign-compare \ ... lots of -Dxxxx ... \ --emit-llvm -I/usr/share/qt3/mkspecs/default \ -I. -I.. -I../../../include/qt3 -I.obj/ \ -o .obj/FILENAME.o FILENAME.cpp so that I later had 211 .o files, all in the binary bytecode format. I tried it that way because I thought that then the possibilities for inter-process and inter-...

...it less painful. FWIW, here is what I do, and I know not > >> everyone wants to use `arc`. Ina script this could potentially reduce > >> the pain. Again, this is not meant to tell you it is simple or your > >> problems are not real. > >> > >> arc patch DXXXX > >> git pull --rebase origin master > >> arc amend > >> arcfilter // see below > >> git llvm push master > >> > >> > >> arcfilter () { git log -1 --pretty=%B | awk '/Reviewers:|Subscribers:/{p=1} /Reviewed By:|Differential...

Hello I'm trying to build hpa-tftp on an OpenBSD so I'll have support for "tsize". configure run successfully, then I run gmake, then the following errors. thanks gmake[1]: Entering directory `/usr/local/src/tftp-hpa-0.28/tftp' gcc -g -O2 -D_XPG4_2 -D_XOPEN_SOURCE -D__EXTENSIONS__ -D_BSD_SOURCE -D_ISO9X_SOURCE -D_OSF_SOURCE -D_XOPEN_SOURCE_EXTENDED -W -Wall

...ike the memory-hog status is related to debug info, e.g. to -g. Because I later compiled the same program with RELEASE settings, e.g. $ /usr/src/llvm/dist/bin/g++ -c -pipe --emit-llvm \ -fvisibility=hidden -fvisibility-inlines-hidden \ -Wall -Wextra -Wno-sign-compare -Os \ ... lots of -Dxxxx ... \ -I/usr/share/qt3/mkspecs/default -I. -I.. \ -I../../../include/qt3 -I.obj/ \ -o .obj/FILENAME.o .obj/FILENAME.cpp and linked the result like this: $ /usr/src/llvm/dist/bin/llvm-ld \ -v -stats -native -verify-each -strip-all \ -o main \ ... lots of *.o files ... \...

...e novel/worth having, so if you want to write more, perhaps do so I & if it seems like too many, we can cut back/retune. Looking at https://releases.llvm.org/10.0.0/docs/ReleaseNotes.html https://releases.llvm.org/10.0.0/tools/clang/docs/ReleaseNotes.html most items don't include a link to Dxxxxx. A user needs some log grepping to find the particular differential revisions. Where possible, I hope we include a link. I added Dxxxx links for lld 10.0.0 ELF items https://releases.llvm.org/10.0.0/tools/lld/docs/ReleaseNotes.html#elf-improvements (In my opinion Dxxxxx is better than rGxxxxxx b...

...c/samba/smbpasswd wins support = yes [test] comment = for testing only path = /usr/local/test read only = no [homes] browseable = yes writable = yes valid users = dxxxx I can connect to the Windows XP machine from the Linux machine quite easily, and I'm sharing a printer with it. However, the problem comes when I try to go the opposite direction, and attempt to connect to my Linux machine from the Windows XP machine. Going to My Network Places >> View...

Hi, I know there has been significant discussion about "moving" from Phabricator to GitHub reviews and pull requests, etc. I'm not suggesting that we do anything in terms of global LLVM policy. However, as a maintainer of libc++, I commit __a lot__ of other people's code for them. It would be a huge time saver for me if I could nicely suggest to contributors (not force them) to

...specify the call blocking numbers. (since v3.0) # o Fxxxx: specify the call forwarding blocking numbers. (since # v3.0) # o Xxxxx: specify the call blocking/call forwarding blocking # numbers. (since v3.0) # o Dxxxx: displaying Caller ID. (since v3.0) # # More details are available in the eng114487.doc. # # Examples 1: The set of dial plan rules: # # ".t7>#......t4-|911|1t7>#..........t1-|0t4>#.t7-" # # or equivalently # # &...

Hi all, I have a Cisco ATA186 connected to an Asterisk Server (SIP) The dialplan uses 1XX for local extensions and XXXXXXX for external numbers, where the first digit is always different than 1. In this moment, when I dial 123 for example, ATA waits till timeout before dialing that number. The same for the longer one. How can I do to make it dial imediately when 3 digits starting with 1 are

...be finished: - Logical View in JSON format. Currently it uses free form text style. - COFF/CodeView disassembly text sections. - COFF/CodeView ranges and locations. ========== Conclusion ========== The source code has been uploaded for review on phabricator at this link: https://reviews.llvm.org/Dxxxx. The review covers two patches: A first patch with a IntervalTree data structure implementation which is required by llvm-diva. A second patch with the actual tool (in llvm/tools/llvm-diva). Once these first two patches are committed, the plan is to keep working on llvm-diva with the help of th...

I'm not sure if this is well known, but it helped me so I thought I'd share it with you. When committing to gitmonorepo, (with git llvm push) you need to have committed to your local repo first and so you need to have crafted your commit message from your the Phabricator revision. (e.g. D12345) Phabricator has the ability to give you this commit message it would have used, even if you do

Hi Vishal, Ruijie, Thanks for your interest in the project. To get started, the first task would be to merge the 5 patches on top of trunk llvm. The list of patches are listed in the project description: http://llvm.org/OpenProjects.html#llvm_mergesim Please create an account in llvm phabricator (reviews.llvm.org) if you haven't already, and put your patches there. Let me know if you have

Eh - I'd say "Big" new features (hey, LLVM supports DWARFv5, or Split DWARF, or DWARF type units, or DWARF compression (though I don't think I wrote any release notes for several of those features that I implemented)). I wouldn't bother release noting changes in output format for tools we don't consider to have stable output, or changes in robustness/better error