From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dave Brolley <brolley@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: Fwd: Regarding the sid simulator [patch][commit]
Date: Wed, 29 Nov 2006 21:33:00 -0000 [thread overview]
Message-ID: <20061129213327.GJ8910@redhat.com> (raw)
In-Reply-To: <456DFBD1.7000406@redhat.com>
Hi -
> >Would it be possible to simply always compile in the shCfg.cxx file?
> >Protect it with an embedded #if SIDTARGET_SH | SIDTARGET_SH64
> >if you really must.
>
> Well yes, of course it would. It just seemed wasteful. Similar to how we
> don't compile/link in the bits which support unspecified targets in
> sid/component/cgen-cpu.
The costs (compile time / object size) are of a different magnitude.
We don't rip out unconfigured platforms out of configrun-sid.pl either
- they just won't work. Plus, if you add the #if/#endif thing I
mentioned, the costs of including a dummy shCfg.cxx are approximately
zero.
- FChE
next prev parent reply other threads:[~2006-11-29 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c1cd9c970611262354h2b5e928cib4ac5c7ee4390269@mail.gmail.com>
2006-11-27 13:03 ` Regarding the sid simulator Frank Ch. Eigler
[not found] ` <c1cd9c970611271523hd2e9721n6da6c054754e0976@mail.gmail.com>
[not found] ` <c1cd9c970611271531x37001d3k59da231d5c6a7506@mail.gmail.com>
2006-11-27 23:57 ` Fwd: " Frank Ch. Eigler
2006-11-28 7:48 ` Avinash Malik
2006-11-28 23:54 ` Frank Ch. Eigler
2006-11-29 21:20 ` Fwd: Regarding the sid simulator [patch][commit] Dave Brolley
2006-11-29 21:25 ` Frank Ch. Eigler
2006-11-29 21:30 ` Dave Brolley
2006-11-29 21:33 ` Frank Ch. Eigler [this message]
2006-11-30 18:52 ` Dave Brolley
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=20061129213327.GJ8910@redhat.com \
--to=fche@redhat.com \
--cc=brolley@redhat.com \
--cc=sid@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).