From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPICA 20031002 released
Date: Tue, 7 Oct 2003 12:56:45 +0200 [thread overview]
Message-ID: <20031007105645.GB1659@openzaurus.ucw.cz> (raw)
In-Reply-To: <1065475231.2511.33.camel-D2Zvc0uNKG8@public.gmane.org>
Hi!
> Code and Data Size: Current and previous core subsystem library sizes
> are shown below. These are the code and data sizes for the acpica.lib
They are not :-(.
> produced by the Microsoft Visual C++ 6.0 compiler, and these values do
> not include any ACPI driver or OSPM code. The debug version of the code
> includes the debug output trace mechanism and has a much larger code and
> data size. Note that these values will vary depending on the efficiency
> of the compiler and the compiler options used during generation.
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-07 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 21:20 ACPICA 20031002 released Len Brown
[not found] ` <1065475231.2511.33.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-07 10:56 ` Pavel Machek [this message]
2003-10-07 15:49 Brown, Len
2003-10-10 17:01 Brown, Len
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=20031007105645.GB1659@openzaurus.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.