public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106811] New: GENERIC and GIMPLE IL undefined behavior needs documenting Date: Fri, 02 Sep 2022 06:49:53 +0000 [thread overview] Message-ID: <bug-106811-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106811 Bug ID: 106811 Summary: GENERIC and GIMPLE IL undefined behavior needs documenting Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- Undefined behavior triggered by the GENERIC operations from tree.def (also used in GIMPLE) need to be documented. In general we follow C here, including GCCs implementation defined behavior here, but not all C undefined behavior cases are exploited by the middle-end so the state of those cases is not clear. We need - a list of operations with undefined behavior cases that are currently exploited or seen as OK to exploit - a list of operations where C documents undefined behavior cases but the middle-end conciously defines some implementation defined behavior (which should not be target specific) - middle-end predicates that can be used to check - variants of the operations with (implementation) defined behavior probably best in generic.texi with cross reference from gimple.texi Note for RTL operations doing the same is necessary.
next reply other threads:[~2022-09-02 6:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-02 6:49 rguenth at gcc dot gnu.org [this message] 2022-11-02 9:59 ` [Bug middle-end/106811] " nunoplopes at sapo dot pt 2022-11-05 14:22 ` rguenther at suse dot de 2022-11-07 18:07 ` nunoplopes at sapo dot pt 2022-11-07 18:17 ` rguenther at suse dot de 2023-09-15 10:22 ` rguenth 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-106811-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).