C++ Logo

liaison

Advanced search

Re: [isocpp-wg14/wg21-liaison] [isocpp-core] Review of CWG2970 Races with volatile sig_atomic_t bit-fields

From: Joseph Myers <josmyers_at_[hidden]>
Date: Tue, 21 Jan 2025 18:09:47 +0000 (UTC)
On Tue, 21 Jan 2025, Jā‚‘ā‚™ā‚› Gustedt via Liaison wrote:

> > Does WG14 have an issue tracker where I can report such issues when
> > they're discovered on the C++ side?
>
> We have, but it is private to WG14 because of copyright
> scare. According to ISO policies it should at least be possible to
> extend this to all SC22, I'd think. Perhaps we should talk to Robert
> and David about this.

I do not think the issue tracker in the private GitLab for the C standard
sources is suitable for technical issues, because those need to be
discussed in the committee rather than having an editor apply a fix
unilaterally without such discussion. It's only suitable for the subset
of editorial issues that can reasonably be resolved by the editors without
needing further reference to the committee (that's what I use it for, if I
have an editorial issue for which I don't have a LaTeX fix ready but don't
think committee input is needed for either).

I believe JeanHeyd has been working on an issue tracker to accompany the
system for C-numbered documents. I've accumulated a list of about 25-30 C
standard issues over the past several years (mostly technical, a few
editorial issues where I think committee input is needed) ready to file in
such a tracker once it's available. That issue tracker is supposed to
have everything apart from the user authentication database in a public
git repository. I also have a preliminary conversion of 547 issues filed
against past versions of the C standard and related documents to JSON
metadata plus Markdown text, for inclusion in such an issue tracker.

-- 
Joseph S. Myers
josmyers_at_[hidden]

Received on 2025-01-21 18:09:55