public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/67442] [5/6 Regression] GCC 5.2.0 on x86_64 creates invalid address on specific array index calculation through pointer
Date: Thu, 03 Sep 2015 08:27:00 -0000	[thread overview]
Message-ID: <bug-67442-4-MnTD0AEIQ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67442-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Seems this started with r210113 - wide_int merge.


  parent reply	other threads:[~2015-09-03  8:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  7:00 [Bug c/67442] New: " jussi.judin at ericsson dot com
2015-09-03  8:24 ` [Bug middle-end/67442] [5/6 Regression] " rguenth at gcc dot gnu.org
2015-09-03  8:27 ` mpolacek at gcc dot gnu.org [this message]
2015-09-03  8:44 ` rguenth at gcc dot gnu.org
2015-09-03  8:59 ` rguenth at gcc dot gnu.org
2015-09-03  9:02 ` rguenth at gcc dot gnu.org
2015-09-03  9:09 ` rguenth at gcc dot gnu.org
2015-09-03  9:11 ` rguenth at gcc dot gnu.org
2015-09-03  9:28 ` rguenth at gcc dot gnu.org
2015-09-03 10:04 ` rguenth at gcc dot gnu.org
2015-09-15 14:21 ` rguenth at gcc dot gnu.org
2015-09-16  7:25 ` rguenth at gcc dot gnu.org
2015-09-16  7:26 ` [Bug middle-end/67442] [5 " rguenth at gcc dot gnu.org
2015-09-28 10:46 ` rguenth at gcc dot gnu.org
2015-09-28 10:46 ` rguenth at gcc dot gnu.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=bug-67442-4-MnTD0AEIQ7@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).