[clang] [llvm] demangle function names in trace files (PR #87626)

2024-07-10 Thread Jamie Schmeiser via cfe-commits
https://github.com/jamieschmeiser closed https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-07-10 Thread Jamie Schmeiser via cfe-commits
jamieschmeiser wrote: To directly answer your question: No, deliver this. If you find loop entries in the future, then consider expanding it. Also, the link to that here may help others should then decide to expand this work. https://github.com/llvm/llvm-project/pull/87626

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-07-10 Thread Jamie Schmeiser via cfe-commits
jamieschmeiser wrote: @Trass3r, sorry, I didn't realize that you were waiting on me... I had already approved this so you can go ahead and merge it. I was just pointing you at possibly related work that might interest you. Even if you decide to expand this work, I would suggest delivering

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-05-06 Thread Jamie Schmeiser via cfe-commits
jamieschmeiser wrote: You may want to look at https://github.com/llvm/llvm-project/pull/90756 https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-05-06 Thread Jamie Schmeiser via cfe-commits
jamieschmeiser wrote: Thanks, I looked over things and they still look good. https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-04-18 Thread Jamie Schmeiser via cfe-commits
jamieschmeiser wrote: Yes, the way to proceed is to rebase and resolve the conflicts. As far as the formatting changes, I think you should go with what the formatter wants. Everyone has different opinions about things like spacing, line length, etc and will never agree. The formatter keeps

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-04-09 Thread Jamie Schmeiser via cfe-commits
https://github.com/jamieschmeiser approved this pull request. LGTM, thanks https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-04-05 Thread Jamie Schmeiser via cfe-commits
https://github.com/jamieschmeiser edited https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-04-05 Thread Jamie Schmeiser via cfe-commits
https://github.com/jamieschmeiser requested changes to this pull request. See comments in response https://github.com/llvm/llvm-project/pull/87626 ___ cfe-commits mailing list cfe-commits@lists.llvm.org

[clang] [llvm] demangle function names in trace files (PR #87626)

2024-04-05 Thread Jamie Schmeiser via cfe-commits
@@ -1495,7 +1496,7 @@ void TimeProfilingPassesHandler::registerCallbacks( } void TimeProfilingPassesHandler::runBeforePass(StringRef PassID, Any IR) { - timeTraceProfilerBegin(PassID, getIRName(IR)); + timeTraceProfilerBegin(PassID, demangle(getIRName(IR)));

[clang] 5e3ac79 - Loop names used in reporting can grow very large

2022-09-09 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2022-09-09T13:45:14-04:00 New Revision: 5e3ac7969039678fc017a5599b051ea2b78075a4 URL: https://github.com/llvm/llvm-project/commit/5e3ac7969039678fc017a5599b051ea2b78075a4 DIFF:

[clang] efbf013 - Only issue warning for subtraction involving null pointers on live code paths

2022-06-03 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2022-06-03T10:10:37-04:00 New Revision: efbf0136b4108692ddd1a852b3f5b232c10d2097 URL: https://github.com/llvm/llvm-project/commit/efbf0136b4108692ddd1a852b3f5b232c10d2097 DIFF:

[clang] c3c1826 - Set TargetCPUName for AIX to default to pwr7.

2021-07-29 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2021-07-29T09:59:24-04:00 New Revision: c3c1826c310c42244c7cad8d0c6af3a368fcd064 URL: https://github.com/llvm/llvm-project/commit/c3c1826c310c42244c7cad8d0c6af3a368fcd064 DIFF:

[clang] 9cb00b9 - Reland Produce warning for performing pointer arithmetic on a null pointer.

2021-07-20 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2021-07-20T10:12:20-04:00 New Revision: 9cb00b9ecbe74d19389a5818d61ddee328afe031 URL: https://github.com/llvm/llvm-project/commit/9cb00b9ecbe74d19389a5818d61ddee328afe031 DIFF:

[clang] 73840f9 - thread_local support for AIX

2021-07-19 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2021-07-19T10:03:22-04:00 New Revision: 73840f9f81413f21d3c8fab0ed85917aca2b5d34 URL: https://github.com/llvm/llvm-project/commit/73840f9f81413f21d3c8fab0ed85917aca2b5d34 DIFF:

[clang] 136ced4 - When vector is found as a type or non-type id, check if it is really the altivec vector token.

2021-05-20 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2021-05-20T12:39:04-04:00 New Revision: 136ced498ba84f6b6126051626e319f18ba740f5 URL: https://github.com/llvm/llvm-project/commit/136ced498ba84f6b6126051626e319f18ba740f5 DIFF:

[clang] dfc1e31 - Produce warning for performing pointer arithmetic on a null pointer.

2021-05-11 Thread Jamie Schmeiser via cfe-commits
Author: Jamie Schmeiser Date: 2021-05-11T11:29:50-04:00 New Revision: dfc1e31d49fe1380c9bab43373995df5fed15e6d URL: https://github.com/llvm/llvm-project/commit/dfc1e31d49fe1380c9bab43373995df5fed15e6d DIFF: