public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vt at altlinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114507] New: FR: Randomize order of evluation of function of arguments Date: Thu, 28 Mar 2024 05:28:53 +0000 [thread overview] Message-ID: <bug-114507-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114507 Bug ID: 114507 Summary: FR: Randomize order of evluation of function of arguments Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: vt at altlinux dot org Target Milestone: --- There is class of bugs when, for example, printf is called with several functions that output to the same static buffer overwriting each others result. This could be hard to detect in legacy code, for example there is nested calls invisible from top level functions, also compiler tend to create the same call order, so if overwriting is order dependent it could be undetected for years and appear on some rare architecture when compiler reorder calls [1]. To detect this kind of bugs it would be useful to have compiler option to reorder function arguments evaluation randomly. With this test suites will have a _chance_ to detect the bugs even on one architecture. [1] https://lore.kernel.org/all/20240323091717.dtsioyvjnhl5dtyv@altlinux.org/
next reply other threads:[~2024-03-28 5:28 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 5:28 vt at altlinux dot org [this message] 2024-03-28 5:30 ` [Bug c/114507] " sjames at gcc dot gnu.org 2024-03-28 5:31 ` sjames at gcc dot gnu.org 2024-03-28 5:35 ` pinskia at gcc dot gnu.org 2024-03-28 5:37 ` pinskia at gcc dot gnu.org
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=bug-114507-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).