public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/96549] [10/11 Regression] Wrong evaluation of a comparison between long & short
Date: Tue, 11 Aug 2020 11:52:34 +0000 [thread overview]
Message-ID: <bug-96549-4-grSoB86Aru@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96549-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96549
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6b815e113c9aec397a86d7194f66455eb189cc7a
commit r11-2646-g6b815e113c9aec397a86d7194f66455eb189cc7a
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Aug 11 13:46:14 2020 +0200
tree: Fix up get_narrower [PR96549]
My changes to get_narrower to support COMPOUND_EXPRs apparently
used a wrong type for the COMPOUND_EXPRs, while e.g. the rhs
type was unsigned short, the COMPOUND_EXPR got int type as that was the
original type of op. The type of COMPOUND_EXPR should be always the type
of the rhs.
2020-08-11 Jakub Jelinek <jakub@redhat.com>
PR c/96549
* tree.c (get_narrower): Use TREE_TYPE (ret) instead of
TREE_TYPE (win) for COMPOUND_EXPRs.
* gcc.c-torture/execute/pr96549.c: New test.
next prev parent reply other threads:[~2020-08-11 11:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 8:03 [Bug c/96549] New: " zhige.yu18 at imperial dot ac.uk
2020-08-10 8:09 ` [Bug c/96549] [10/11 Regression] " marxin at gcc dot gnu.org
2020-08-10 8:20 ` [Bug middle-end/96549] " pinskia at gcc dot gnu.org
2020-08-10 8:20 ` [Bug middle-end/96549] [10/11 Regression] " pinskia at gcc dot gnu.org
2020-08-10 9:10 ` jakub at gcc dot gnu.org
2020-08-10 9:13 ` jakub at gcc dot gnu.org
2020-08-11 11:52 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-11 11:53 ` [Bug middle-end/96549] [10 " jakub at gcc dot gnu.org
2020-08-25 8:12 ` rguenth at gcc dot gnu.org
2020-08-25 17:45 ` cvs-commit at gcc dot gnu.org
2020-08-25 18:23 ` jakub 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-96549-4-grSoB86Aru@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).