From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] OpenPOSIX: Add common entry point function for all tests
Date: Tue, 21 Apr 2026 12:26:28 +0200 [thread overview]
Message-ID: <20260421102628.GA505866@pevik> (raw)
In-Reply-To: <4b48d98e-9e2d-4ee9-8d1f-b92020357b47@suse.cz>
> On 4/17/26 16:44, Petr Vorel wrote:
> > > > > This changes verbatim POSIX specification text. The assertions.xml files
> > > > > quote the POSIX standard, which defines behaviour relative to main() — the C
> > > > > entry point, not an LTP-internal function name. Revert these hunks in both
> > > > > pthread_create/assertions.xml and pthread_exit/assertions.xml.
> > > > +1
> > > This "issue" is nonsense. I've checked the XML files and the assertions are
> > > still correct as is regardless of renaming a few functions. The
> > > pthread_create() and pthread_exit() specification applies special treatment
> > > to the main thread and adding one more function call between the main()
> > > function and the test code does not change that.
> > I understood that spec talks about main() as a specific C startup function.
> > But ok, I was probably wrong.
> The spec DOES talk about main() as the C process startup function. But the
> AI for some reason believes that my patch can somehow rewrite the POSIX
> standard itself.
I understand it differently: keep main() because that's the C entry function
and any reader of assertions.xml does not really care about our implementation
that we wrap main() with other function for our internal purposes of other test
scenario.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-21 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260416144213.27221-1-mdoucha@suse.cz>
2026-04-16 18:36 ` [LTP] OpenPOSIX: Add common entry point function for all tests linuxtestproject.agent
2026-04-17 13:09 ` Petr Vorel
2026-04-17 13:35 ` Martin Doucha
2026-04-17 14:44 ` Petr Vorel
2026-04-21 8:58 ` Martin Doucha
2026-04-21 10:26 ` Petr Vorel [this message]
2026-04-17 14:33 ` Petr Vorel
2026-04-16 18:53 ` [LTP] [PATCH] " Petr Vorel
2026-04-17 0:30 ` Li Wang via ltp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260421102628.GA505866@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox