World: r3wp

i have a first crude hack of a ELF section header table working. 
it can currently describe itself :)

builds/hello:     file format elf32-i386

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .shstrtab ...

Here we go, hello.reds now results in a 1065 bytes binary (882 previously). 
For this bloat, you get the following information:

Section Headers:

  [Nr] Name              Type            Addr     Off    Size   ES 
  Flg Lk Inf Al

  [ 0]                   NULL            00000000 000000 000000 00 
       0   0  0

  [ 1] .text             PROGBITS        08048074 000074 000290 00 
   AX  0   0  4

  [ 2] .data             PROGBITS        08048304 000304 000085 00 
   WA  0   0  4

  [ 3] .shstrtab         STRTAB          00000000 000372 000017 00 
       0   0  1

Nice!

http://www.agner.org/optimize/promise convertor for obj files from 
PE, ELF to Mach-O and vice versa if it would help

Well, Red will probably not have to deal with object files directly, 
but anyway there are some good resources there. Too bad, the asm 
optimized subroutine library is not LGPL...

Ask, and I'm sure you will get a LGPL version.

You'd be surprised

Well, I'll try it when the need for such optimized code will come 
(not in the short-term). I'll probably need a subset only.

Why would you want an LGPL library for a BSD language?

For that matter, why would he make a GPL library for tutorial purposes? 
You can get in legal trouble for reading that code if you actually 
use what you learn to write code that isn't GPL licensed. This seems 
like poor planning, or just being mean. Is there at least a commercial 
license?

there is. and where do you get the idea from that this library is 
for tutorial purposes?

Brian: I don't intend to make Red deviate from the BSD road in anyway, 
I'm very much attached to keep it as open as possible. If some 3rd- 
party libraries with compatible license, can be used to add *optional* 
features, that shouldn't be a problem. The official Red distribution 
will always stay BSD.

Btw, I usually try not to read GPL code for features that I might 
have to implement in my pubic projects (not only Red). I've also 
stayed away from the host-kit source code for the same reason, knowing 
that I might have to work on similar features someday.

I didn't read the asm subroutine library source code, just the Manual, 
which is very informative.

Each routine has several implementations depending on the features 
available at runtime in the CPU (SSE, SSE2, SSE3,...). So, it's a 
bit too large for my needs (I would prefer selecting the best implementation 
at compile-time).

A few wildly different observations

I usually try to refrain from being a spelling nazi, but I did have 
a snicker at "pubic projects (not only Red)" :-)

The host kit is published but the licence is undetermined, so you 
could argue it's public domain

Hehe :-) Shouldn't chat on AltME while working.

At least not about those projects :-)

Unfortunately, the public domain argument won't get far:
**  Copyright 2010 REBOL Technologies
**  All rights reserved.

I just mean to say that Carl is creating a problem for himself by 
publishing with the monicker "open source" but undetermined licence

Absolutely.

or just take it as WTFPL

Even apart from the continuous creation of uncertainty, which everyone 
knows kills business

Anyway, it's hard to keep up with Red development. :-) I meant to 
say that in an unconnected context

I've updated the 0MQ binding again to the latest Red, and implemented 
the remaining 0MQ functions:

http://rebol.esperconsultancy.nl/extensions/0MQ

Among other things, you should now be able to set socket options, 
for example to create publish/subscribe topologies

Good job! It's nice seeing Red/System implementation near R2/R3 ones. 
I'll need to find some free time this weekend to start playing with 
0MQ and Red/System.

The code uses the new preprocessor. It's starting to look quite nice, 
and I've split off the examples into separate files, to the binding 
is now a proper separate library/#include file

Source code looks good. I need to add a "contributions" section in 
red-lang.org to reference your 0MQ page.

Thanks. It's very nice how you keep solving the crooked parts in 
it :-)

Your first implementation was very helpful for improving Red/System, 
especially the preprocessor part.

Communicating in code :-)

Almost all of the mezzanine changes to R2 starting with 2.7.6 are 
MIT licensed as part of R2/Forward. The R2 SDK source includes an 
attribution clause in the headers. Anything else in REBOL written 
by me can be contributed under the same license.

I am now able to compile RED program that throws "Illegal instruction" 
under OSX which is good thing as it means that the compiler now produces 
at least valid Mach-O header :)

You're implementing Mach-O?

I'm just trying to ;)

Cool!

Rebolek: great news! :-)

I'm glad someone picked up the task of implementing Mach-O output 
format.

Rebolek: maybe OS X requires position-independent code for executables? 
Checking it right now...

I should have basics required for functioning executable soon. If 
it still throws "illegal instruction" then, well...

Doc no it doesn't, I just still haven't got all the sections done.

but I'm close.

Good, it will make the porting easier.

A link for Andreas: http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/MachOTopics/1-Articles/dynamic_code.html


I was thinking about using some similar trick for ELF to allow efficient 
PIC support (avoiding the indirection table). It works by having 
a fixed offset between CODE and DATA segments in memory, so DATA's 
start address can be calculated at runtime, and all globals can be 
accessed using a simple offset.


It should be enough to reserve enough space for CODE segment (let's 
say 10MB) and make DATA entry point fixed? I wonder if the relative 
offsets between segments are preserved when the segments are moved 
by OSes (I hope so)?

10 MB should be enough for everyone ;-)