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 tree-optimization/102608] [12 regression] Recent change to VN causes bogus Wuninitialized warnings & kernel build failures
Date: Wed, 06 Oct 2021 08:39:21 +0000 [thread overview]
Message-ID: <bug-102608-4-fLRTVOroDc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102608-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102608
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|11.0 |12.0
Last reconfirmed| |2021-10-06
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> old32_34 = .DEFERRED_INIT (4, 2, 0);
>
> ...
>
> - _24 = .DEFERRED_INIT (4, 2, 0);
> - __res ={v} _24;
> + __res ={v} old32_34;
>
>
> # 68 "../arch/mips/include/asm/cmpxchg.h"
> This is due to __typeof(*((volatile u32 *)ptr)) __ret
>
>
>
> The warning is kinda of correct but wrong as it uses the wrong decl :).
>
> Fre maybe should be disabled for DEFERRED_INIT ....
Hmm, I did consider that but then I thought it wouldn't matter (there were no
testsuite FAILs).
But sure, I can easily make .DEFERRED_INIT always produce a VARYING value.
next prev parent reply other threads:[~2021-10-06 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 14:51 [Bug tree-optimization/102608] New: " law at gcc dot gnu.org
2021-10-05 15:37 ` [Bug tree-optimization/102608] " pinskia at gcc dot gnu.org
2021-10-05 15:38 ` pinskia at gcc dot gnu.org
2021-10-06 8:39 ` rguenth at gcc dot gnu.org [this message]
2021-10-07 12:28 ` cvs-commit at gcc dot gnu.org
2021-10-07 12:29 ` 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-102608-4-fLRTVOroDc@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: 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).