From: Daniel Jacobowitz <drow@mvista.com>
To: Richard Henderson <rth@redhat.com>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] OSF/1 - "next" over prologueless function call
Date: Tue, 02 Dec 2003 13:55:00 -0000 [thread overview]
Message-ID: <20031202135516.GA18934@nevyn.them.org> (raw)
In-Reply-To: <20031202063532.GC31561@redhat.com>
On Mon, Dec 01, 2003 at 10:35:32PM -0800, Richard Henderson wrote:
> On Mon, Dec 01, 2003 at 08:26:46PM -0800, Joel Brobecker wrote:
> > + if (pc == func_start)
> > + return 1;
> > +
> > + if (pc == func_start + 8)
> > + {
> > + unsigned int inst;
> > +
> > + /* ldah $gp,n($t12) */
> > + inst = alpha_read_insn (func_start);
> > + if ((inst & 0xffff0000) != 0x27bb0000)
> > + return 0;
> > +
> > + /* lda $gp,n($gp) */
> > + inst = alpha_read_insn (func_start + 4);
> > + if ((inst & 0xffff0000) != 0x23bd0000)
> > + return 0;
>
> Is there any chance we could get hold of the symbol associated with
> this function start? On ELF detecting this condition can be
> streamlined to
>
> sym->st_other & STO_ALPHA_STD_GPLOAD == STO_ALPHA_STD_GPLOAD
>
> or from bfd, elf_link_hash_entry.other, though I don't remember off
> the top of my head how to get at the elf hash entry from asymbol.
I don't think you can. They're not added to a link hash table unless
you're actually linking.
It looks like there's no way to go from the asymbol to the ELF symbol
either, and st_other isn't stashed anywhere.
> And yes indeed, the gnu tools do this same optimization. Both at
> compile time and link time.
>
>
> r~
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-02 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 4:26 Joel Brobecker
2003-12-02 4:30 ` Daniel Jacobowitz
2003-12-02 6:06 ` Joel Brobecker
2003-12-02 6:35 ` Richard Henderson
2003-12-02 7:21 ` Joel Brobecker
2003-12-02 15:14 ` Daniel Jacobowitz
2003-12-03 1:54 ` Joel Brobecker
2003-12-02 13:55 ` Daniel Jacobowitz [this message]
2003-12-03 4:19 ` Andrew Cagney
2003-12-04 0:55 ` Joel Brobecker
2003-12-04 1:49 ` Andrew Cagney
2003-12-04 23:24 ` Joel Brobecker
2003-12-04 23:28 ` Daniel Jacobowitz
2003-12-05 20:19 ` Andrew Cagney
2003-12-08 23:25 ` Joel Brobecker
2003-12-09 23:10 ` Andrew Cagney
2003-12-02 5:49 Michael Elizabeth Chastain
2003-12-02 7:53 Michael Elizabeth Chastain
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=20031202135516.GA18934@nevyn.them.org \
--to=drow@mvista.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@redhat.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