system clang's -debugger-tuning setting: Is the default gdb setting intended?

[Curiosity, not an objection.]

It appears that most likely all FreeBSD platforms get the gdb
setting by default . . .

armv7:

# cc -v main.c
FreeBSD clang version 17.0.6 (https://github.com/llvm/llvm-project.git llvmorg-17.0.6-0-g6009708b4367)
Target: armv7-unknown-freebsd15.0-gnueabihf
. . . -debugger-tuning=gdb . . . -x c main.c
. . .

aarch64:

# cc -v main.c
FreeBSD clang version 17.0.6 (https://github.com/llvm/llvm-project.git llvmorg-17.0.6-0-g6009708b4367)
Target: aarch64-unknown-freebsd15.0
. . . -debugger-tuning=gdb . . . -x c main.c
. . .

amd64:

# cc -v main.c
FreeBSD clang version 17.0.6 (https://github.com/llvm/llvm-project.git llvmorg-17.0.6-0-g6009708b4367)
Target: x86_64-unknown-freebsd15.0
. . . -debugger-tuning=gdb . . . -x c main.c

FYI:

QUOTE of https://clang.llvm.org/docs/UsersManual.html#controlling-debugger-tuning
Controlling Debugger “Tuning”
While Clang generally emits standard DWARF debug info (http://dwarfstd.org), different debuggers may know how to take advantage of different specific DWARF features. You can “tune” the debug info for one of several different debuggers.

-ggdb, -glldb, -gsce, -gdbx
Tune the debug info for the gdb, lldb, Sony PlayStation® debugger, or dbx, respectively. Each of these options implies -g. (Therefore, if you want both -gline-tables-only and debugger tuning, the tuning option must come first.)
END QUOTE

===
Mark Millard
marklmi at yahoo.com