public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/34389] -Wconversion produces wrong warning
Date: Fri, 15 Feb 2008 16:54:00 -0000 [thread overview]
Message-ID: <20080215165323.32298.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34389-5307@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from manu at gcc dot gnu dot org 2008-02-15 16:53 -------
So fold_unary is transforming (T)(x & c) into (T)x & (T)c. Which is exactly the
opposite transformation that build_binary_op just performed! Weird...
So I see two options:
* Either teach fold_unary to avoid this particular transformation in this
particular case.
* Hack conversion_warning to realize that (short)((int)x & c) is the same as
(short)(x & c) if x is signed int and c fits in a signed int. Which will be
undoing the transformation once more (fourth? fifth time?). And I am not even
sure how to do this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34389
next prev parent reply other threads:[~2008-02-15 16:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 4:15 [Bug c/34389] New: " Raimund dot Merkert at baesystems dot com
2007-12-13 21:38 ` [Bug c/34389] " manu at gcc dot gnu dot org
2007-12-13 21:53 ` pinskia at gcc dot gnu dot org
2007-12-17 11:57 ` manu at gcc dot gnu dot org
2008-01-07 12:11 ` manu at gcc dot gnu dot org
2008-01-23 18:35 ` manu at gcc dot gnu dot org
2008-02-15 16:34 ` manu at gcc dot gnu dot org
2008-02-15 16:54 ` manu at gcc dot gnu dot org [this message]
2008-02-15 18:05 ` manu at gcc dot gnu dot org
2008-04-23 7:21 ` rainy6144 at gmail dot com
2008-06-08 17:31 ` manu at gcc dot gnu dot org
2008-07-30 8:33 ` manu at gcc dot gnu dot org
2008-07-30 8:38 ` manu at gcc dot gnu dot org
2008-08-01 19:37 ` manu 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=20080215165323.32298.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).