From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
stcarrez@nerim.fr, brobecker@gnat.com, gdb@sources.redhat.com,
kettenis@chello.nl
Subject: Re: 8-byte register values on a 32-bit machine
Date: Wed, 12 Mar 2003 18:15:00 -0000 [thread overview]
Message-ID: <3E6F7926.2070603@redhat.com> (raw)
In-Reply-To: <20030312170052.GA31979@nevyn.them.org>
>> > I think it is very dangerous. It's assuming a specific algorithm
>> > in the compiler. That locks both GDB and GCC into something of a
>> > death spiral. I think its far better to try and get a proper
>> > location mechanism working.
>
>>
>> There are other ways forward on this - moving the algorithm to libiberty
>> (like the demangler).
>
>
> This is a target-specific allocation order, for communication between
> GCC and GDB, not a matter of published interfaces - I don't think it
> belongs in libiberty. It's subject to change, but I have a reasonable
> expectation that it won't change until after debugging info to express
> it is available.
>
> In any case I'm going back to working on locations as objects, which is
> the next step in fixing this properly.
Mark's point was that the algorithm, while machine specific, hasn't
changed in N (10?) years.
Even if in the future, the algorithm does change, GDB/GCC might as well
share the code for the original one so that GDB can work better with
older compilers.
Andrew
next prev parent reply other threads:[~2003-03-12 18:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 16:59 Michael Elizabeth Chastain
2003-03-12 15:35 ` Andrew Cagney
2003-03-12 15:51 ` Daniel Jacobowitz
2003-03-12 16:57 ` Andrew Cagney
2003-03-12 17:01 ` Daniel Jacobowitz
2003-03-12 18:15 ` Andrew Cagney [this message]
2003-03-12 18:29 ` Andrew Cagney
2003-03-12 18:35 ` Daniel Jacobowitz
2003-03-12 18:38 ` Andrew Cagney
2003-03-12 18:48 ` Paul Koning
2003-03-12 19:00 ` Daniel Jacobowitz
2003-03-12 21:04 ` Andrew Cagney
2003-03-12 20:06 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 16:27 Michael Elizabeth Chastain
2003-03-13 4:18 Michael Elizabeth Chastain
2003-03-13 17:05 ` Andrew Cagney
2003-03-12 19:09 Michael Elizabeth Chastain
2003-03-12 20:47 ` Andrew Cagney
2003-03-02 6:52 Michael Elizabeth Chastain
2003-03-02 9:35 ` Stephane Carrez
2003-03-03 4:50 ` Daniel Jacobowitz
2003-03-01 20:57 Michael Elizabeth Chastain
2003-03-01 22:46 ` Mark Kettenis
2003-02-24 2:36 Michael Elizabeth Chastain
2003-03-01 13:35 ` Mark Kettenis
2003-03-01 20:33 ` Joel Brobecker
2003-03-01 22:38 ` Mark Kettenis
2003-03-01 23:41 ` Andrew Cagney
2003-03-02 0:28 ` Daniel Jacobowitz
2003-03-03 11:26 ` Richard Earnshaw
2003-03-03 11:52 ` Keith Walker
2003-03-01 23:39 ` Andrew Cagney
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=3E6F7926.2070603@redhat.com \
--to=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=mec@shout.net \
--cc=stcarrez@nerim.fr \
/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).