On Tue, Oct 12, 2021 at 01:09:10PM +0200, Martin Jambor wrote: > The preferred way of communication is email posted to the mailing list > (sometimes CCing the people you think are most likely to reply) and I am > quite confident that people will read it and reply to reasonable > questions and review patches, even RFC patches. > > I think that the important OpenMP contributors could be persuaded to an > occasional - if perhaps not regular - call to discuss overall > architecture, milestones and even any hard-to-tackle problems, but you > need to ask them yourselves (hint: I CCed some). In the end of the day, > email should be the main channel, though.
Note, we had already in the past a GSoC project for OMPD in 2020, by Tony Sim. It wasn't finished, so nothing has been committed, but the student had GCC Copyright Assignment, so parts of what he has posted to the gcc-patches mailing list could be used for the project, either unmodified or modified (but I think changes from his private repository can't be used unless he agrees with that), but even if nothing that has been posted is used, it would be useful if you and your collegues read the OMPD threads on gcc-patches. Search in https://gcc.gnu.org/pipermail/gcc-patches/2020-June/thread.html#start https://gcc.gnu.org/pipermail/gcc-patches/2020-July/thread.html#start for threads where y2s1982 participated, to e.g. see what we've been looking for. One important part that was missing and is needed quite early is that it is testable and consumable, so while some of the students should work on the OMPD code in libgomp, somebody should also work on GDB support for OMPD (and for that it would be useful to talk to people on the gdb mailing list in sourceware.org and look for a mentor for that part of work there) and somebody ideally should work on either a GDB plugin or just GDB python scripts (and if needed some C code) and associated dejagnu infrastructure, so that it is also possible to test the OMPD library side in the libgomp testsuite. You can e.g. look how other parts of GCC testsuite use GDB, we have e.g. gcc/testsuite/gcc.dg/guality/* testsuite including gcc/testsuite/gcc.dg/guality/guality.exp driver for that that uses gcc/testsuite/lib/gcc-gdb-test.exp under the hood for running GDB on certain test and querying the debugger about values of certain expressions on certain lines, or e.g. libstdc++-v3/testsuite/libstdc++-prettyprinters/* with libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp driver tests printing of libstdc++ types in the debugger. Another option is writing some simple framework for the testing, but one needs to provide the various callbacks OMPD needs and those would need to use something like ptrace to talk to the inferior. Also, please see https://gcc.gnu.org/contribute.html Jakub
