From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-431731-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 29803 invoked by alias); 15 Jul 2016 07:32:29 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 29782 invoked by uid 89); 15 Jul 2016 07:32:28 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: mail-wm0-f52.google.com
Received: from mail-wm0-f52.google.com (HELO mail-wm0-f52.google.com) (74.125.82.52) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 15 Jul 2016 07:32:18 +0000
Received: by mail-wm0-f52.google.com with SMTP id i5so16920899wmg.0        for <gcc-patches@gcc.gnu.org>; Fri, 15 Jul 2016 00:32:18 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=VoDkY6rfj0bdarTMZRSy6JdAbP6KxRGUdQ4m5GCt3z8=;        b=B2x+ZmmBrl4je20xKG9sAucn7qkkrANmz6liuQYn5gWLfGbI9+GuVqvUggQLAjffBl         ZLGZCU2miXoFlMyr1FypTuCdDzOACffP/smi4PB4NWG5BGyby625s3HRPdq4R3lAs57e         FnV4gmNopguSJN/UKCaqP0i1mWJOaraVn0DZrYKLZAAGeIm1aA6uQ3p8mss4lO/u2ro0         GWhrf/8NEtg2+AtcdyCTPMZDrb5V3TcswLi9UPIelAnkzSLamToLWEtsagTg6wt7RLsL         V3J74FO6pEcIGLUYIOgMlP+xdFieaFjwsFIzpeXDROjGhFJqyo1uN/KiGJsaXW+GJXpW         ZqCA==
X-Gm-Message-State: ALyK8tKUdN2OF5rdIAzLaX9mRnT6WB+6dkDwRs4Gk4o5QX9IgWZHfmV6ta7mqWtKLbL7tHuBDWGFTYMEBkGG3Q==
X-Received: by 10.28.141.74 with SMTP id p71mr20152947wmd.37.1468567935608; Fri, 15 Jul 2016 00:32:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.207.135 with HTTP; Fri, 15 Jul 2016 00:32:15 -0700 (PDT)
In-Reply-To: <578869F9.5040606@linaro.org>
References: <57886949.8010300@linaro.org> <578869F9.5040606@linaro.org>
From: Richard Biener <richard.guenther@gmail.com>
Date: Fri, 15 Jul 2016 07:32:00 -0000
Message-ID: <CAFiYyc0P3dvO6gF+e6r4k5=YhUqcn_k9wZUEECqSLGdaxfeZvA@mail.gmail.com>
Subject: Re: [RFC][IPA-VRP] Check for POINTER_TYPE_P before accessing SSA_NAME_PTR_INFO in tree-inline
To: kugan <kugan.vivekanandarajah@linaro.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, Jan Hubicka <hubicka@ucw.cz>, 	Martin Jambor <mjambor@suse.cz>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2016-07/txt/msg00903.txt.bz2

On Fri, Jul 15, 2016 at 6:43 AM, kugan
<kugan.vivekanandarajah@linaro.org> wrote:
>
> Hi,
>
>
>
> This patch adds check for POINTER_TYPE_P before accessing SSA_NAME_PTR_INFO
> in remap_ssa_name in gcc/tree-inline.c. This is not related to IPA_VRP but
> was exposed by that.

Ok.  (before your IPA VRP nothing sets RANGE_INFO on SSA vars before
inlining is complete)

Thanks,
Richard.

>
>
> Thanks,
>
> Kugan
>
>
>
>
>
> gcc/ChangeLog:
>
>
>
> 2016-07-14  Kugan Vivekanandarajah  <kuganv@linaro.org>
>
>
>
>         * tree-inline.c (remap_ssa_name): Check for POINTER_TYPE_P before
>
>         accessing SSA_NAME_PTR_INFO.
>
>
>
>
>