================ @@ -0,0 +1,7 @@ +// RUN: %clang_cc1 -foverflow-behavior-types -std=c++11 -ast-print %s -o - | FileCheck %s + +extern int __attribute__((overflow_behavior(no_wrap))) a; +extern int __attribute__((overflow_behavior(wrap))) b; + +// CHECK: extern __no_wrap int a; +// CHECK: extern __wrap int b; ---------------- JustinStitt wrote:
@mizvekov Let me know what you think about https://github.com/llvm/llvm-project/pull/148914/commits/0042195b7c9f06b70ffb24c8d76d1aaed6ee3dee. I use the full attribute spelling for AST type printer and I use a shorthand in diagnostics. I had to make a method `TryConvertOverflowBehaviorTypeToDiagnosticString()` to drop into `ConvertTypeToDiagnosticString()` which sort of matches how `ext_vector` types are handled to be pretty printed. round-trip test is all good. Im happy to iterate further too. let me know what you think. https://github.com/llvm/llvm-project/pull/148914 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
