search for: btl

...otice how they are actually fundamentally different. Test-case: I'm coming at this from the compiler side, where the register form is unambiguous and not questioned. The discussion we're having involves only the immediate form of the instruction. GNU as interprets: bt $63, mem as btl $63, mem which may or may not be what the user intended, but is not the same as "btq $63, mem". I'm not an official LLVM spokesperson or anything, but our consensus seems to be that "bt $imm, whatever" is ambiguous (the %eax and %rax versions you quoted disambiguate the wi...

Greetings. I see a warning message while compiling OpenMPI and would appreciate it if you tell me what it means. This warning happens with any OpenMPI > 1.6.5. Even before starting a cluster, just "sessionInfo" triggers this warning. I'm pasting in the message from R-3.3.2 (this is MRO). Do the R parallel package cluster functions violate the warnings described here? >

...unk/test/CodeGen/X86/bt.ll (original) >> +++ llvm/trunk/test/CodeGen/X86/bt.ll Tue Oct 15 18:33:07 2013 >> @@ -38,7 +38,7 @@ UnifiedReturnBlock: ; preds = %entry >> define void @test2b(i32 %x, i32 %n) nounwind { >> entry: >> ; CHECK: test2b >> -; CHECK: btl %eax, %ecx >> +; CHECK: btl %e{{..}}, %e{{..}} >> ; CHECK: jb >> %tmp29 = lshr i32 %x, %n ; <i32> [#uses=1] >> %tmp3 = and i32 1, %tmp29 >> @@ -56,7 +56,7 @@ UnifiedReturnBlock: ; preds = %entry >> define void @atest2(...

...arser/X86AsmParser.cpp @@ -2124,6 +2124,36 @@ ParseInstruction(ParseInstructionInfo &Info, StringRef Name, SMLoc NameLoc, } } + // Infer the immediate form of bit-test instructions without length suffix + // correctly. The register form works fine. + // bt{,r,s,..} $n, mem becomes btl $(n % 32), (mem + 4 * (n / 32)) + if (Name.startswith("bt") + && !(Name.endswith("b") || Name.endswith("w") || Name.endswith("l") || Name.endswith("q")) + && Operands.size() == 3) { + X86Operand &Op1 = *(X86Operand*...

...gmail.com> wrote: > > I'm coming at this from the compiler side, where the register form is > unambiguous and not questioned. The discussion we're having involves > only the immediate form of the instruction. GNU as interprets: > > bt $63, mem > > as > btl $63, mem > > which may or may not be what the user intended, but is not the same as > "btq $63, mem". Umm. The user doesn't care. The user wants the best code without having to worry about it. Think of it this way: the whole and ONLY point of an assembler is to make machine...

> And that is why I think you should just consider "bt $x,y" to be > trivially the same thing and not at all ambiguous. Because there is > ABSOLUTELY ZERO ambiguity when people write > > bt $63, mem > > Zero. Nada. None. The semantics are *exactly* the same for btl and btq > in this case, so why would you want the user to specify one or the > other? I don't think you've actually tested that, have you? (x86-64) int main() { long val = 0xffffffff; char res; asm("btl $63, %1\n\tsetc %0" : "=r"(res) : "m"(val))...

...al, int index) { return (val & (1ULL<<index)) != 0ULL; } > unsigned int IsBitSetB_32(unsigned int val, int index) { return (val & (1U<<index)) != 0U; } > > $ icc -O3 -S bt.c -o - | grep bt > .file "bt.c" > btq %rsi, %rdi > btl %esi, %edi > > Does anyone at Intel have guidance for us? > > > On Thu, Jan 22, 2015 at 4:34 PM, Eric Christopher <echristo at gmail.com <mailto:echristo at gmail.com>> wrote: > > > On Thu Jan 22 2015 at 3:32:53 PM Chris Sears <chris.sears at gmail....

Off topic but an interesting article http://blogs.zdnet.com/BTL/index.php?p=1306 Cheers, Dean -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050603/6e1373e7/attachment.htm

...f the thread (it started out as 1). > > We use the gcc constraint "I" (0-31) in the kernel for this reason. > > Linus This is also why the Intel manuals point out that "some assemblers" can take things like: bt[l] $63,(%rsi) ... and turn it into: btl $31,4(%rsi) This is definitely the friendly thing to do toward the human programmer. Unfortunately gas doesn't, nor does e.g. NASM. -hpa

On Sun, Jul 14, 2013 at 12:30 PM, Tim Northover <t.p.northover at gmail.com> wrote: > > I don't think you've actually tested that, have you? (x86-64) Oh, you're right, for constants > 5 bits you have that other thing going on. I didn't think about the fact that the constant changed in the middle of the thread (it started out as 1). We use the gcc constraint

For several days, I try to run an Windows- Application on an Ubuntu 7.04 System through wine 0.9.58. In detail, it's a tool for supporting a change of food and sports behavior. The tool is freeware, named "Di?t- Tagebuch" (diet diary or diet day book) and downloadable at: http://www.diet-daybook.de/DTBInstall2.exe (unfortunately it's only in german) The DTBInstall2.exe is an

...es, circa 1980, S data directories were called swork and sdata not .Data, and "New-S" as described in the already medieval "Blue Book" discusses a function DBCONVERT that converted swork data into .Data data. It is embarrassing to admit it, but I still have data archives from a BTL machine called alice in the swork format and would like to convert a dataset to something modern. I had assumed that DBCONVERT or some equivalent would still be in my early modern Splus 3.3 version, but apparently not. Could anyone advise me on an alternative strategy? My apologies for such a...

On Thu Jan 22 2015 at 3:32:53 PM Chris Sears <chris.sears at gmail.com> wrote: > The status quo is: > > a) 40b REX+BT instruction for the 64b case > b) 48b TEST for the 32b case > c) unless it's small TEST > > > You are currently paying a 16b penalty for TEST vs BT in the 32b case. > That may be worth testing the -Os flag. > You'll want -Oz here, Os

...d b/lib/Target/X86/X86InstrInfo.td > index f33ae2a..4950674 100644 > --- a/lib/Target/X86/X86InstrInfo.td > +++ b/lib/Target/X86/X86InstrInfo.td > @@ -1971,6 +1971,10 @@ def : InstAlias<"aam", (AAM8i8 10)>; > // Disambiguate the mem/imm form of bt-without-a-suffix as btl. > def : InstAlias<"bt $imm, $mem", (BT32mi8 i32mem:$mem, i32i8imm:$imm)>; > > +// Disambiguate btr and bts, just like GNU as. > +def : InstAlias<"btr $imm, $mem", (BT16mi8 i16mem:$mem, i16i8imm:$imm)>; > +def : InstAlias<"bts $imm, $mem"...

...s and there can be nasty performance implications of doing a 32-bit write and then doing a 64-bit read of the result. I'm not actually aware of us having ever worried/cared about it, but it's a possible source of trouble: mixing bitop instructions with non-bitop instructions can have some subtle interactions, and you need to be careful, since the size of the operand affects both the offset *and* the memory access size. The access size generally is meaningless from a semantic standpoint (little-endian being the only sane model), but the access size *can* have performance implications for t...

...S "stosq" # define __FD_SET_BTS "btsq" # define __FD_CLR_BTR "btrq" # define __FD_ISSET_BT "btq" # else # define __FD_ZERO_STOS "stosl" # define __FD_SET_BTS "btsl" # define __FD_CLR_BTR "btrl" # define __FD_ISSET_BT "btl" # endif # define __FD_ZERO(fdsp) \ do { \ int __d0, __d1; \ __asm__ __volatile__ ("cld; rep; " __FD_ZERO_STOS \...

I have recently uploaded a new package to CRAN called eba, which stands for elimination-by-aspects models. It allows for fitting and testing probabilistic choice models, especially the BTL model (Bradley & Terry, 1952; Luce, 1959), elimination-by-aspects (EBA) models (Tversky, 1972), and preference tree (Pretree) models (Tversky & Sattath, 1979). I believe that the functions in this package can be useful in many fields, like marketing, consumer research, psychological scalin...

I have recently uploaded a new package to CRAN called eba, which stands for elimination-by-aspects models. It allows for fitting and testing probabilistic choice models, especially the BTL model (Bradley & Terry, 1952; Luce, 1959), elimination-by-aspects (EBA) models (Tversky, 1972), and preference tree (Pretree) models (Tversky & Sattath, 1979). I believe that the functions in this package can be useful in many fields, like marketing, consumer research, psychological scalin...

...----- 19035 ldbl acct nedelchev (192.168.0.100) Service pid machine Connected at ------------------------------------------------------- IPC$ 19035 nedelchev Thu Apr 5 14:07:17 2007 No locked files and here is mu smb.conf [global] workgroup = BTL show add printer wizard = No security = USER log level = 3 [files] comment = Work area files path = /home/samba/data/%U valid users = %S read only = No I have group acct and user ldbl password is set fo user ldbl with passwd and smbpasswd. I'm login to samba server without problem with user l...

...X86InstrInfo.td >> index f33ae2a..4950674 100644 >> --- a/lib/Target/X86/X86InstrInfo.td >> +++ b/lib/Target/X86/X86InstrInfo.td >> @@ -1971,6 +1971,10 @@ def : InstAlias<"aam", (AAM8i8 10)>; >> // Disambiguate the mem/imm form of bt-without-a-suffix as btl. >> def : InstAlias<"bt $imm, $mem", (BT32mi8 i32mem:$mem, i32i8imm:$imm)>; >> >> +// Disambiguate btr and bts, just like GNU as. >> +def : InstAlias<"btr $imm, $mem", (BT16mi8 i16mem:$mem, i16i8imm:$imm)>; >> +def : InstAlias<"...