From: Richard Guenther <richard.guenther@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Adam Nemet <anemet@caviumnetworks.com>, gcc@gcc.gnu.org
Subject: Re: STRIP_NOPS and lower-precision/bit-field types
Date: Thu, 04 Jun 2009 21:00:00 -0000 [thread overview]
Message-ID: <84fc9c000906041400p2c936482ha9bb9d7b3a8c6dd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906042045090.8600@digraph.polyomino.org.uk>
On Thu, Jun 4, 2009 at 10:49 PM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Thu, 4 Jun 2009, Adam Nemet wrote:
>
>> 1. Change STRIP_NOPS not to remove the cast if it's changing the precision
>> (not just when it changes machine modes). And then audit code quality where
>> we need to and are allowed to look through these casts.
>
> As I said in <http://gcc.gnu.org/ml/gcc-bugs/2007-03/msg02228.html> and
> <http://gcc.gnu.org/ml/gcc/2008-01/msg00215.html>, I think such references
> to the mode are as a proxy for precision and machine modes are an
> inappropriate level of abstraction for the tree optimizers. So I favour
> checking for precision here - but I also favour having a good look at
> anything using STRIP_NOPS etc. and considering whether it should use some
> better defined function for removing redundant conversions instead.
FWIW I agree. STRIP_NOPS should not change the precision - we came
to this conclusion multiple times but never got around to do the change.
Richard.
> --
> Joseph S. Myers
> joseph@codesourcery.com
>
prev parent reply other threads:[~2009-06-04 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 20:15 Adam Nemet
2009-06-04 20:49 ` Joseph S. Myers
2009-06-04 21:00 ` Richard Guenther [this message]
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=84fc9c000906041400p2c936482ha9bb9d7b3a8c6dd@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=anemet@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).