search for: prefix

I'm looking at the instruction formats and I can't grok the comments. For example: // SSSE3 Instruction Templates: // // SS38I - SSSE3 instructions with T8 prefix. // SS3AI - SSSE3 instructions with TA prefix. // Where are these prefix names coming from? I can't find any mention of them in the Intel literature. Also, there's this curious table: // Prefix byte classes which are used to indicate to the ad-hoc machine code // emitter that various...

On Mar 23, 2009, at 12:57 PM, David A. Greene wrote: > I'm looking at the instruction formats and I can't grok the > comments. For > example: > > // SSSE3 Instruction Templates: > // > // SS38I - SSSE3 instructions with T8 prefix. > // SS3AI - SSSE3 instructions with TA prefix. > // > > Where are these prefix names coming from? I can't find any mention > of them in > the Intel literature. They come from the fact that the SSSE3 instructions begin with 0F 38 or 0F 3A. > > Also, there's...

On Thu, May 26, 2016 at 10:35 AM, Ehsan Amiri via llvm-dev < llvm-dev at lists.llvm.org> wrote: > 7. Wildcard for prefixes - If some statements should be checked > regardless prefix, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME > and etc. > >> 8. Prefix with regular expressions - If statement should be >> checked if prefix matches some regular expression, it should be used >>...

I wrote: > I think it's a bug. Or at least QueryParser uses a rather delicate rule > for when to add a ":" between the prefix and the term, which scriptindex > doesn't implement. The rule is undocumented (except in the code) so > it's arguable who is correct. I've been looking at this some more. We need some way to distinguish the term prefix from the term itself. The scheme Omega uses is that a sing...

https://bugzilla.netfilter.org/show_bug.cgi?id=1733 Bug ID: 1733 Summary: prefix len in a set of ips is wrong in a rule Product: nftables Version: 0.9.x Hardware: x86_64 OS: RedHat Linux Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org...

....0.0/0 0 0 eth2_in all -- eth2 * 0.0.0.0/0 0.0.0.0/0 0 0 Reject all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 6 prefix `Shorewall:INPUT:REJECT:'' 0 0 reject all -- * * 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy DROP 53 packets, 2772 bytes) pkts bytes target prot opt in out source destination 0 0 DROP !icmp -- *...

Hi, I would like to add a prefix to colnames in a matrix but I can't get the prefix option in colnames to work. What am I doing wrong? > X<-matrix(NA,3,4) > colnames(X)<-c("test","test","test","test") > colnames(X)<-colnames(X,prefix="PREFIX.") > X te...

...Elena.Lepilkina at synopsys.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] RFC: FileCheck Enhancements On Thu, May 26, 2016 at 10:35 AM, Ehsan Amiri via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: 7. Wildcard for prefixes - If some statements should be checked regardless prefix, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. 8. Prefix with regular expressions - If statement should be checked if prefix matches some regular expression, it should be used {{regex}}:, {{regex}}-NEXT and etc....

Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix t...

I run R 2.1.1 in a Linux environment (RedHat 9) although my question is not platform-specific. Consider the following: > A <- c("Prefix-aaa", "Prefix-bbb", "Prefix-ccc") > B <- strsplit(A, "-") > B [[1]] [1] "Prefix" "aaa" [[2]] [1] "Prefix" "bbb" [[3]] [1] "Prefix" "ccc" How do I extract the elements "aaa", "...

...n | 3 ++- 5 files changed, 16 insertions(+), 4 deletions(-) diff --git a/autoconf/configure.ac b/autoconf/configure.ac index f3e94e8..cd943cc 100644 --- a/autoconf/configure.ac +++ b/autoconf/configure.ac @@ -1606,9 +1606,11 @@ AC_SUBST(SHLIBPATH_VAR,$libltdl_cv_shlibpath_var) if test "${prefix}" = "NONE" ; then prefix="/usr/local" fi +libdir_suffix=$(echo ${libdir} | sed -r "s:.*[^0-9]([0-9]*):\1:g") eval LLVM_PREFIX="${prefix}"; eval LLVM_BINDIR="${prefix}/bin"; -eval LLVM_LIBDIR="${prefix}/lib"; +eval LLVM_LIBDIR_SU...

Hi, I am planning to add support to CMake so that the binaries of llvm will have a prefix appended to it. At this point, I am stuck on which approach to follow 1. Append the prefix during build and install time. If so, this might involve tweaking lit infrastructure to make sure lit picks the prefixed binaries. 2. Append the prefix only during install time. a. Ei...

Hi List, I am working on least cost routing code on the moment, and I am stumbling on a problem. Say you have provider A having: Prefix XXX 0.10 Prefix XXXYYY 0.20 And provider B having Prefix XXX 0.15 You're stuck, because you cannot decide if provider B's "XXX" prefix also covers XXXYYY numbers or not. If it doesn't, it would be a waste to try and contact it. Or maybe worse,...

hi, get.vars.name.prefix<-function(prefix){ result<-list() len<-nchar(prefix) var.names<-ls(name=1,pattern=prefix) #name=1 probably wrong option print(var.names) for(i in 1:length(var.names)){ name<-var.names[i] field<-substr(name,len+1,nchar(name)) result[[field]]<-get(name) } result } f...

With print(list(A="a",B="b")) it displays $A [1] "a" $B [1] "b" I would like to add a common prefix to all the list tags after the $. Pasting the prefix to the "names" does not work (appear after the $). For example if the prefix would be "P", it should display: P$A [1] "a" P$B [1] "b" I tried to add a "name" attribute to the list or to add a...

...r syslinux.efi and are having trouble with HTTP, see below... Regarding the "-a" and "-b" options, with (l)pxelinux.0 I discovered at some point in the past, after some trials, that the following combination worked great for me: -b next-server my.ip.address -a path-prefix http://my.ip.address/ -a config-file pxe.bios.cfg Thus, with syslinux.efi I similarly tried: -b next-server my.ip.address -a path-prefix http://my.ip.address/ -a config-file pxe.efi64.cfg But now, after the initial TFTP transfer of syslinux.efi, the client would hang (with no attem...

...a better way to do this? If this will help, these are the options I'm using to build llvm-gcc4. It's in tcl, but it hopefully is straight forward enough: # create a build directory and run out of there worksrcdir build pre-configure { file mkdir ${workpath}/build } # ${prefix} is where we install llvm, normally /opt/local configure.cmd ../llvm-gcc4-${version}.source/configure configure.args-append --enable-llvm=${prefix}/lib/llvm/obj \ --enable-languages=c,c++,objc,obj-c++ \ --libdir=${prefix}/lib/${name} \...

...al, I imagine this feature could be useful for the implementation of languages which require runtime metadata for each function. The proposal is that an IR function definition acquires a constant operand which contains the data to be emitted immediately before the function body (known as the prefix data). To access the data for a given function, a program may bitcast the function pointer to a pointer to the constant's type. This implies that the IR symbol points to the start of the prefix data. To maintain the semantics of ordinary function calls, the prefix data must have a particular...

7. Wildcard for prefixes - If some statements should be checked regardless prefix, it should be used //{{*}}, //{{*}}-NEXT, //{{*}}-SAME and etc. > 8. Prefix with regular expressions - If statement should be checked > if prefix matches some regular expression, it should be used {{regex}}:, > {{regex}}-NEX...

On Wed, Jul 17, 2013 at 9:06 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > To maintain the semantics of ordinary function calls, the prefix data > must have a particular format. Specifically, it must begin with a > sequence of bytes which decode to a sequence of machine instructions, > valid for the module's target, which transfer control to the point > immediately succeeding the prefix data, without performing any oth...