Changes in debug_private.c

4821508d - Revert "DebugInfo: Fully integrate ctor type homing into 'limited' debug info"

Fri, 24 Jun 2022 16:47:57 +0000

Revert "DebugInfo: Fully integrate ctor type homing into 'limited' debug info"Reverting to simplify some Google-internal rollout issues. Will recommitin a week or two.This reverts commit 517bbc64dbe493644eff8d55fd9566435e930520. List of files: /llvm-project-15.0.7/clang/test/OpenMP/debug_private.c

517bbc64 - DebugInfo: Fully integrate ctor type homing into 'limited' debug info

Wed, 22 Jun 2022 23:26:23 +0000

DebugInfo: Fully integrate ctor type homing into 'limited' debug infoSimplify debug info back to just "limited" or "full" by rolling the ctortype homing fully into the "limited" debug info.Also fix a bug I found along the way that was causing ctor type homingto kick in even when something could be vtable homed (where vtablehoming is stronger/more effective than ctor homing) - fixing at the sametime as it keeps the tests (that were testing only "limited non ctor"homing and now test ctor homing) passing. List of files: /llvm-project-15.0.7/clang/test/OpenMP/debug_private.c

532dc62b - [OpaquePtrs][Clang] Add -no-opaque-pointers to tests (NFC)

Thu, 07 Apr 2022 10:03:55 +0000

[OpaquePtrs][Clang] Add -no-opaque-pointers to tests (NFC)This adds -no-opaque-pointers to clang tests whose output willchange when opaque pointers are enabled by default. This isintended to be part of the migration approach described inhttps://discourse.llvm.org/t/enabling-opaque-pointers-by-default/61322/9.The patch has been produced by replacing %clang_cc1 with%clang_cc1 -no-opaque-pointers for tests that fail with opaquepointers enabled. Worth noting that this doesn't cover all tests,there's a remaining ~40 tests not using %clang_cc1 that will needa followup change.Differential Revision: https://reviews.llvm.org/D123115 List of files: /llvm-project-15.0.7/clang/test/OpenMP/debug_private.c

37639b72 - [OpenMP][FIX] Emit debug declares only if debug info is available

Sat, 08 Jan 2022 19:53:39 +0000

[OpenMP][FIX] Emit debug declares only if debug info is availableThe `EmitDeclareOfAutoVariable` introduced in D114504 and D115510 has aprecondition that cannot be violated. It is unclear if we should call itdirectly given the sparse usage in clang but for now we should at leastnot crash if the debug info kind is too low.Fixes #52938.Differential Revision: https://reviews.llvm.org/D116865 List of files: /llvm-project-15.0.7/clang/test/OpenMP/debug_private.c

36cb7477 - [clang][OpenMP][DebugInfo] Debug support for private variables inside an OpenMP task construct

Wed, 24 Nov 2021 05:08:19 +0000

[clang][OpenMP][DebugInfo] Debug support for private variables inside an OpenMP task constructCurrently variables appearing inside private/firstprivate/lastprivateclause of openmp task construct are not visible inside lldb debugger.This is because compiler does not generate debug info for it.Please consider the testcase debug_private.c attached with patch.``` 28 #pragma omp task shared(res) private(priv1, priv2) firstprivate(fpriv) 29 { 30 priv1 = n; 31 priv2 = n + 2; 32 printf("Task n=%d,priv1=%d,priv2=%d,fpriv=%d\n",n,priv1,priv2,fpriv); 33-> 34 res = priv1 + priv2 + fpriv + foo(n - 1); 35 } 36 #pragma omp taskwait 37 return res;(lldb) p priv1error: :1:1: use of undeclared identifier 'priv1'priv1^(lldb) p priv2error: :1:1: use of undeclared identifier 'priv2'priv2^(lldb) p fpriverror: :1:1: use of undeclared identifier 'fpriv'fpriv^```After the current patch, lldb is able to show the variables```(lldb) p priv1(int) $0 = 10(lldb) p priv2(int) $1 = 12(lldb) p fpriv(int) $2 = 14```Reviewed By: djtodoroDifferential Revision: https://reviews.llvm.org/D114504 List of files: /llvm-project-15.0.7/clang/test/OpenMP/debug_private.c