Re: [PATCH 0/5] Remove a few hurdles of compiling with clang

[Yao Qi <qiyaoltc at gmail dot com>]

Eli Zaretskii <eliz@gnu.org> writes:

> Specifically, this text sounds too vague to me to be considered
> "policy".  Too much is left to judgment calls.  But if everyone else
> is happy, I won't insist on prolonging this discussion.
>

It is vague because the tasks this "policy" about are not clear.  It is
unlike other polices like "-Werror policy" or "GDB's #include file
policy", their tasks are quite clear, so it is possible to give clear
actionable rules.  However, it is still unknown that what are we going
to do to make GDB built with compilers other than GCC.  It was just
raised by Simon's patches several days ago.  We need to write this vague
policy down, and don't discourage people building GDB with different
compilers.

Patches are still reviewed, and some of them may be controversial.  As
we have some concrete bad/good patches, we can have some specific rules
in this policy.

>> I also looked for the place to add this policy.  Looks the most relevant
>> page is https://sourceware.org/gdb/wiki/Internals%20Compiler-Warnings
>
> I would suggest to consider a new page, or maybe make this part of
> coding standards.

OK, let me create a new page, "Build GDB with different compilers" in
chapter "Miscellaneous guidelines" in 
https://sourceware.org/gdb/wiki/Internals  It has few to do with coding
standards.  People should still write the code in the same way,
specified in our coding standards, although GDB can be built by
different compilers.

-- 
Yao (齐尧)