[libc][docs] generate docs for signal.h

[nickdesaulniers]

Using n3096 Section 7.14, we should fill out the function list in a new file called libc/utils/docgen/signal.json (so that we have entries about which standard section talks about what, similar to libc/utils/docgen/fenv.json).

Then we should run ./libc/utils/docgen/docgen.py signal.h > libc/docs/signal.rst to create a page for signal.h.

Then we should add a link to signal in libc/docs/index.rst so that it's linked from libc.llvm.org (similar to fenv).

[llvmbot]

Hi!

This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

1. Check that no other contributor has already been assigned to this issue. If you believe that no one is actually working on it despite an assignment, ping the person. After one week without a response, the assignee may be changed.
2. In the comments of this issue, request for it to be assigned to you, or just create a pull request after following the steps below. Mention this issue in the description of the pull request.
3. Fix the issue locally.
4. Run the test suite locally. Remember that the subdirectories under test/ create fine-grained testing targets, so you can e.g. use make check-clang-ast to only run Clang's AST tests.
5. Create a Git commit.
6. Run git clang-format HEAD~1 to format your changes.
7. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation. Mention this issue in the description of the pull request.

If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.

[llvmbot]

@llvm/issue-subscribers-good-first-issue

Author: Nick Desaulniers (nickdesaulniers)

Details

Using [n3096](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3096.pdf) Section 7.14, we should fill out the function list in a new file called libc/utils/docgen/signal.json (so that we have entries about which standard section talks about what, similar to libc/utils/docgen/fenv.json).

Then we should run ./libc/utils/docgen/docgen.py signal.h > libc/docs/signal.rst to create a page for signal.h.

Then we should add a link to signal in libc/docs/index.rst so that it's linked from libc.llvm.org (similar to fenv).

[llvmbot]

@llvm/issue-subscribers-libc

Author: Nick Desaulniers (nickdesaulniers)

Details

Using [n3096](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3096.pdf) Section 7.14, we should fill out the function list in a new file called libc/utils/docgen/signal.json (so that we have entries about which standard section talks about what, similar to libc/utils/docgen/fenv.json).

Then we should run ./libc/utils/docgen/docgen.py signal.h > libc/docs/signal.rst to create a page for signal.h.

Then we should add a link to signal in libc/docs/index.rst so that it's linked from libc.llvm.org (similar to fenv).

[nickdesaulniers]

For this, we'll also need to modify libc/utils/docgen/docgen.py to recurse into linux/ directories to see what functions "exist" or are implemented.

[simonzgx]

I'd like to work on these two issues, including #87833.

[zdumonts]

I'd like to work on these two issues, including #87833.

Hi, I just submitted a pr for #87833. Are you working on either issue as of now?

[simonzgx]

I'd like to work on these two issues, including #87833.

Hi, I just submitted a pr for #87833. Are you working on either issue as of now?

Yeah.
It's ok, I'll open a PR for the current issue later.