public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/85927] ud2 instruction generated starting with gcc 8 Date: Fri, 31 Dec 2021 10:25:34 +0000 [thread overview] Message-ID: <bug-85927-4-s4GAZoXhVK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85927-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85927 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |uros at gcc dot gnu.org --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The ud2 is there since naked has been implemented for x86 in PR25967. It is true it is a kind of debugging aid, so perhaps more suitable for sanitization or if we add some option to decide preferred behavior on e.g. __builtin_unreachable or for detected UB in the code (whether to use __builtin_unreachable with its current behavior, just assume it doesn't happen and don't emit anything in there, or whether to act as __builtin_trap etc.). But without it e.g. the reporter wouldn't know so easily the function is invalid and won't work correctly.
prev parent reply other threads:[~2021-12-31 10:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85927-4@http.gcc.gnu.org/bugzilla/> 2021-12-31 10:07 ` pskocik at gmail dot com 2021-12-31 10:25 ` jakub at gcc dot gnu.org [this message]
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-85927-4-s4GAZoXhVK@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).