public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/104274] FAIL: gcc.dg/analyzer/pr97029.c (test for excess errors) Date: Thu, 10 Feb 2022 23:50:47 +0000 [thread overview] Message-ID: <bug-104274-4-qMmtSQURZ5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104274-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104274 --- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- In theory, 3978 gimplify_assign (local, parm, &stmts); ought to be generating a "pl.0 = pl;" assignment, but we're hitting this case in gimplify_modify_expr: VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV 5927 /* For empty types only gimplify the left hand side and right hand 5928 side as statements and throw away the assignment. Do this after 5929 gimplify_modify_expr_rhs so we handle TARGET_EXPRs of addressable 5930 types properly. */ 5931 if (is_empty_type (TREE_TYPE (*from_p)) 5932 && !want_value 5933 /* Don't do this for calls that return addressable types, expand_call 5934 relies on those having a lhs. */ 5935 && !(TREE_ADDRESSABLE (TREE_TYPE (*from_p)) 5936 && TREE_CODE (*from_p) == CALL_EXPR)) (gdb) 5937 { 5938 gimplify_stmt (from_p, pre_p); 5939 gimplify_stmt (to_p, pre_p); 5940 *expr_p = NULL_TREE; 5941 return GS_ALL_DONE; 5942 } ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
next prev parent reply other threads:[~2022-02-10 23:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-28 18:57 [Bug analyzer/104274] New: " danglin at gcc dot gnu.org 2022-02-10 23:02 ` [Bug analyzer/104274] " dmalcolm at gcc dot gnu.org 2022-02-10 23:38 ` dmalcolm at gcc dot gnu.org 2022-02-10 23:50 ` dmalcolm at gcc dot gnu.org [this message] 2022-02-10 23:59 ` dmalcolm at gcc dot gnu.org 2022-02-11 13:47 ` cvs-commit at gcc dot gnu.org 2022-02-11 13:53 ` dmalcolm 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-104274-4-qMmtSQURZ5@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).