public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "MichieldeB at aim dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/45831] 0 = 10 (with -O0, 0 = 0 with -O1, but 10 = 10 expected)
Date: Thu, 30 Sep 2010 23:02:00 -0000	[thread overview]
Message-ID: <20100930230200.VDltWbVWv_0dKd9IUx-LYbFXhJq9iEOaFQf1cTjWz0s@z> (raw)
In-Reply-To: <bug-45831-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45831

--- Comment #16 from Michiel <MichieldeB at aim dot com> 2010-09-30 19:38:55 UTC ---
(In reply to comment #15)
> (In reply to comment #14)
> >
> > Is that really too hard?
>
> You are ignoring everything everybody is saying. If you think it is trivial,
> just take one single little case of the ones that bother you and fix it:
> 
> http://gcc.gnu.org/contribute.html
> 
> GCC needs more developers anyway, so you are welcome on board.

I am not ignoring everyone, since I formulated things far more concrete than
before. And I failed to formulate similar things to warnings for assigning
negative expressions to unsigned integers.

Another thing that is worth noting, is that recognizing expression as mentioned
above is also valuable for optimization, namely if you convert the result later
to a smaller integral type, and the larger integral type is larger than the
machines integral type, then you better do the computations with the smaller
integral type instead.

I have to apologize. There are already too many technically interesting things,
or just interesting things that are also technically, that I want to do.
Furthermore, I think that it will take very much time before I can make my
first contribution to the compiler, but I should browse the source to get a
better opinion on that. Some library routines would be more attainable, I will
think about that.


      parent reply	other threads:[~2010-09-30 19:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 15:33 [Bug c/45831] New: " MichieldeB at aim dot com
2010-09-29 15:35 ` [Bug c/45831] " schwab@linux-m68k.org
2010-09-29 15:43 ` MichieldeB at aim dot com
2010-09-29 15:44 ` MichieldeB at aim dot com
2010-09-29 15:47 ` MichieldeB at aim dot com
2010-09-29 16:28 ` pinskia at gcc dot gnu.org
2010-09-29 17:04 ` manu at gcc dot gnu.org
2010-09-29 17:04 ` MichieldeB at aim dot com
2010-09-29 17:09 ` manu at gcc dot gnu.org
2010-09-29 19:41 ` joseph at codesourcery dot com
2010-09-30 13:01 ` MichieldeB at aim dot com
2010-09-30 13:13 ` schwab@linux-m68k.org
2010-09-30 16:42 ` jakub at gcc dot gnu.org
2010-09-30 17:09 ` manu at gcc dot gnu.org
2010-09-30 21:10 ` MichieldeB at aim dot com
2010-09-30 21:19 ` manu at gcc dot gnu.org
2010-09-30 23:02 ` MichieldeB at aim dot com [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=20100930230200.VDltWbVWv_0dKd9IUx-LYbFXhJq9iEOaFQf1cTjWz0s@z \
    --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).