From: Jim Blandy <jimb@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: PATCH: replace cpu_trace_stream subclass with rdbuf swap
Date: Thu, 22 Jan 2004 17:33:00 -0000 [thread overview]
Message-ID: <vt2smi7j3da.fsf@zenia.home> (raw)
In-Reply-To: <20040122124853.GA28974@redhat.com>
"Frank Ch. Eigler" <fche@redhat.com> writes:
> > It builds, but I haven't tested it. The original patch was developed
> > on an internal Red Hat branch and tested against an internal Red Hat
> > cpu.
>
> Does this version of the code run on that internal port?
Yes --- it works with no redirection, with redirection to a file, with
redirection to one file and then another file (the first file gets
just the "start of trace" line, but is then empty), and redirection to
a file and then back to cout.
> > The full SID takes an awful long time to build, and I'm not sure what
> > toolchain and BSP to match it against. Do folks here have any advice
> > on how to pare down the SID build and which architecture to target to
> > test this with as little fuss as possible?
>
> The usual tricks are to configure sid with a single simple --target (say
> m32r-elf), with --disable-shared to omit shared library building, and
> build with CXXFLAGS excluding -O2 for a quicker compilation run.
Thanks --- I'll give that a try.
next prev parent reply other threads:[~2004-01-22 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 6:32 Jim Blandy
2004-01-22 12:49 ` Frank Ch. Eigler
2004-01-22 17:33 ` Jim Blandy [this message]
2004-01-22 17:39 ` Frank Ch. Eigler
2004-01-22 20:43 ` Ben Elliston
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=vt2smi7j3da.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=fche@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).