From: Ben Elliston <bje@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: modeling latency (fwd)
Date: Sun, 24 Jun 2001 17:06:00 -0000 [thread overview]
Message-ID: <15158.32871.322836.589521@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <20010621072133.A4390@redhat.com>
>>>>> "Frank" == Frank Ch Eigler <fche@redhat.com> writes:
Frank> BTW, regarding the proposed bus::status patch, it would be nice if you
Frank> could find some way of ensuring/requesting that the compiler packs the
Frank> struct into 4 bytes. Maybe the g++ "enum foo : 16" extension, maybe
Frank> something else.
I agree that packing the bus::status struct should be considered
important for performance, given that it is likely passed by value.
As you suggest, there is a g++ extension to help with this: packed
enums, but was never implemented. I am testing a patch to correct
this and will hopefully submit it to gcc-patches@ this week. It could
be quite some time before we can depend on its existence.
Ben
next prev parent reply other threads:[~2001-06-24 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 20:28 Ben Elliston
2001-06-20 23:23 ` Ben Elliston
2001-06-21 4:21 ` Frank Ch. Eigler
2001-06-24 17:06 ` Ben Elliston [this message]
2001-06-24 17:46 ` Frank Ch. Eigler
2001-06-24 18:52 ` 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=15158.32871.322836.589521@scooby.brisbane.redhat.com \
--to=bje@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).