search for: junkoi2004

...> .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,0xabcdef1234567890 Cool,...

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: >> >> ..... >> } else if...

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 AssemblerDialect...

...mbly 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. >> >...

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: >>> >>>&g...

...;t have an LLVM back end. > > > > > > > > The source program could be in modern C, C++, or any other high > > level language or assembly language with a translator to LLVM. > > > > > > > > On Tue, Aug 19, 2014 at 1:40 PM, Jun Koi <junkoi2004 at gmail.com > > <mailto:junkoi2004 at gmail.com>> wrote: > > > > > > > > > > > > On Mon, Aug 18, 2014 at 9:18 PM, Carback, Richard T., III > > <rcarback at draper.com <mailto:rcarback at draper.com>> wrote: > >...

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-by: Jun Koi &l...

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: >>>> On 5 Oct 2012, at 08:34, Jun Koi wrote: >>&gt...

...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" > > > > Be...

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}"|./Release+Asserts...

...M) is never used, and the disassembler always reads the opcode as a 4-byte value. Vladimir/Sasa/Jozef/Zoran: I don't know much about the microMIPS encodings at the moment. Do you have the details on distinguishing 16-bit from 32-bit instructions? ________________________________ From: Jun Koi [junkoi2004 at gmail.com] Sent: 29 October 2014 14:46 To: Daniel Sanders Cc: llvmdev at cs.uiuc.edu Subject: Mips's MicroMips ?? Hi, We have this line in micromips-16-bit-instructions.s # CHECK-EB: addu16 $6, $17, $4 # encoding: [0x07,0x42] However, when I check this with llvm-mc, like below,...

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 related instruction...

...\ > 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+Asserts/bin/llvm-mc...

I'll look into it, thanks for the report. On Thu, Jul 30, 2015 at 11:01 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > Any ideas on this bug? > > Thanks. > > > On Wed, Jul 29, 2015 at 12:17 AM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> Hello, >> >> There is an issue in the latest Sparc code: while we can encode POPC, >> decode results...

...ve no commit access, if you think the patch is correct I would appreciate your help in committing it. Regards David 2015-07-31 16:56 GMT+02:00 James Y Knight <jyknight at google.com>: > I'll look into it, thanks for the report. > > On Thu, Jul 30, 2015 at 11:01 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > >> Any ideas on this bug? >> >> Thanks. >> >> >> On Wed, Jul 29, 2015 at 12:17 AM, Jun Koi <junkoi2004 at gmail.com> wrote: >> >>> Hello, >>> >>> There is an issue in the latest Sparc code: while...

...liased to @XXX. I guess "opt -basicaa -{any-transform-passes}" would help you. You may also try "opt -{any-analysis-passes} -aa-eval}" Note, opt is the tool not for users but for developers. He does not invoke unspecified passes automatically. ...Takumi 2012/8/11 Jun Koi <junkoi2004 at gmail.com>: > On Sat, Aug 11, 2012 at 7:42 PM, Jun Koi <junkoi2004 at gmail.com> wrote: >> hi, >> >> i am trying to optimize the below code, in one of my LLVM functions: >> >> .... >> store i32 96, i32* @XXX, align 4 ; (1) >> store i3...

forgot to mention: this is from file MipsGenDisassemblerTables.inc thanks. On Fri, Aug 23, 2013 at 2:12 PM, Jun Koi <junkoi2004 at gmail.com> wrote: > 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 > > > > --------------...

Hi, In file X86DisassemblerDecoder.c, we have function readPrefixes() with below code: ..... } else if (insn->mode == MODE_32BIT) { insn->registerSize = (hasOpSize ? 2 : 4); insn->addressSize = (hasAdSize ? 2 : 4); insn->displacementSize = (hasAdSize ? 2 : 4); insn->immediateSize = (hasOpSize ? 2 : 4); } .... This is confused to me: so we

...o run natively on CPUs that have a working simple C compiler (maybe only K&R or C89) but don't have an LLVM back end. The source program could be in modern C, C++, or any other high level language or assembly language with a translator to LLVM. On Tue, Aug 19, 2014 at 1:40 PM, Jun Koi <junkoi2004 at gmail.com<mailto:junkoi2004 at gmail.com>> wrote: On Mon, Aug 18, 2014 at 9:18 PM, Carback, Richard T., III <rcarback at draper.com<mailto:rcarback at draper.com>> wrote: Hi All, 2 of my summer interns (Aimee Dipietro and Greg Simpson) used their time over the summer to r...