From: Sam James <sam@gentoo.org>
To: James Addison <jay@jp-hosting.net>
Cc: gcc@gcc.gnu.org
Subject: Re: avx512erintrin.h: uninitialized variable warning (optimized build)
Date: Thu, 12 Jan 2023 06:51:32 +0000 [thread overview]
Message-ID: <7D444AFD-A62E-450E-A80F-CA0C2EB9ECD4@gentoo.org> (raw)
In-Reply-To: <CALDQ5NxWOswUk+40zoyPckK4oR8PMpi+_bRcTSYQgnU+6WiaXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
> On 12 Jan 2023, at 00:26, James Addison via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hi,
>
> During GCC 12.2.0 compilation of a file that includes[1] immintrin.h
> with both code-optimization and uninitialized-variable-warnings
> enabled, a warning is emitted:
>
> /usr/lib/gcc/x86_64-linux-gnu/12/include/avx512erintrin.h:55:20:
> warning: ‘__W’ is used uninitialized [-Wuninitialized]
>
> The minimal repro compilation command appears to be:
>
> gcc -O -Wuninitialized -mavx512er -mavx512pf
> ./numpy/distutils/checks/cpu_avx512_knl.c
>
> My question is: does the warning indicate a possible bug that should
> be reported, or is there a reason that the relevant code[2] does not
> initialize the variable (for example, for performance reasons)?
See also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105593, might
be the same thing?
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2023-01-12 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 0:26 James Addison
2023-01-12 6:51 ` Sam James [this message]
2023-01-12 11:30 ` James Addison
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=7D444AFD-A62E-450E-A80F-CA0C2EB9ECD4@gentoo.org \
--to=sam@gentoo.org \
--cc=gcc@gcc.gnu.org \
--cc=jay@jp-hosting.net \
/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: link
Be 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).