public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/67442] [5 Regression] GCC 5.2.0 on x86_64 creates invalid address on specific array index calculation through pointer
Date: Mon, 28 Sep 2015 10:46:00 -0000	[thread overview]
Message-ID: <bug-67442-4-OeaNaibb4O@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

--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Sep 28 10:45:55 2015
New Revision: 228199

URL: https://gcc.gnu.org/viewcvs?rev=228199&root=gcc&view=rev
Log:
2015-09-28  Richard Biener  <rguenther@suse.de>

        Backport from mainline
        2015-08-03  Richard Biener  <rguenther@suse.de>

        PR tree-optimization/66917
        * tree-vectorizer.h (struct dataref_aux): Add base_element_aligned
        field.
        (DR_VECT_AUX): New macro.
        (set_dr_misalignment): Adjust.
        (dr_misalignment): Likewise.
        * tree-vect-data-refs.c (vect_compute_data_ref_alignment):
        Compute whether the base is at least element aligned.
        * tree-vect-stmts.c (ensure_base_align): Adjust.
        (vectorizable_store): If the base is not element aligned
        preserve alignment of the original access if misalignment is unknown.
        (vectorizable_load): Likewise.

        2015-09-16  Richard Biener  <rguenther@suse.de>

        PR middle-end/67442
        * fold-const.c (extract_muldiv_1): Properly extend multiplication
        result before builting a tree via wide_int_to_tree.

        * gcc.dg/torture/pr67442.c: New testcase.

Added:
    branches/gcc-5-branch/gcc/testsuite/gcc.dg/torture/pr67442.c
Modified:
    branches/gcc-5-branch/gcc/ChangeLog
    branches/gcc-5-branch/gcc/fold-const.c
    branches/gcc-5-branch/gcc/testsuite/ChangeLog
    branches/gcc-5-branch/gcc/tree-vect-data-refs.c
    branches/gcc-5-branch/gcc/tree-vect-stmts.c
    branches/gcc-5-branch/gcc/tree-vectorizer.h


      parent reply	other threads:[~2015-09-28 10:46 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
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 [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-67442-4-OeaNaibb4O@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).