search for: minilanguage

...would require custom C++ code in the ARM target to handle properly. It might make sense to introduce something like CCIfType<[f64], CCCustom> where CCCustom is a new entity that tells the calling convention code to to let the target do something not easily representable in the tablegen minilanguage. Dan

...r written in LLVM IR which consist of 3 modules: filter, decoder and filter_rule. The last one is generated using my own-written compiler. I`d like to ask if there is a possibility to generate filter_rule, then link it with other two modules and run on the fly. Now I compile my own BPF-like minilanguage to IR, then translate it to bitcode using llvm-as, then link it with other two modules with llvm-link and finally run with lli. I don`t want to use makefile I want to do everything on the fly in my compiler. Thanks. Radovan Baranec

...ARM target to > handle properly. It might make sense to introduce something > like > > CCIfType<[f64], CCCustom> > > where CCCustom is a new entity that tells the calling convention > code to to let the target do something not easily representable > in the tablegen minilanguage. I am thinking that this requires two changes: add a flag to CCValAssign (take a bit from HTP) to indicate isCustom and a way to author an arbitrary CCAction by including the source directly in the TableGen mini-language. This latter change might want a generic change to the TableGen language. For...

Attached is a prototype patch that uses CCState to lower RET nodes in the ARM target. Lowering CALL nodes will come later. This patch does not handle f64 and i64 types. For these types, it would be ideal to request the conversions below: def RetCC_ARM_APCS : CallingConv<[ CCIfType<[f32], CCBitConvertToType<i32>>, CCIfType<[f64], CCBitConvertToType<i64>>,

...roperly. It might make sense to introduce something >> like >> >> CCIfType<[f64], CCCustom> >> >> where CCCustom is a new entity that tells the calling convention >> code to to let the target do something not easily representable >> in the tablegen minilanguage. > > I am thinking that this requires two changes: add a flag to > CCValAssign (take a bit from HTP) to indicate isCustom and a way to > author an arbitrary CCAction by including the source directly in the > TableGen mini-language. This latter change might want a generic change >...

...LLVM IR which consist of 3 modules: > filter, decoder and filter_rule. The last one is generated using my > own-written compiler. I`d like to ask if there is a possibility to > generate filter_rule, then link it with other two modules and run on the > fly. Now I compile my own BPF-like minilanguage to IR, then translate it > to bitcode using llvm-as, then link it with other two modules with > llvm-link and finally run with lli. I don`t want to use makefile I want to > do everything on the fly in my compiler. Thanks. > > Radovan Baranec > _____________________________________...

...e to introduce something >>> like >>> >>> CCIfType<[f64], CCCustom> >>> >>> where CCCustom is a new entity that tells the calling convention >>> code to to let the target do something not easily representable >>> in the tablegen minilanguage. >> >> I am thinking that this requires two changes: add a flag to >> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >> author an arbitrary CCAction by including the source directly in the >> TableGen mini-language. This latter change might want a...

...t;>>> like >>>> >>>> CCIfType<[f64], CCCustom> >>>> >>>> where CCCustom is a new entity that tells the calling convention >>>> code to to let the target do something not easily representable >>>> in the tablegen minilanguage. >>> >>> I am thinking that this requires two changes: add a flag to >>> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >>> author an arbitrary CCAction by including the source directly in the >>> TableGen mini-language. This latter...

...onsist of 3 modules: >> filter, decoder and filter_rule. The last one is generated using my >> own-written compiler. I`d like to ask if there is a possibility to >> generate filter_rule, then link it with other two modules and run on the >> fly. Now I compile my own BPF-like minilanguage to IR, then translate it >> to bitcode using llvm-as, then link it with other two modules with >> llvm-link and finally run with lli. I don`t want to use makefile I want >> to >> do everything on the fly in my compiler. Thanks. >> >> Radovan Baranec >> __...

...>>>> >>>>> CCIfType<[f64], CCCustom> >>>>> >>>>> where CCCustom is a new entity that tells the calling convention >>>>> code to to let the target do something not easily representable >>>>> in the tablegen minilanguage. >>>> >>>> I am thinking that this requires two changes: add a flag to >>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >>>> author an arbitrary CCAction by including the source directly in the >>>> TableGen mini-la...

...ructs the x86 code generator to use SSE3 > instructions > in fn7() whereas the code generator should not use SSE instructions > for function > fn8(). Can the names directly correspond with the current -mattr names somehow? It'd be good to avoid inventing yet another subtarget minilanguage :-). > > The Function Notes are not a place for all the llvm-gcc command line > options. > Each note should represent function specific choice or an option for > LLVM > passes. For example, optimize for size is appropriate because it > instructions > the LLVM passes t...

...t;>>>>> CCIfType<[f64], CCCustom> >>>>>> >>>>>> where CCCustom is a new entity that tells the calling convention >>>>>> code to to let the target do something not easily representable >>>>>> in the tablegen minilanguage. >>>>> >>>>> I am thinking that this requires two changes: add a flag to >>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>> to >>>>> author an arbitrary CCAction by including the source directly i...

...t;> CCIfType<[f64], CCCustom> >>>>>>> >>>>>>> where CCCustom is a new entity that tells the calling convention >>>>>>> code to to let the target do something not easily representable >>>>>>> in the tablegen minilanguage. >>>>>> >>>>>> I am thinking that this requires two changes: add a flag to >>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>> to >>>>>> author an arbitrary CCAction by including the...

...t;> >>>>>>>>> where CCCustom is a new entity that tells the calling >>>>>>>>> convention >>>>>>>>> code to to let the target do something not easily representable >>>>>>>>> in the tablegen minilanguage. >>>>>>>> >>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>>>> to >>>>>>>> autho...

...>>>>> >>>>>>>> where CCCustom is a new entity that tells the calling >>>>>>>> convention >>>>>>>> code to to let the target do something not easily representable >>>>>>>> in the tablegen minilanguage. >>>>>>> >>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>>> to >>>>>>> author an arbitrary CCAct...

...ntity that tells the calling >>>>>>>>>>> convention >>>>>>>>>>> code to to let the target do something not easily >>>>>>>>>>> representable >>>>>>>>>>> in the tablegen minilanguage. >>>>>>>>>> >>>>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a >>>>>>>>>> way >>&...

...tom is a new entity that tells the calling >>>>>>>>>> convention >>>>>>>>>> code to to let the target do something not easily >>>>>>>>>> representable >>>>>>>>>> in the tablegen minilanguage. >>>>>>>>> >>>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a >>>>>>>>> way >>>>>&gt...

...;>>>>>>>>>>>> convention >>>>>>>>>>>>> code to to let the target do something not easily >>>>>>>>>>>>> representable >>>>>>>>>>>>> in the tablegen minilanguage. >>>>>>>>>>>> >>>>>>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom >>>>>>>>&g...

...the calling >>>>>>>>>>>> convention >>>>>>>>>>>> code to to let the target do something not easily >>>>>>>>>>>> representable >>>>>>>>>>>> in the tablegen minilanguage. >>>>>>>>>>> >>>>>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a >>>>>>>>>>&g...

...;>>>>>>>>> convention >>>>>>>>>>>>>> code to to let the target do something not easily >>>>>>>>>>>>>> representable >>>>>>>>>>>>>> in the tablegen minilanguage. >>>>>>>>>>>>> >>>>>>>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom >>>>>>...