Bugzilla clang components for C

Currently, our bugzilla for Clang lists all of the various C++
standards supported by Clang as "components" for categorizing bugs,
but we do not have any C standard (or even just a generic C category).
I've seen this cause confusion twice within the past week, so I'm
hoping our bugzilla admins can help add one or more categories for C.

I propose that we add C as a catch-all category for C bugs, add C17
because it's the latest published standard, and C2x because it's the
next upcoming standard. I'm not certain if there's enough merit to
having C11, C99, and C89 as explicit categories and I'm a mildly
concerned about having too many component choices, but I'm not opposed
to adding them as well.

Additionally, it would be nice to fix C++'17 to be C++17 as a drive-by.

~Aaron

Hi Aaron,

Adapting the components in the bugzilla is pretty straightforward for the bugzilla admins and I am happy to do so when it’s clear how the components should be changed.
I’ve just fixed the C++'17 component name to now be C++17. Thanks for highlighting that.

Thanks,

Kristof

I added some before seeing this message, but we can change it later if
needed. I added: C, C11, C18 (apparently that's the official name, so
the first bug in that component should probably be Clang's -std=c17
option) and C2x. I decided the cut-off based on the C++ standards
supported, though that may be historical.

Cheers.

Tim.

> I propose that we add C as a catch-all category for C bugs, add C17
> because it's the latest published standard, and C2x because it's the
> next upcoming standard. I'm not certain if there's enough merit to
> having C11, C99, and C89 as explicit categories and I'm a mildly
> concerned about having too many component choices, but I'm not opposed
> to adding them as well.

I added some before seeing this message, but we can change it later if
needed.

Thank you!

I added: C, C11, C18 (apparently that's the official name, so
the first bug in that component should probably be Clang's -std=c17
option)

Heh, nope, it goes by both names thanks to a hitch with ISO. We
ratified in 2017 but the publication process didn't complete until
2018. We support both names, as does GCC, by design.

and C2x. I decided the cut-off based on the C++ standards
supported, though that may be historical.

I think this is reasonable enough.

Thanks, again!

~Aaron