Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Richard Henderson <rth@redhat.com>,
	David B Anderson <davea@quasar.engr.sgi.com>,
	gdb@sourceware.cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Why does mips define elf_backend_sign_extend_vma to true?
Date: Wed, 08 Aug 2001 09:53:00 -0000	[thread overview]
Message-ID: <20010808095401.B23955@nevyn.them.org> (raw)
In-Reply-To: <20010808090249.A28467@lucon.org>

On Wed, Aug 08, 2001 at 09:02:49AM -0700, H . J . Lu wrote:
> 
> I am willing to buy it. The immediate problem is in
> 
> struct obj_section *
> find_pc_sect_section (CORE_ADDR pc, struct sec *section)
> {
>   struct obj_section *s;
>   struct objfile *objfile;
> 
>   ALL_OBJSECTIONS (objfile, s)
>     if ((section == 0 || section == s->the_bfd_section) &&
>         s->addr <= pc && pc < s->endaddr)
>       return (s);
> 
>   return (NULL);
> }
> 
> s->addr and s->endaddr came from BFD with sign extension. But `pc' is
> not, which has the bit 31 set. All of them have the type of CORE_ADDR.
> Any suggestions? I am not sure if it is the only problem in gdb.

PC should be already be sign extended at this point... in my tests, it
is.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-08-08  9:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 20:27 David B Anderson
2001-08-07 22:04 ` H . J . Lu
2001-08-07 22:46   ` Richard Henderson
2001-08-07 23:21     ` H . J . Lu
2001-08-08  0:50       ` Richard Henderson
2001-08-08  1:09       ` Maciej W. Rozycki
2001-08-08  7:29         ` H . J . Lu
2001-08-08  7:50           ` Andrew Cagney
2001-08-08  8:03             ` H . J . Lu
2001-08-08  8:18               ` Andrew Cagney
2001-08-08  9:02                 ` H . J . Lu
2001-08-08  9:53                   ` Daniel Jacobowitz [this message]
2001-08-08 10:02                     ` H . J . Lu
2001-08-08 11:02                       ` Daniel Jacobowitz
2001-08-08 11:08                         ` H . J . Lu
2001-08-09 12:23                   ` Andrew Cagney
2001-08-08  9:48               ` Daniel Jacobowitz
2001-08-08  9:52                 ` H . J . Lu
2001-08-10  0:47               ` Maciej W. Rozycki
     [not found] <20010807182459.A15252@lucon.org>
     [not found] ` <20010807183933.A15425@lucon.org>
     [not found]   ` <3B709900.3000502@cygnus.com>
     [not found]     ` <20010807184504.A15571@lucon.org>
2001-08-07 18:52       ` H . J . Lu
2001-08-07 18:58         ` Daniel Jacobowitz

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=20010808095401.B23955@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=davea@quasar.engr.sgi.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=macro@ds2.pg.gda.pl \
    --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