Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Thiemo Seufer <ths@mips.com>,
	gdb-patches@sourceware.org,
	     "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS: Handle manual calls of MIPS16 functions with a call stub
Date: Fri, 01 Feb 2008 17:07:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0802011659160.14889@perivale.mips.com> (raw)
In-Reply-To: <20080201165411.GA4063@caradoc.them.org>

On Fri, 1 Feb 2008, Daniel Jacobowitz wrote:

> Does the low bit end up set in the DWARF for init_small_structs?  From
> what you're saying, I think it does.  My experience with Thumb makes
> me think that's the actual GAS bug here.  Those are code addresses,
> not symbols, and I don't think they should encode MIPS16-ness -
> see the recent discussion of values in .debug_line, which we agreed
> should not have assorted flag bits set either.  The code starts at
> 0x900, not 0x901.

 It does.  Here is the final DWARF-2 record for init_small_structs():

 <1><ce2>: Abbrev Number: 16 (DW_TAG_subprogram)
  <ce3>     DW_AT_external    : 1
  <ce4>     DW_AT_name        : init_small_structs
  <cf7>     DW_AT_decl_file   : 1
  <cf8>     DW_AT_decl_line   : 613
  <cfa>     DW_AT_low_pc      : 0x8002093d
  <cfe>     DW_AT_high_pc     : 0x80020a90
  <d02>     DW_AT_frame_base  : 0x2db   (location list)
  <d06>     DW_AT_sibling     : <de6>

I cannot seem to locate the discussion you are referring to easily enough 
-- would you care to provide a link?

  Maciej


  reply	other threads:[~2008-02-01 17:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 18:14 Maciej W. Rozycki
2008-01-31 22:08 ` Daniel Jacobowitz
2008-02-01 10:27   ` Maciej W. Rozycki
2008-02-01 14:19     ` Daniel Jacobowitz
2008-02-01 15:34       ` Maciej W. Rozycki
2008-02-01 16:58         ` Daniel Jacobowitz
2008-02-01 17:07           ` Maciej W. Rozycki [this message]
2008-02-01 17:15             ` Daniel Jacobowitz
2008-02-04 16:14     ` Maciej W. Rozycki
2008-02-04 16:39       ` Daniel Jacobowitz
2008-02-08 14:23         ` Maciej W. Rozycki
2008-02-08 14:57           ` Daniel Jacobowitz
2008-02-08 18:06           ` Jim Blandy
2008-02-08 18:08           ` Jim Blandy
2008-02-13 18:28             ` Maciej W. Rozycki
2008-02-13 20:54               ` Jim Blandy
2008-02-15 11:36                 ` Maciej W. Rozycki
2008-02-18 13:32                   ` Nigel Stephens
2008-02-18 16:28                     ` Maciej W. Rozycki
2008-02-19 19:48                       ` Michael Snyder
2008-02-22 16:38                     ` Jim Blandy

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=Pine.LNX.4.61.0802011659160.14889@perivale.mips.com \
    --to=macro@mips.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=ths@mips.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