From: Doug Evans <dje@transmeta.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: <cpu>-frame.c, frame/<cpu>.c, config/<cpu>/frame.c, ...
Date: Sun, 04 May 2003 07:31:00 -0000 [thread overview]
Message-ID: <16052.49599.471333.59775@casey.transmeta.com> (raw)
In-Reply-To: <3EB492BC.3080502@redhat.com>
Andrew Cagney writes:
> config/<cpu>/*.{mt,mh,h} are all
> being deleted, so adding files to that directory would make for
> confusion.
I dunno about confusion.
The consistency with gcc and gas is nice.
(while gas doesn't have config/<cpu>, neither did gcc until way back when,
not that I'm suggesting gas should have config/<cpu>, just that
both have config/<something> for target files).
If one is going to try to reduce the number of files in the top level dir,
to me having all the target specific files in config/<cpu>
seems reasonable (and more preferable than having them littered about
in the top level directory and various subdirs).
next prev parent reply other threads:[~2003-05-04 7:31 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 [this message]
2003-05-04 15:46 ` Daniel Jacobowitz
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=16052.49599.471333.59775@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=ac131313@redhat.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).