search for: setc

...and started to create a new backend for a new RISC architecture. Now I need some help to get forward with my project. I'm quite new to compiling techniques so I'm sorry for the stupid questions. Question 1: My idea is to lower the select SDNode as follows: %res1 = %falseVal %res2 = setc %trueVal, %condition Where setc is conditional mov. The question is how can I make sure that %res1 and %res2 are assigned to the same phsyical register? (I'm assuming you can only define virtual register once, is this correct assumption?) Question 2: What kind of information if any the...

...s option > processing > > This is dumped by clang. I am not sure what I am supposed to put as value > in order to tune unrolling/inlining threshold. > As the help says, this is used to pass argument to LLVM itself. If you remember you earlier question about setA (clang options) and setC (opt options), this allows to reach setC from the clang command line. Any option that you see in the output of `opt --help` can be set from clang using `-mllvm`. Same caveat as I mentioned before: these aren't supposed to be end-user options. -- Mehdi > > On Mon, Jan 8, 2018 at 2:02...

...by clang. I am not sure what I am supposed to put as >>> value in order to tune unrolling/inlining threshold. >>> >> >> >> As the help says, this is used to pass argument to LLVM itself. If you >> remember you earlier question about setA (clang options) and setC (opt >> options), this allows to reach setC from the clang command line. >> Any option that you see in the output of `opt --help` can be set from >> clang using `-mllvm`. Same caveat as I mentioned before: these aren't >> supposed to be end-user options. >> >&g...

...>> This is dumped by clang. I am not sure what I am supposed to put as value >> in order to tune unrolling/inlining threshold. >> > > > As the help says, this is used to pass argument to LLVM itself. If you > remember you earlier question about setA (clang options) and setC (opt > options), this allows to reach setC from the clang command line. > Any option that you see in the output of `opt --help` can be set from > clang using `-mllvm`. Same caveat as I mentioned before: these aren't > supposed to be end-user options. > > -- > Mehdi > &g...

...t as >>>>> value in order to tune unrolling/inlining threshold. >>>>> >>>> >>>> >>>> As the help says, this is used to pass argument to LLVM itself. If you >>>> remember you earlier question about setA (clang options) and setC (opt >>>> options), this allows to reach setC from the clang command line. >>>> Any option that you see in the output of `opt --help` can be set from >>>> clang using `-mllvm`. Same caveat as I mentioned before: these aren't >>>> supposed to be e...

...what I am supposed to put as >>>> value in order to tune unrolling/inlining threshold. >>>> >>> >>> >>> As the help says, this is used to pass argument to LLVM itself. If you >>> remember you earlier question about setA (clang options) and setC (opt >>> options), this allows to reach setC from the clang command line. >>> Any option that you see in the output of `opt --help` can be set from >>> clang using `-mllvm`. Same caveat as I mentioned before: these aren't >>> supposed to be end-user options....

...;> value in order to tune unrolling/inlining threshold. >>>>>> >>>>> >>>>> >>>>> As the help says, this is used to pass argument to LLVM itself. If you >>>>> remember you earlier question about setA (clang options) and setC (opt >>>>> options), this allows to reach setC from the clang command line. >>>>> Any option that you see in the output of `opt --help` can be set from >>>>> clang using `-mllvm`. Same caveat as I mentioned before: these aren't >>>>>...

...to tune unrolling/inlining threshold. >>>>>>> >>>>>> >>>>>> >>>>>> As the help says, this is used to pass argument to LLVM itself. If >>>>>> you remember you earlier question about setA (clang options) and setC (opt >>>>>> options), this allows to reach setC from the clang command line. >>>>>> Any option that you see in the output of `opt --help` can be set from >>>>>> clang using `-mllvm`. Same caveat as I mentioned before: these aren't >>&...

...nlining threshold. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> As the help says, this is used to pass argument to LLVM itself. If >>>>>>> you remember you earlier question about setA (clang options) and setC (opt >>>>>>> options), this allows to reach setC from the clang command line. >>>>>>> Any option that you see in the output of `opt --help` can be set >>>>>>> from clang using `-mllvm`. Same caveat as I mentioned before: these aren'...

...gt;>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> As the help says, this is used to pass argument to LLVM itself. If >>>>>>>> you remember you earlier question about setA (clang options) and setC (opt >>>>>>>> options), this allows to reach setC from the clang command line. >>>>>>>> Any option that you see in the output of `opt --help` can be set >>>>>>>> from clang using `-mllvm`. Same caveat as I mentioned before: th...

...orward to more discussions. >>>> >>>> Thanks a lot! >>>> >>>> On Sun, Jan 7, 2018 at 10:11 AM, Mehdi AMINI <joker.eph at gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> "SetC" options are LLVM cl::opt options, they are intended for LLVM >>>>> developer and experimentations. If a settings is intended to be used as a >>>>> public API, there is usually a programmatic way of setting it in LLVM. >>>>> "SetA" is what...

...gt; pipeline. >>> Looking forward to more discussions. >>> >>> Thanks a lot! >>> >>> On Sun, Jan 7, 2018 at 10:11 AM, Mehdi AMINI <joker.eph at gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> "SetC" options are LLVM cl::opt options, they are intended for LLVM >>>> developer and experimentations. If a settings is intended to be used as a >>>> public API, there is usually a programmatic way of setting it in LLVM. >>>> "SetA" is what clang as a...

Hi, "SetC" options are LLVM cl::opt options, they are intended for LLVM developer and experimentations. If a settings is intended to be used as a public API, there is usually a programmatic way of setting it in LLVM. "SetA" is what clang as a C++ compiler exposes to the end-user. Internally cl...

.... I am curious about which way is the best for my purpose. Please see my latest reply for 3 possible fine-grained optimization pipeline. Looking forward to more discussions. Thanks a lot! On Sun, Jan 7, 2018 at 10:11 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: > Hi, > > "SetC" options are LLVM cl::opt options, they are intended for LLVM > developer and experimentations. If a settings is intended to be used as a > public API, there is usually a programmatic way of setting it in LLVM. > "SetA" is what clang as a C++ compiler exposes to the end-user...

...y purpose. > Please see my latest reply for 3 possible fine-grained optimization > pipeline. > Looking forward to more discussions. > > Thanks a lot! > > On Sun, Jan 7, 2018 at 10:11 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: > >> Hi, >> >> "SetC" options are LLVM cl::opt options, they are intended for LLVM >> developer and experimentations. If a settings is intended to be used as a >> public API, there is usually a programmatic way of setting it in LLVM. >> "SetA" is what clang as a C++ compiler exposes to...

...ly for 3 possible fine-grained optimization >> pipeline. >> Looking forward to more discussions. >> >> Thanks a lot! >> >> On Sun, Jan 7, 2018 at 10:11 AM, Mehdi AMINI <joker.eph at gmail.com> wrote: >> >>> Hi, >>> >>> "SetC" options are LLVM cl::opt options, they are intended for LLVM >>> developer and experimentations. If a settings is intended to be used as a >>> public API, there is usually a programmatic way of setting it in LLVM. >>> "SetA" is what clang as a C++ compiler...

...BOUNCE_eip(%rdx) - movb $0,TRAPBOUNCE_flags(%rdx) - bt $_VGCF_syscall_disables_events,VCPU_guest_context_flags(%rbx) - jnc 1f - movb $TBF_INTERRUPT,TRAPBOUNCE_flags(%rdx) -1: call create_bounce_frame - andl $~X86_EFLAGS_DF,UREGS_eflags(%rsp) + setc %cl + leal (,%rcx,TBF_INTERRUPT),%ecx + movb %cl,TRAPBOUNCE_flags(%rdx) + call create_bounce_frame + movl VCPU_syscall_eflags_mask(%rbx),%eax + notl %eax + andl %eax,UREGS_eflags(%rsp) jmp test_all_events /* %rbx: struct vcpu, interrupt...

Craig, thanks a lot! I'm actually confused by clang optimization flags. If I run clang -help, it will show many optimizations (denoted as set A) and non-optimization options (denoted as set B). If I run llvm-as < /dev/null | opt -O0/1/2/3 -disable-output -debug-pass=Arguments, it also shows many optimization flags (denote as set C). There are many options in set C while not in set A,

O0 didn't start applying optnone until r304127 in May 2017 which is after the 4.0 family was branched. So only 5.0, 6.0, and trunk have that behavior. Commit message copied below Author: Mehdi Amini <joker.eph at gmail.com> Date: Mon May 29 05:38:20 2017 +0000 IRGen: Add optnone attribute on function during O0 Amongst other, this will help LTO to correctly handle/honor

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability