Why 64 bit only?

3 views
Skip to first unread message

Digited

unread,
Nov 20, 2008, 2:04:32 AM11/20/08
to XOmB
Why do you make the kernel 64-bit only?
How do you make it with 32-bit dmd?

Adam Hobaugh

unread,
Nov 20, 2008, 9:02:26 AM11/20/08
to xo...@googlegroups.com, dig...@yandex.ru
For the question about 64-bit only I refer to
http://code.google.com/p/xomb/wiki/DesignTradeoffs

"multicore x64, no legacy

This hardware is already over 50% of the market, and as old designs
are milked for extra life this paradigm will trickle down, even to the
high-end embedded market."

To make the kernel we use a gdc cross-compiler on 32 bit machines. It
won't work with 32-bit dmd unless it is set up as a cross compiler.

//adam

Brian Madden

unread,
Nov 20, 2008, 12:09:03 PM11/20/08
to xo...@googlegroups.com, dig...@yandex.ru

привет,

I think Adam answered the questions rather well, however I have some questions of my own.  How did you find us, and what is your interest in XOmB?

-Brian
--
Brian Madden
www.pittgeeks.org

Digited

unread,
Nov 20, 2008, 1:05:05 PM11/20/08
to XOmB
On 20 нояб, 21:09, "Brian Madden" <untwis...@gmail.com> wrote:
> привет,
> I think Adam answered the questions rather well, however I have some
> questions of my own.  How did you find us, and what is your interest in
> XOmB?

I've found you long ago with google projects search with keywords like
"D", "DigitalMars" and "tango", your main page has links to this
groups. I've done search because google hosts my projects too
(moonglide and dee0xd), so I was curious about what else, written in
d, is hosted there.

XoMB is a VERY interesting and a very promising project, I gave links
to it to many people to show that even a kernel can be written in D,
and that XoMB (besides LDC) can be our Bright future.
I don't have enough skills and free time to participate, but I can
test it (have a 64 bit notebook with vista & opensuse), maybe even
find bugs in the code or help a bit with it.

Wilkie

unread,
Nov 20, 2008, 2:18:07 PM11/20/08
to XOmB
Hello,

It is always exciting to find somebody with an interest in our
project. We appreciate your support and spreading the word about
XOmB. We very much hope that it will be useful and a success overall.

The use of D is an interesting one for many reasons. D's goal is
primarily to provide a general purpose language. In many ways this is
counter to the specific nature and goal of XOmB. C, on the other
hand, is a systems language primarily. However, C was written for
UNIX, and we consider such things a form of 'legacy' and these
entities must be abolished completely in order to facilitate a better
prospect for newer technologies. The D language inherits, pretty much
directly, the systems capabilities from C, however (inline assembly,
compatibility with the C ABI). Overall, it suits our interests very
well by providing at least a good basis for not being legacy and being
extremely useful, especially in the future when user-space programs
are executed, while allowing for all of our sweet low-level magical
stuff. It offers readability over C (mostly due to the lack of the
macro preprocessor) and if offers writeability over C (through D's
sophisticated functional template engine; metaprogramming (without C+
+) is extremely useful!). Of course, the prospect of a new language
(much like C is to UNIX) for modern systems work (multiprocessor
issues mostly) is not out of the question. We have compiler writers
considering the prospects of such a language currently.

Also, our googlecode pages are embarrassingly out of date. We moved
our trunk to github to allow for the use of git and its more powerful
branching features. Also the googlecode wiki is horribly lacking for
our needs (to have sophisticated and detailed documentation on XOmB
and the actual hardware architecture), so we got our own mediawiki set
up on our website. So, to update your linking:

Our master branch in github for XOmB:
http://github.com/untwisted/xomb/tree/master

Our wiki:
http://wiki.xomb.org/

In terms of testing, XOmB is very picky. It should, in theory, heh,
work well on any modern multiprocessor x86 environment. The
requirements right now are basically that. Dual-core x86 or better.
Extremely soon, you will need HPET support, which should be available
on all modern mid-range dual-core chips.

This may help if you would like to try out the current stable build.
Embarrassingly, it has not updated for git, but it will be within the
next 7 days. Basically you can get information on git and pulling our
repository in general web searches and off of github's site. Also
information about building a cross compiler. We can also help within
this discussion group if you have a specific problem in this process.
(it is tricky!)
http://wiki.xomb.org/index.php?title=Getting_Started

Thank you for your interest,
Dave Wilkinson II

Wilkie

unread,
Nov 20, 2008, 2:21:03 PM11/20/08
to XOmB
Hello,

Apparently we have bad habits of linking to old stuff.

http://wiki.xomb.org/index.php?title=Design_Tradeoffs

Better :)

--
Dave Wilkinson II
> (it is tricky!)http://wiki.xomb.org/index.php?title=Getting_Started

Digited

unread,
Nov 21, 2008, 2:31:40 AM11/21/08
to XOmB
Thanks a lot, Adam, Brian, Dave.
I'll be watching your progress, if I can help - I'll be glad to.
Reply all
Reply to author
Forward
0 new messages