public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rogerio.souza at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/105593] New: avx512 math function raises uninitialized variable warning Date: Fri, 13 May 2022 14:35:19 +0000 [thread overview] Message-ID: <bug-105593-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105593 Bug ID: 105593 Summary: avx512 math function raises uninitialized variable warning Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: rogerio.souza at gmail dot com Target Milestone: --- When using avx512 math function we got the following warning: /<gcc_path>/lib/gcc/x86_64-redhat-linux/12.1.0/include/avx512fintrin.h:6994:10: error: '__Y' may be used uninitialized [-Werror=maybe-uninitialized] The code that triggers the error is the one below, from file avx512fintrin.h: 202 extern __inline __m512i 203 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) 204 _mm512_undefined_epi32 (void) 205 { 206 __m512i __Y = __Y; // Uninitialized variable "__Y" 207 return __Y; 208 } Should this code be reviewed? Using "-Wno-uninitialized" prevents this warning from happening.
next reply other threads:[~2022-05-13 14:35 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-13 14:35 rogerio.souza at gmail dot com [this message] 2022-05-13 14:42 ` [Bug target/105593] " pinskia at gcc dot gnu.org 2022-05-13 14:43 ` pinskia at gcc dot gnu.org 2022-05-13 16:58 ` rogerio.souza at gmail dot com 2022-05-13 17:04 ` rogerio.souza at gmail dot com 2022-05-16 7:16 ` [Bug c++/105593] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-06-01 19:36 ` [Bug c++/105593] " jason at gcc dot gnu.org 2022-06-02 6:41 ` rguenth at gcc dot gnu.org 2022-06-23 16:18 ` rogerio.souza at gmail dot com 2022-11-22 19:14 ` pinskia at gcc dot gnu.org 2023-01-12 8:09 ` rguenth at gcc dot gnu.org 2023-01-12 11:44 ` jay+ggcc@jp-hosting.net 2023-01-12 14:03 ` jakub at gcc dot gnu.org 2023-01-12 14:26 ` jakub at gcc dot gnu.org 2023-01-12 15:10 ` jakub at gcc dot gnu.org 2023-01-16 8:41 ` cvs-commit at gcc dot gnu.org 2023-01-16 8:42 ` cvs-commit at gcc dot gnu.org 2023-01-16 9:04 ` jakub at gcc dot gnu.org 2023-01-29 15:15 ` jay+ggcc@jp-hosting.net 2023-01-30 17:46 ` jakub at gcc dot gnu.org 2023-01-31 8:21 ` cvs-commit at gcc dot gnu.org 2023-01-31 10:53 ` jay+ggcc@jp-hosting.net 2023-01-31 11:23 ` jakub at gcc dot gnu.org 2023-01-31 11:30 ` jay+ggcc@jp-hosting.net 2023-02-10 13:21 ` jakub at gcc dot gnu.org 2023-02-10 15:02 ` mpolacek at gcc dot gnu.org 2023-02-10 15:13 ` jakub at gcc dot gnu.org 2023-02-10 15:15 ` mpolacek at gcc dot gnu.org 2023-02-10 15:16 ` jakub at gcc dot gnu.org 2023-02-10 15:18 ` mpolacek at gcc dot gnu.org 2023-02-10 15:22 ` jakub at gcc dot gnu.org 2023-02-10 17:47 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:47 ` cvs-commit at gcc dot gnu.org 2023-02-10 17:47 ` cvs-commit 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-105593-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).