public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: pinskia@gmail.com
To: "jiwang at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: [Bug rtl-optimization/65912] New: x_rtl.x_frame_offset not updated after frame related insn deleted
Date: Tue, 28 Apr 2015 16:25:00 -0000	[thread overview]
Message-ID: <BCEDAD12-4EF4-4919-A2A6-84745BB4A8FF@gmail.com> (raw)
In-Reply-To: <bug-65912-4@http.gcc.gnu.org/bugzilla/>



> On Apr 27, 2015, at 9:10 PM, jiwang at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote:
> 
> Has anyone run into this issue on other architecture like MIPS, PPC?

Yes on both. 
>From gcc-bugs-return-484877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Apr 28 16:26:30 2015
Return-Path: <gcc-bugs-return-484877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21558 invoked by alias); 28 Apr 2015 16:26:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21506 invoked by uid 55); 28 Apr 2015 16:26:26 -0000
From: "pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/65912] x_rtl.x_frame_offset not updated after frame related insn deleted
Date: Tue, 28 Apr 2015 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65912-4-L3SS9OPGkt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65912-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65912-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg02429.txt.bz2
Content-length: 308

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide912

--- Comment #1 from pinskia at gmail dot com <pinskia at gmail dot com> ---
> On Apr 27, 2015, at 9:10 PM, jiwang at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote:
>
> Has anyone run into this issue on other architecture like MIPS, PPC?

Yes on both.


  reply	other threads:[~2015-04-28 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  9:40 jiwang at gcc dot gnu.org
2015-04-28 16:25 ` pinskia [this message]
2015-06-25 21:23 ` [Bug rtl-optimization/65912] " ramana at gcc dot gnu.org
2015-06-25 21:23 ` ramana at gcc dot gnu.org
2021-12-19  0:26 ` [Bug middle-end/65912] " pinskia 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=BCEDAD12-4EF4-4919-A2A6-84745BB4A8FF@gmail.com \
    --to=pinskia@gmail.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).