From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Doug Evans <dje@transmeta.com>, gdb@sources.redhat.com
Subject: Re: <cpu>-frame.c, frame/<cpu>.c, config/<cpu>/frame.c, ...
Date: Sun, 04 May 2003 15:46:00 -0000 [thread overview]
Message-ID: <20030504154654.GC12099@nevyn.them.org> (raw)
In-Reply-To: <3EB492BC.3080502@redhat.com>
On Sun, May 04, 2003 at 12:10:36AM -0400, Andrew Cagney wrote:
> >Andrew Cagney writes:
> > > config/<cpu>/frame.[hc]:
> > > Keeps the cpu stuff in a single directory.
>
> Some things I forgot to note:
>
> This is actually the one I like least. config/<cpu>/*.{mt,mh,h} are all
> being deleted, so adding files to that directory would make for
> confusion. Unlike {unwind,frame}/, it isn't clear what the exact
> interface that the file should be exporting was. On the other hand, it
> keeps <cpu> files together.
>
> There is the question of where to put more generic unwinders (dwarf2cfi,
> libunwind, ...)
Hmm. For non-cpu-specific files, we have two choices that I can think
of off the top of my head:
- Toplevel directory
- Functional subdirectory, i.e. unwind/ or frame/. I rather like
that idea...
> >Seems like this is a winner though you'd still want to call it
> ><cpu>-frame.c to avoid collisions in multi-arch targeted gdb's.
>
> ?
For instance, gcc -c normally drops object files in the current
directory. Makes debugging simpler too. Having multiple files named
frame.c in your debug info is a little confusing.
Again, something GDB could handle better, if we could figure out the
interface...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-04 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 3:12 Andrew Cagney
2003-05-04 3:33 ` Doug Evans
2003-05-04 4:10 ` Andrew Cagney
2003-05-04 7:31 ` Doug Evans
2003-05-04 15:46 ` Daniel Jacobowitz [this message]
2003-05-04 16:42 ` Andrew Cagney
2003-05-04 18:25 ` Daniel Jacobowitz
2003-05-07 18:49 ` Andrew Cagney
2003-05-04 15:44 ` Daniel Jacobowitz
2003-05-04 16:41 ` David Carlton
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=20030504154654.GC12099@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=dje@transmeta.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).