search for: trunking

Hello, Is there a script to update those test cases? I see mention of a sed script in the commit message but when I try it (see attached) on sed I get the following error: sed: file script line 2: invalid reference \3 on `s' command's RHS Did I lose something in a copy-paste? Is it not really a sed script? How do I run it? On Fri, Jan 19, 2018 at 9:15 AM, Daniel Neilson via

Hi Alexandre, The script uses extended-sed syntax, so you need to run sed with the -E option. For example, when preparing the patch I created a file ( script.sed ) containing all of the lines that I copied into the commit message. Then, I ran this bash one-liner from the test directory: for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; done When I was happy

Thanks, that worked like a charm except for the following: llvm generate: call void @llvm.memcpy.p3i8.p1i8.i64(i8 addrspace(3)* align 1 bitcast ([512 x float] addrspace(3)* @a_scratchpad to i8 addrspace(3)*), i8 addrspace(1)* align 1 %0, i64 2048, i1 false) And we expected: call void @llvm.memcpy.p3i8.p1i8.i64(i8 addrspace(3)* bitcast ([512 x float] addrspace(3)* [[SPM0]] to i8

Yes, all that is correct. My question is more a long term question: why do the .ll printer specify the alignment if it is equivalent to the default one? That is, it seems the sed script expect the printer to not specify it (this would match the load/store behavior), but the ll-printer does specify it, which either means the printer is not ideal on this case and I should fix it, or in this case

Hi Alexandre, Before the change you would have been expecting one of the following, correct? a) call void @llvm.memcpy.p3i8.p1i8.i64(i8 addrspace(3)* bitcast ([512 x float] addrspace(3)* [[SPM0]] to i8 addrspace(3)*), i8 addrspace(1)* [[APTR]], i64 2048, i32 0, i1 false) b) call void @llvm.memcpy.p3i8.p1i8.i64(i8 addrspace(3)* bitcast ([512 x float] addrspace(3)* [[SPM0]] to i8 addrspace(3)*), i8

Good question. AFAIK, the IR-printer doesn’t understand the semantics of parameter attributes. In this case, it only knows that there is an attribute on the parameter that is integer valued (with value 1) and that has the name “align”, so it prints it out. If we don’t want it printing out ‘align 1’ then it’s up to us to not set the alignment parameter attribute to a value if that value would be 1.

Anyone able to post a copy of the svn trunk of file_column? The website''s been down for the past few days, and I''ve only got the last release (0.31, I think), which is missing a whole load of goodies. Tx

Le 21/08/2013 12:20, maximilian attems a ?crit : > On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: >> Find attached two patches I have in order to build klibc 2.0.2 >> against kernel 3.8.13 >> We had to introduce those patches when going from kernel 3.6 to kernel 3.7 >> Hope it helps. >> > those patches are wrong and again very brittle. >

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux

I've been attempting to calculate the predictions from a poisson glm object, along these lines: predict(foo.glm, type = "response") and predict(foo.glm, type = "response", se.fit = TRUE) foo.glm is arrived at this way: foo.glm <- glm(Insects ~ Dad * Mum + Location, offset = log(MM), family = "poisson", data = model.df) There are two

Hi everybody, got it from svn: dtmf_2833_1.pcap */asterisk/trunk/tests/rfc2833_dtmf_detect/configs/extensions.conf PRE-CREATION *>* /asterisk/trunk/tests/rfc2833_dtmf_detect/configs/sip.conf PRE-CREATION *>* /asterisk/trunk/tests/rfc2833_dtmf_detect/run-test PRE-CREATION *>* /asterisk/trunk/tests/rfc2833_dtmf_detect/sipp/broken_dtmf.pcap UNKNOWN *>*

Dear list, This is my first time trying to set up the development version of R (R-devel ) in my local machine to test some packages before submitting them to CRAN. I'm using Linux Mint 17.1 64-bit, which is an Ubuntu-based distro. However, I'm not able to correctly set up r-devel, apparently due to a problem with enabling the shared library support. I run the first script given by Dirk

Cool, i'll help out a bit with the windows port, i will start right away with a new project on asteriskguru making nightly executable builds and installers - will post the links in -users when i'm done. Well done luigi, this will make it a lot easier for a lot of non linux guys to make their first steps in the asterisk world Crossposted to -users. Zoa Luigi Rizzo wrote: > As a

Hi, I try to build llvm-trunk with Cmake (gcc-5.3.0 is necessary for CUDA) on my "SUSE Linux Enterprise Server 12.2 (x86_64)". svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm cd llvm/tools svn co http://llvm.org/svn/llvm-project/cfe/trunk clang svn co http://llvm.org/svn/llvm-project/polly/trunk polly cd clang/tools svn co

Hi, I've taken a small bit of time to initiate this work. There is now: - an m4 macro to detect the system (linux only ATM, but simple to complete) - a set of "make package" targets throughout the tree (limited to debian ATM) The remaining tasks on this specific point are: - m4 macro completion to handle all the supported platforms (at least the ones that have files in the

Pending positive confirmation in http://llvm.org/PR2886, I'd recommend that r57974 and r57976 be pulled into the 2.4 release branch and configure regenerated there. Begin forwarded message: > From: Gordon Henriksen <gordonhenriksen at mac.com> > Date: October 22, 2008 08:40:40 EDT > To: llvm-commits at cs.uiuc.edu > Subject: [llvm-commits] [llvm] r57974 -

Hello, GCC 9.0 introduces a new warning checkers and some of them found possible issues in LLVM. In file included from /home/davidbolvansky/trunk/llvm/include/llvm/Analysis/LazyCallGraph.h:38, from /home/davidbolvansky/trunk/llvm/unittests/Analysis/LazyCallGraphTest.cpp:10: /home/davidbolvansky/trunk/llvm/include/llvm/ADT/ArrayRef.h: In instantiation of

We are starting a local LLVM backend project (using svn) and are looking for a mechanism to periodically update to later LLVM releases. Certainly, this seems like it would be a relatively common use case and I expected a google search would reveal several options. However, I didn’t really find anything. Perhaps I’m not looking for the right keywords, if so please help me out and point me to any

Anyone got a script to share that: 1. Creates a trunk directory 2. Creates a trunk/vendor directory 3. Adds the above to svn 4. Modifies trunk/vendor to use a certain rails revision (i.e. trunk or 1.1) 5. Runs trunk/vendor/rails/.../bin/rails to generate a rails directory skeleton 6. Modifies the svn:ignore for the logs and config/database.yml 7. Moves config/database.yml to

I'm getting the following when building llvm-gcc with an optimized set of LLVM libraries: /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/