Re: <cpu>-frame.c, frame/<cpu>.c, config/<cpu>/frame.c, ...

[Andrew Cagney <ac131313 at redhat dot com>]

> 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, ...)

> 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.

?

Andrew