From: Ben Elliston <bje@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <cgen@sources.redhat.com>
Subject: Re: simulation; vliw targets; writeback tracking bitstring overflow
Date: Sun, 28 Jan 2001 19:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.31.0101291324390.23345-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <20010125173953.B915@redhat.com>
Anyway, this needs to get fixed. A couple of alternatives are:
- widening the bitfield to "unsigned long long"
- adopting a separate per-field indicator variable
- (since I'm interested in sid -> C++) adopting a std::bitset<N> type
What are the runtime memory requirements for moving to unsigned long long?
Ben
next prev parent reply other threads:[~2001-01-28 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 14:40 Frank Ch. Eigler
2001-01-28 19:44 ` Ben Elliston [this message]
2001-01-28 20:04 ` Frank Ch. Eigler
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=Pine.LNX.4.31.0101291324390.23345-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).