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/107743] expmed: extract_bit_field_1: maybe-uninitialized warning Date: Fri, 18 Nov 2022 08:10:57 +0000 [thread overview] Message-ID: <bug-107743-4-d9cGLJq3JN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107743-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107743 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Is that with release checking? The code around this is /* Extraction of a full MODE1 value can be done with a subreg as long as the least significant bit of the value is the least significant bit of either OP0 or a word of OP0. */ if (!MEM_P (op0) && !reverse && op0_mode.exists (&imode)) { rtx sub = extract_bit_field_as_subreg (mode1, op0, imode, bitsize, bitnum); if (sub) return convert_extracted_bit_field (sub, mode, tmode, unsignedp); } where template<typename T> template<typename U> inline bool opt_mode<T>::exists (U *mode) const { if (m_mode != E_VOIDmode) { *mode = T (typename mode_traits<T>::from_int (m_mode)); return true; } return false; } so it's unobvious how 'imode' is uninitialized.
next prev parent reply other threads:[~2022-11-18 8:10 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-18 7:27 [Bug middle-end/107743] New: " aldot at gcc dot gnu.org 2022-11-18 8:10 ` rguenth at gcc dot gnu.org [this message] 2022-11-19 18:01 ` [Bug middle-end/107743] " aldot 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-107743-4-d9cGLJq3JN@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).