From: Jie Zhang <jie@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Guenther <rguenther@suse.de>,
Alexandre Oliva <aoliva@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Do framep replacement even on RHS outside of MEM contexts (PR debug/44694)
Date: Thu, 01 Jul 2010 08:34:00 -0000 [thread overview]
Message-ID: <4C2C52D4.1090107@codesourcery.com> (raw)
In-Reply-To: <20100701082205.GT25077@tyan-ft48-01.lab.bos.redhat.com>
On 07/01/2010 04:22 PM, Jakub Jelinek wrote:
> On Thu, Jul 01, 2010 at 04:13:03PM +0800, Jie Zhang wrote:
>> This patch caused ICE for arm-none-eabi target:
>>
>> internal compiler error: in arm_dbx_register_number, at
>> config/arm/arm.c:21155
>>
>> when compiling thumb multilib libstdc++.
>
> Richard Earnshaw has already reported this in the PR, and here is my fix for
> that. I don't have any arm boxes, so will just test it on x86_64-linux and
> i686-linux (the PR44694 patch has been tested also on ppc/ppc64/s390/s390x
> btw), could you please test it on arm? Thanks.
>
> 2010-07-01 Jakub Jelinek<jakub@redhat.com>
>
> PR debug/44694
> * dwarf2out.c (reg_loc_descriptor): For eliminated arg_pointer_rtx
> or frame_pointer_rtx use DW_OP_fbreg offset DW_OP_stack_value.
>
Yes. This fixes the ICE I saw. Thanks!
--
Jie Zhang
CodeSourcery
next prev parent reply other threads:[~2010-07-01 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 15:29 Jakub Jelinek
2010-06-29 15:46 ` Richard Guenther
2010-06-29 16:03 ` Jakub Jelinek
2010-07-01 8:13 ` Jie Zhang
2010-07-01 8:21 ` Jakub Jelinek
2010-07-01 8:34 ` Jie Zhang [this message]
2010-07-01 11:06 ` [PATCH] Do framep replacement even on RHS outside of MEM contexts (PR debug/44694 followup) Jakub Jelinek
2010-07-01 11:07 ` Richard Guenther
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=4C2C52D4.1090107@codesourcery.com \
--to=jie@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).