search for: koi

...rom the Windows DC. Note that I did not have to specify which name server to use to dig, so the entry in resolv.conf is working. When I try to join the domain as a DC, I get the error: NO DNS zone information found in source domain, not replicating DNS The Windows DC does now list the Linux box (Koi) as a DC, but the adi.com zone on the Windows box does not list Koi in any of the records. I manually added an address record for Koi to the Windows DC and redid the join, but the result is the same. Given some of the other messages, I am not sure if anything is working correctly. Following is the...

On Tue, Oct 9, 2012 at 9:25 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >> On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall >> <David.Chisnall at cl.cam.ac.uk> wrote: >>> On 5 Oct 2012, at 08:34, Jun Koi wrote: >>>...

Hi Jun, On 18/10/12 11:19, Jun Koi wrote: > On Tue, Oct 9, 2012 at 9:25 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >> On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >>> On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall >>> <David.Chisnall at cl.cam.ac.uk> wrote: &...

...ains multiple errors about updating the DNS. I ran samba_dnsupdate --verbose to see what it would say and it listed many missing resords and then output errors about trying to add them. Here are three sample errors: Calling nsupdate for CNAME ef382a43-092e-4cda-acb1-e7ba70e9253e._msdcs.adi.com koi.adi.com Outgoing update query: ;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0 ;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0 ;; UPDATE SECTION: ef382a43-092e-4cda-acb1-e7ba70e9253e._msdcs.adi.com. 900 IN CNAME koi.adi.com. dns_request_getresponse: FORMERR Failed n...

I looked at this briefly, I think it causes some mistakes that get reversed later in fixupReg. The disassembler design is a bit of a mess with regards to prefixes and operand size. On Tue, Apr 1, 2014 at 4:43 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > > > > On Mon, Mar 31, 2014 at 11:48 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> Hi, >> >> In file X86DisassemblerDecoder.c, we have function readPrefixes() with >> below code: >> >> ..... >&g...

On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 Oct 2012, at 08:34, Jun Koi wrote: > >> any idea on how to fix the problem? > > The correct solution is to fix the LLVM build to install the .cmake files in a location that CMake knows about. could you please elaborate? > The hacky solution that I've used is just to copy them into the correct place ma...

On Thu, Jun 26, 2014 at 10:23 AM, Adam Nemet <anemet at apple.com> wrote: > > > On Jun 25, 2014, at 7:05 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > > > > > On Thu, Jun 26, 2014 at 5:47 AM, Adam Nemet <anemet at apple.com> wrote: > >> Hi Jun, >> >> On Jun 25, 2014, at 8:14 AM, Jun Koi <junkoi2004 at gmail.com> wrote: >> >> > Hi, >> >...

currently, there is no (easy) way to set the AssemblerDialect. the only method i am aware of is to set that via cl:opt. this patch fixes that by adding a public function setAssemblerDialect() to class MCAsmInfo. Signed-off-by: Jun Koi <junkoi2004 at gmail.com> diff --git a/include/llvm/MC/MCAsmInfo.h b/include/llvm/MC/MCAsmInfo.h index 97aad71..cd08a7e 100644 --- a/include/llvm/MC/MCAsmInfo.h +++ b/include/llvm/MC/MCAsmInfo.h @@ -453,6 +453,9 @@ namespace llvm { unsigned getAssemblerDialect() const { return A...

...irst two bytes are read and decodeInstruction is called with DecoderTableMicroMips16 and only if it fails we read 4 bytes and call decodeInstruction with DecoderTableMicroMips32. Regards, Zoran ________________________________ From: Daniel Sanders Sent: Sunday, November 02, 2014 5:49 PM To: Jun Koi; Vladimir Medic; Sasa Stankovic; Jozef Kolek; Zoran Jovanovic Cc: llvmdev at cs.uiuc.edu Subject: RE: Mips's MicroMips ?? Hi, I've had a quick look through MipsDisassembler.cpp and it seems that the disassembler doesn't know anything about 16-bit instructions at the moment. The two ma...

...the assembly using alternative dialect. currently, on Intel machine, the default dialect is AT&T, and we cannot change that to Intel syntax without using cl:opt. the new public method lets us change the dialect without having cl:opt involved. thanks, Jun > On Oct 1, 2012, at 8:33 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> currently, there is no (easy) way to set the AssemblerDialect. the >> only method i am aware of is to set that via cl:opt. >> >> this patch fixes that by adding a public function >> setAssemblerDialect() to class MCAsmInfo...

hi, there are two arrays named DecoderTable32[] and DecoderTable16[] that has no reference to. any idea why they are there? does it make sense to remove them? (this is llvm 3.3) thanks, Jun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130823/a95811fb/attachment.html>

On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall > <David.Chisnall at cl.cam.ac.uk> wrote: >> On 5 Oct 2012, at 08:34, Jun Koi wrote: >> >>> any idea on how to fix the problem? >> >> The correct solution is to fix t...

...>>>> .text >>>>> movq $0x12345678, %r8 # encoding: [0x49,0xc7,0xc0,0x78,0x56,0x34,0x12] I would recommend you some studying of x86 instruction set. Another recommendation is to look at existing tests when you suspect a bug. Regards, --artem. From: Jun Koi [mailto:junkoi2004 at gmail.com] Sent: 18 February, 2016 15:09 To: Tamazov, Artem Subject: RE: [llvm-dev] Bug in X86 assembler? On Feb 18, 2016 7:27 PM, "Tamazov, Artem" <Artem.Tamazov at amd.com<mailto:Artem.Tamazov at amd.com>> wrote: > > movabsq %rax,0xabcde...

What's the use case? On Oct 1, 2012, at 8:33 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > currently, there is no (easy) way to set the AssemblerDialect. the > only method i am aware of is to set that via cl:opt. > > this patch fixes that by adding a public function > setAssemblerDialect() to class MCAsmInfo. > > Signed-off...

I am fairly new to dovecot... I had a user who in outlook tried to move one of the folders into another folder but it crapped out. User tried to move "Djans*" folders into Koi folder. The subscription seems to show the folder move but the actual data is still under ".ClickEats.Clients.Djans" instead of ".ClickEats.Clients.Koi.Djans*. How do I fix this? Thanks. root at the:/apps/mail/clickeats.com/juliam/Maildir# grep -i djan subscriptions ClickEats.Rest...

...problem, as nothing is wrong with compiling in the source directory. actually i did this many times before, but now i moved to a new OSX machine, and have this problem. (and i already tried your solution, and confirm it doesnt help). thanks. > > On Wed, Sep 17, 2014 at 10:40 AM, Jun Koi <junkoi2004 at gmail.com> wrote: > > I got the latest LLVM code from git repo, and tried to compile > > that on my OSX 10.9.4 machine. But I got the error at "make" step: > > > > "Makefile:151: /Makefile.rules: No such file or directory" > &g...

On Thu, Jun 26, 2014 at 5:47 AM, Adam Nemet <anemet at apple.com> wrote: > Hi Jun, > > On Jun 25, 2014, at 8:14 AM, Jun Koi <junkoi2004 at gmail.com> wrote: > > > Hi, > > > > I am trying to assemble below instruction with latest LLVM code, but > fail. Am I doing something wrong, or is this a bug? > > > > > > $ echo "vaddps zmm7 {k6}, zmm2, zmm4, > {rd-sae}"|./...

On Thu, Oct 18, 2012 at 5:33 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Jun, > > > On 18/10/12 11:19, Jun Koi wrote: >> >> On Tue, Oct 9, 2012 at 9:25 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >>> >>> On Fri, Oct 5, 2012 at 3:45 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >>>> >>>> On Fri, Oct 5, 2012 at 3:39 PM, David Chisnall >>&...

The IMM3/IMM5 come from here X86RecognizableInstr.cpp 943 TYPE("SSECC", TYPE_IMM3) 944: TYPE("AVXCC", TYPE_IMM5) On Thu, Dec 25, 2014 at 8:22 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > > > On Fri, Dec 26, 2014 at 11:54 AM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> hi, >> >> some instructions mismatch between assembler & disassembler, like below. >> it seems this happens with all SSECC rela...

...\ > return prefix##_MM0 + index; > yes, exactly this place. but the question is: how do we know when to drop the REX.B? i dont know any non-MMX examples. it seems only MMX related instructions have this issue. thanks, Jun > > On Tue, Dec 23, 2014 at 10:17 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >> >> hi, >> >> i think the current X86 disassembler is quite broken and fails badly on >> handling REX for x86_64 code. >> >> below are some examples: >> >> $ echo "0x0f,0xeb,0xc3"|./Release+Asse...