From: Yao Qi <yao@codesourcery.com>
To: Jiong Wang <jiwang@tilera.com>
Cc: <gdb-patches@sourceware.org>, Walter Lee <walt@tilera.com>,
<palves@redhat.com>
Subject: Re: [PATCH/tilegx] tilegx bug fixes & improvements
Date: Fri, 07 Dec 2012 02:40:00 -0000 [thread overview]
Message-ID: <50C15700.7020400@codesourcery.com> (raw)
In-Reply-To: <50C0B790.9070509@tilera.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030"; format=flowed, Size: 1731 bytes --]
On 12/06/2012 11:19 PM, Jiong Wang wrote:
>> The problems looks about plt. I find tilegx port doesn't have a plt
>> >stub unwinder. I am not sure creating a plt stub unwinder can fix
>> >this problem,
> I am not quite understand the usage of plt stub unwinder here. i386
> do not append plt stub unwinder also. from my understanding, those plt
> stub can be unwinded as normal frame, like a leaf function, or have I
> misunderstood something?
>
I am not familiar with i386 port. plt stub unwinder is helpful to
identify current pc is within the plt stub and dynamic resolver, IIRC.
It is useful when user type command 'n' to step over function 'printf',
for example, otherwise, gdb will stop inside printf instead of the next
line of printf, which is expected.
>> >but it should fix other fails in testsuite.
> the left failures are mostly about type print issues under gdb.cp
> and gdb.python
>
plt stub unwinder may not help in this case.
> attachment is the patch to fix above problems
>
Thanks for the fix. We don't post a delta-patch on top of the reviewed
patch. If you updated your patch to address review comments, please
post the new one instead of the delta part (and one mail for one patch).
> diff --git a/gdb/tilegx-tdep.c b/gdb/tilegx-tdep.c
> index f7e00d7..903bf20 100644
> --- a/gdb/tilegx-tdep.c
> +++ b/gdb/tilegx-tdep.c
> @@ -324,23 +324,27 @@ tilegx_push_dummy_call (struct gdbarch *gdbarch,
> }
>
> /* Align SP. */
> - stack_dest = (stack_dest + 7) & ~0x7;
> + stack_dest = align_down(stack_dest, 8);
^ A space is missing.
or you can use 'tilegx_frame_align', which was used before you change.
--
Yao (ÆëÒ¢)
next prev parent reply other threads:[~2012-12-07 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 7:00 Jiong Wang
2012-12-06 9:39 ` Yao Qi
2012-12-06 15:20 ` Jiong Wang
2012-12-07 2:40 ` Yao Qi [this message]
2012-12-07 2:42 ` Joel Brobecker
2012-12-07 3:12 ` Jiong Wang
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=50C15700.7020400@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jiwang@tilera.com \
--cc=palves@redhat.com \
--cc=walt@tilera.com \
/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