search for: printregisteredtargetsforversion

In these days I’ve integrated llc code into my compiler. I had an undefined behaviour because when cl::AddExtraVersionPrinter(TargetRegistry::printRegisteredTargetsForVersion) is called, the modules I give to the code in input to compile got somehow “corrupted" by this function. It is definitely an undefined behaviour because every debug I do, modules gets different changes, producing different assertions every run: - Target triple string gets changes with null ch...

...http://llvm.org/bugs/ cheers, --renato On 27 March 2016 at 17:15, Lorenzo Laneve via llvm-dev <llvm-dev at lists.llvm.org> wrote: > In these days I’ve integrated llc code into my compiler. > > I had an undefined behaviour because when > cl::AddExtraVersionPrinter(TargetRegistry::printRegisteredTargetsForVersion) > is called, the modules I give to the code in input to compile got somehow > “corrupted" by this function. > It is definitely an undefined behaviour because every debug I do, modules > gets different changes, producing different assertions every run: > > - Target triple str...

...-renato > > On 27 March 2016 at 17:15, Lorenzo Laneve via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> In these days I’ve integrated llc code into my compiler. >> >> I had an undefined behaviour because when >> cl::AddExtraVersionPrinter(TargetRegistry::printRegisteredTargetsForVersion) >> is called, the modules I give to the code in input to compile got somehow >> “corrupted" by this function. >> It is definitely an undefined behaviour because every debug I do, modules >> gets different changes, producing different assertions every run: >> &gt...

Patch for review. On Mon, Aug 21, 2017 at 11:45 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> wrote: > Ping. > > Still working on preparing code for review. Will have a patch for review > ready in the coming days. > > PL > > On Tue, Aug 15, 2017 at 12:06 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> > wrote: > >> Hi, >> >> >>