search for: cs97g

Also you might need to check use PostRASchedulerList or PostMachineScheduler, PostRASchedulerList is considered deprecated as mentioned in [1]. [1] http://lists.llvm.org/pipermail/llvm-dev/2017-April/112348.html HTH, chenwj 2017-06-10 4:03 GMT+08:00 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw>: > Not saying I am totally understand how thing works, but I think you're > misleading > by the DAG in the class name ScheduleDAGInstrs. I only see MachineInstrs > there, no SDNode. And the comment of ScheduleDAGInstrs says, > > /// A ScheduleDAG for s...

Thanks :) From: 陳韋任 [mailto:chenwj.cs97g at g2.nctu.edu.tw] Sent: 14 April 2017 12:53 To: Martin J. O'Riordan <martin.oriordan at movidius.com> Cc: LLVM Developers <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Options for timing passes in LLVM? Refer to `llc` document [1], it would be `--time-passes`. [1] h...

> > Of course, you want to duplicate as little of the generic scheduling logic > as you can. So I think the challenge is how to expose the > generic scheduler's functionality as a base class or composition of > utilities so that defining your strategy doesn't require too much > copy-paste. ​Isn't GCNMaxOccupancySchedStrategy [1] already an example on using

Hi Bekket, I don't see any use case in the codebase adding clEnumValEnd at the end of list (for example, [1]), I also don't see there is clEnumValEnd. Do I miss something here? [1] http://llvm.org/doxygen/DwarfDebug_8cpp_source.html Regards, chenwj 2017-06-06 9:53 GMT+08:00 Bekket McClane via llvm-dev < llvm-dev at lists.llvm.org>: > Hi, > > Can anyone help reviewing

2018-01-16 21:03 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > On 16 January 2018 at 12:23, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > > Do we have to emit directives in the epilogue, too? One of my test case > fail > > due to the directives in the epilogue have been executed. After removing > > them from epilogue, the exception is caught as expected. > > Emitting directiv...

...contribute. I found this email containing backporting timeline for 4.0.1 (already done): http://lists.llvm.org/pipermail/llvm-dev/2017-March/111530.html >From email, it is not clear to me whether we have upcoming 4.0.2 or not. Thanks! Yonghong On Fri, Jul 14, 2017 at 2:27 PM, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > I have no experience on backporting. However, the patches you want > only involves BPF backend itself, > I don't see any particular trouble of backporting. I would suggest you > start working on the latest LLVM > release, i.e., 4.0, then run the tes...

...g to do this "nested flattening". It seems that I need a post-dominator tree-based algorithm to flatten the nested loops from the innermost to the outermost, level by level. Is there any feature already existed in LLVM tools? Or similar? On Sun, Oct 22, 2017 at 2:31 AM, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > If the inner loop can be flatten [1] (not sure if I use the right word), > which means transforming the nested loop into 1-level loop, I think you can > continue using your pass on it. > > [1] https://stackoverflow.com/questions/18369260/flattening- &g...

...-readobj" I see no problem - but when using the metadata I have no clue how to find variables on the stack - there are only this intrinsics, but I don't know how to handle them. Maybe I asked the wrong question :/ From: Reid Kleckner <rnk at google.com> To: 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> Cc: bjoern.gaier at horiba.com, LLVM Developers Mailing List <llvm-dev at lists.llvm.org> Date: 17.01.2018 18:29 Subject: Re: [llvm-dev] Dumping debug information from BC files The debug information is actually still in a different format in the .bc fil...

Hello, I have followed steps given in - https://stackoverflow.com/questions/29910051/integrating-llvm-passes/48142693#48142693 <https://stackoverflow.com/questions/29910051/integrating-llvm-passes/48142693#48142693>, to integrate my pass with pass manager and run it with clang. I am able to run my pass with opt - opt -mypass but when I try to run it with clang, I always get an error -

...` which will disable the verify check. On Sat, 21 Oct 2017 at 23:54 Dipanjan Das via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Yes, that definitely works. Wanted to know if there's a switch for file > output or not. > > On 21 October 2017 at 23:45, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > >> Just use Unix IO redirect? `llc -mllvm -print-after-all &> a.txt` >> >> 2017-10-22 14:17 GMT+08:00 Dipanjan Das via llvm-dev < >> llvm-dev at lists.llvm.org>: >> >>> >>> Seems like "-mllvm -print-...

Thank You Chen ! On Thu, Jun 22, 2017 at 5:21 PM 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > Perhaps you can refer to [1]. Function name should be a global one. > > [1] http://llvm.org/docs/LangRef.html#identifiers > > HTH, > chenwj > > > 2017-06-22 16:35 GMT+08:00 SANJAY SRIVALLABH SINGAPURAM via llvm-dev < > llvm-dev at lis...

On 16 January 2018 at 13:41, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > bar: > > .cfi_def_cfa_offset 16 > epilogue > > _Unwind_Resume > > > > The lookup phase of exception handling is fine. However, something goes > wrong in cleanup phase. The reason is the unwinder evaluates CFI directives &gt...

...eel free to comment on it. Alex, could you add D42178 into your review corner? I hope someone who has more exception handling experience can review on it as well. Thanks. 2018-01-17 3:41 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > On 16 January 2018 at 13:41, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > > bar: > > > > .cfi_def_cfa_offset 16 > > epilogue > > > > _Unwind_Resume > > > > > > > > The lookup phase of exception handling is fine. However, something goes > > wrong in cleanup phase....

Hello This link didn't work for me. As I am getting error whose meaning is - there are no options as -arch i386 -arch x86_64. How should I remove this error? On Wed, Mar 22, 2017 at 6:11 PM, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > Hi Aayushi, > > Seems the link [1] answers your question. > > [1] http://stackoverflow.com/questions/28640585/build- > install-llvm-clang-with-both-32-64-bit-support-libraries > > HTH, > chenwj > > > 2017-03-22 14:43 GMT+08:00 Aa...

...use to add dwarf info to bc file. Can you show me the demo or example, is there any info about how to use these classes step by step. BR Owen 发件人: Andrew Kelley [mailto:superjoe30 at gmail.com] 发送时间: 2017年11月15日 12:51 收件人: Wuweijia <wuweijia at huawei.com> 抄送: 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw>; llvm-dev at lists.llvm.org; Fanbohao <fanbohao at huawei.com> 主题: Re: [llvm-dev] hi, Is there any solution about how to add some dwarf info to the IR bitcode file. Have a look at the DebugInfo API. include/llvm/DebugInfo/* It requires using the C++ API instead of the...

...> On Jan 11, 2018, at 6:41 PM, sangeeta chowdhary < > sangitachowdhary at gmail.com> wrote: > > Can you please tell me when I need to give this option and how. I am sorry > I am new to this. Thank you so much for responding. > > On Jan 11, 2018, at 6:28 PM, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > > -mllvm > > > > -- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180113/c9b780f5/attac...

On 16 January 2018 at 12:23, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote: > Do we have to emit directives in the epilogue, too? One of my test case fail > due to the directives in the epilogue have been executed. After removing > them from epilogue, the exception is caught as expected. Emitting directives in the epilogue is hard be...

The debug information is actually still in a different format in the .bc file, it is LLVM metadata. I think the best reference for it is here: https://llvm.org/docs/SourceLevelDebugging.html#ccxx-frontend You can dump it just by disassembling the .bc file to textual IR using llvm-dis and examining the !DI* metadata nodes. You will have to run the file through llc to generate an object file to

...yedBasicBlock(BA)); BB = DelayedBBs.back().TempBB.get(); } else { BB = cast_or_null<BasicBlock>(mapValue(BA.getBasicBlock())); } return getVM()[&BA] = BlockAddress::get(F, BB ? BB : BA.getBasicBlock()); } Thanks, Pei On 6/28/17, 10:59 AM, "陳韋任" <chenwj.cs97g at g2.nctu.edu.tw> wrote: 2017-06-29 1:55 GMT+08:00 Pei Wang via llvm-dev <llvm-dev at lists.llvm.org>: > Bruce, > > > > Thanks for the explanation. But based on my inspection on the source code, > it seems that materialization is related to l...

Just use Unix IO redirect? `llc -mllvm -print-after-all &> a.txt` 2017-10-22 14:17 GMT+08:00 Dipanjan Das via llvm-dev < llvm-dev at lists.llvm.org>: > > Seems like "-mllvm -print-after-all" does the trick. Is there any switch > that dumps the output to a file instead of console? > > On 21 October 2017 at 21:33, Dipanjan Das <mail.dipanjan.das at