public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104321] New: Dead code since r12-4467-g64f9623765da33
Date: Tue, 01 Feb 2022 09:27:25 +0000 [thread overview]
Message-ID: <bug-104321-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104321
Bug ID: 104321
Summary: Dead code since r12-4467-g64f9623765da33
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: burnus at gcc dot gnu.org
Target Milestone: ---
The following assignment is dead:
gcc/fortran/trans-decl.cc:7108
/* if (cond) { block2 } */
tmp = fold_build2_loc (input_location, MODIFY_EXPR, void_type_node,
data, fold_convert (TREE_TYPE (data),
null_pointer_node));
tmp = build3_v (COND_EXPR, cond_var, gfc_finish_block (&block2),
build_empty_stmt (input_location));
It's likely a bug?
next reply other threads:[~2022-02-01 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 9:27 marxin at gcc dot gnu.org [this message]
2022-02-01 9:27 ` [Bug fortran/104321] " marxin at gcc dot gnu.org
2022-02-01 9:49 ` burnus at gcc dot gnu.org
2023-02-15 19:34 ` anlauf at gcc dot gnu.org
2023-03-25 19:04 ` cvs-commit at gcc dot gnu.org
2023-03-25 19:06 ` anlauf 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-104321-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: 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).