public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "divyajyotidas15 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/61240] [4.9/5/6 Regression] Incorrect warning "integer overflow in expression" on pointer-pointer subtraction
Date: Tue, 30 Jun 2015 22:49:00 -0000	[thread overview]
Message-ID: <bug-61240-4-OjQAPGEG3k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61240-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61240

Divya Jyoti Das <divyajyotidas15 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |divyajyotidas15 at gmail dot com

--- Comment #12 from Divya Jyoti Das <divyajyotidas15 at gmail dot com> ---
(In reply to Marek Polacek from comment #7)
> But C++ has its own pointer_diff version that doesn't do such optimization. 
> With my change the C FE would generate the same expr as the C++ FE.  And FEs
> shouldn't perform such optimizations anyway.


      parent reply	other threads:[~2015-06-30 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 23:10 [Bug c/61240] New: " Keith.S.Thompson at gmail dot com
2014-05-20  8:38 ` [Bug c/61240] [4.8/4.9/4.10 Regression] " rguenth at gcc dot gnu.org
2014-05-22  9:07 ` rguenth at gcc dot gnu.org
2014-07-01 20:09 ` jakub at gcc dot gnu.org
2014-08-04  7:21 ` mpolacek at gcc dot gnu.org
2014-08-04  7:30 ` jakub at gcc dot gnu.org
2014-08-04  7:39 ` mpolacek at gcc dot gnu.org
2014-12-01 12:26 ` [Bug c/61240] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-12-01 12:35 ` mpolacek at gcc dot gnu.org
2014-12-19 13:28 ` jakub at gcc dot gnu.org
2015-02-13  8:45 ` mpolacek at gcc dot gnu.org
2015-04-27 17:54 ` [Bug c/61240] [4.8/4.9/5/6 " ktietz at gcc dot gnu.org
2015-06-30 22:49 ` divyajyotidas15 at gmail 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=bug-61240-4-OjQAPGEG3k@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).