public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107565] -Wanalyzer-use-of-uninitialized-value false positive with rdrand Date: Tue, 08 Nov 2022 05:39:48 +0000 [thread overview] Message-ID: <bug-107565-4-sxHUNixNbP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107565-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107565 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Target| |x86_64 Last reconfirmed| |2022-11-08 Component|analyzer |target Assignee|dmalcolm at gcc dot gnu.org |unassigned at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. else if (!fndecl_has_gimple_body_p (callee_fndecl) && (!(callee_fndecl_flags & (ECF_CONST | ECF_PURE))) && !fndecl_built_in_p (callee_fndecl)) unknown_side_effects = true; The last part is part of the problem I think. At least here. Yes maybe we should have another builtin which returns a "_Complex unsigned long long" here which is folded into for __builtin_ia32_rdrand*_step to remove the need to the address too. I am going to declare this one as a target issue but there might be other builtins which are harder to do the "_Complex" trick.
next prev parent reply other threads:[~2022-11-08 5:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-08 1:15 [Bug analyzer/107565] New: " eggert at cs dot ucla.edu 2022-11-08 5:39 ` pinskia at gcc dot gnu.org [this message] 2022-11-08 14:06 ` [Bug target/107565] [12/13 Regression] " dmalcolm at gcc dot gnu.org 2023-01-13 10:19 ` rguenth at gcc dot gnu.org 2023-01-13 12:44 ` [Bug analyzer/107565] " rguenth at gcc dot gnu.org 2023-03-01 14:32 ` dmalcolm at gcc dot gnu.org 2023-03-01 22:26 ` cvs-commit at gcc dot gnu.org 2023-03-01 22:34 ` dmalcolm at gcc dot gnu.org 2023-03-03 23:01 ` [Bug analyzer/107565] [12 " cvs-commit at gcc dot gnu.org 2023-05-08 12:25 ` 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-107565-4-sxHUNixNbP@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).