public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/16693] [3.5 regression] Bitwise AND is lost when used within a cast to an enum of the same precision
Date: Wed, 25 Aug 2004 20:51:00 -0000 [thread overview]
Message-ID: <20040825205114.9708.qmail@sourceware.org> (raw)
In-Reply-To: <20040723171525.16693.paulg@chiark.greenend.org.uk>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-08-25 20:51 -------
Subject: Bug 16693
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: sayle@gcc.gnu.org 2004-08-25 20:51:02
Modified files:
gcc/cp : ChangeLog decl.c
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/g++.dg/opt: pr16372-1.C pr16693-1.C pr16693-2.C
Log message:
PR middle-end/16693
PR tree-optimization/16372
* decl.c (finish_enum): Make the precision of the enumerated type
the same width as the underlying integer type.
* g++.dg/opt/pr16372-1.C: New test case.
* g++.dg/opt/pr16693-1.C: New test case.
* g++.dg/opt/pr16693-2.C: New test case.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.4308&r2=1.4309
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/decl.c.diff?cvsroot=gcc&r1=1.1278&r2=1.1279
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.4192&r2=1.4193
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/opt/pr16372-1.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/opt/pr16693-1.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/opt/pr16693-2.C.diff?cvsroot=gcc&r1=1.1&r2=1.2
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16693
next prev parent reply other threads:[~2004-08-25 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 17:15 [Bug c++/16693] New: " paulg at chiark dot greenend dot org dot uk
2004-07-23 17:18 ` [Bug c++/16693] " paulg at chiark dot greenend dot org dot uk
2004-07-23 17:20 ` paulg at chiark dot greenend dot org dot uk
2004-07-23 17:22 ` [Bug c++/16693] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-07-23 19:04 ` [Bug c++/16693] [3.4/3.5 regression] " bangerth at dealii dot org
2004-07-23 19:06 ` bangerth at dealii dot org
2004-07-24 0:10 ` paulg at chiark dot greenend dot org dot uk
2004-07-26 13:03 ` paulg at chiark dot greenend dot org dot uk
2004-07-26 13:50 ` pinskia at gcc dot gnu dot org
2004-08-10 1:25 ` pinskia at gcc dot gnu dot org
2004-08-10 9:05 ` reichelt at gcc dot gnu dot org
2004-08-19 21:31 ` [Bug middle-end/16693] " mmitchel at gcc dot gnu dot org
2004-08-20 9:33 ` rearnsha at gcc dot gnu dot org
2004-08-22 23:30 ` mmitchel at gcc dot gnu dot org
2004-08-25 17:22 ` cvs-commit at gcc dot gnu dot org
2004-08-25 17:28 ` [Bug middle-end/16693] [3.5 " pinskia at gcc dot gnu dot org
2004-08-25 20:51 ` cvs-commit at gcc dot gnu dot org [this message]
2004-08-25 20:58 ` pinskia at gcc dot gnu dot org
2004-08-26 12:33 ` rearnsha at gcc dot gnu dot 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=20040825205114.9708.qmail@sourceware.org \
--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).