World: r3wp
[Red] Red language group
older newer | first last |
Dockimbel 23-Nov-2011 [3897x2] | I'd like to make the JVM port before the rewrite of Red/System in Red, as doing so will certainly require some deep adjustments to Red/System compiler and linker, so better have it experienced before the rewrite. |
experienced: experimented | |
Kaj 26-Nov-2011 [3899x2] | I've tried including two bindings in one program that both include the C library binding, and I can't get it to do a single pass over the nested include, either with relative or absoltue paths to the C library binding |
The first thing it bombs out on is a #L marker that it seems to insert into the source to mark line numbers (even though I didn't do a debug build) | |
Dockimbel 27-Nov-2011 [3901x2] | I will a look at it today. |
Kaj: I have just pushed a fix for the problem you've reported. | |
Kaj 27-Nov-2011 [3903] | Great, thanks! |
Kaj 29-Nov-2011 [3904x4] | I can confirm that including multiple times works now on Linux |
Particularly, Mike's case of using both GTK and 0MQ works now | |
The WebKit binding is now here: | |
http://red.esperconsultancy.nl/Red-GTK-WebKit | |
Dockimbel 29-Nov-2011 [3908] | Great news! |
Kaj 29-Nov-2011 [3909] | Implemented a separate SCROLL widget in the GTK binding, that can be used as a container for other suitable widgets to make them scrollable |
Andreas 3-Dec-2011 [3910] | Red/System can now compile hello.reds (including the Red/System runtime) for ARM, and the resulting binary works fine. |
Kaj 3-Dec-2011 [3911] | That's ARMv5, isn't it, not ARMv7? On what targets does it and does it not run? |
Dockimbel 3-Dec-2011 [3912] | It should work fine on all ARM9+ CPUs, which is pretty much any ARM platform used these days. |
Andreas 3-Dec-2011 [3913] | ARMv5, yes. Should work on ARMv5+. |
Dockimbel 3-Dec-2011 [3914] | For ppl non-familiar with ARM naming conventions: http://en.wikipedia.org/wiki/ARM_architecture#ARM_cores |
Andreas 3-Dec-2011 [3915x3] | So on ARM9, ARM11, Cortex A. |
Cores, that is. | |
As Doc said, that covers most ARM systems in use today (except for the original StrongARM (historic; for those who happen to own an Apple Newton or Compaq iPAQ) and the current Cortex M microcontroller cores. | |
Gregg 3-Dec-2011 [3918] | Wow! Exciting news indeed. |
Dockimbel 3-Dec-2011 [3919] | Red/System hello.reds now runs also on Android. If you have a rooted device, you can get and run the binary from here: http://sidl.fr/tmp/hello |
Pekr 3-Dec-2011 [3920] | is there any other possibility than using rooted device? |
Dockimbel 3-Dec-2011 [3921x2] | If you use a native exe loader (like "Run Native Exe"), the ANSI escape codes won't be interpreted. |
Other possibility, yes, just install this app: http://gimite.net/en/index.php?Runnative executable in Android App | |
Pekr 3-Dec-2011 [3923] | as for Cortex MCUs - are those too low level MCUs, or is it just a matter of some work to do? |
Dockimbel 3-Dec-2011 [3924] | I haven't check their specs, but I guess that the current ARM backend should work for them too. |
Oldes 3-Dec-2011 [3925] | Isn't it possible to change debug level durring compilation? I would like to see the traces for my code, but not for the included runtimes. |
Kaj 3-Dec-2011 [3926x2] | It is |
[-v <integer!>] | |
Oldes 3-Dec-2011 [3928] | How it's supposed to be used during compilation? When I use: do/args %rsc.r "-v 3 %tests/hello.reds" i can see a lot of traces for files like %runtime/common.reds %runtime/lib-C.reds %runtime/win32.reds %runtime/utils.reds which I'm not interested in. |
Kaj 3-Dec-2011 [3929] | Not sure what the levels mean. I suspect the runtime can't be excluded |
Oldes 3-Dec-2011 [3930x2] | (I'm just trying to jump in and understand what the compiler does and in which steps) I know they must be there to create the app runable but I don't need such a app at this moment:) |
It's probably more easier for me to add some probes here and there:) | |
Dockimbel 3-Dec-2011 [3932x3] | You can use -v 6 and echo all output to a file and use a text editor to review the output for your code. |
Disabling debug output for runtime files sounds like a useful option though. | |
(and it should be the default option) | |
Andreas 3-Dec-2011 [3935] | Pekr: re "Cortex MCUs - are those too low level MCUs, or is it just a matter of some work to do?" Cortex-M raises two issues: first, these cores just support the Thumb instruction set (which Red/System does not support, at the moment). Second, most -M cores have no memory management unit (MMU). |
Dockimbel 3-Dec-2011 [3936] | Do they support the Thumb2 set (32-bit instructions)? |
Andreas 3-Dec-2011 [3937x2] | Depends on the core. |
Cortex-M3 supports _only_ Thumb2, for example. | |
Oldes 3-Dec-2011 [3939] | I can use -r for no-runtime :) |
Dockimbel 3-Dec-2011 [3940x2] | Yep, but you'll be quickly limited, unless you rewrite the runtime at least partially. ;-) |
I am making some changes to the compiler debug logs output to avoid being pollute by runtime lib logs. | |
Andreas 3-Dec-2011 [3942] | (Cortex-M0 supports Thumb plus a few Thumb-2 insns, IIRC.) |
Dockimbel 3-Dec-2011 [3943] | Oldes: I've pushed a change in master branch, you can now use -v 5 to get the output of your own code only (with max details). |
james_nak 3-Dec-2011 [3944] | I agree with Gregg, great job. I tempted to pull out my Sharp Zaurus SL-6000 (xscale-based) just to see if I could get Red to compile on that but I had better return to my "work". :-( |
Dockimbel 3-Dec-2011 [3945x2] | Oldes: about floating point support, I have made a short review of required changes in current compiler. I will publish it tomorrow, so we can decide on the priority with Kaj and others. |
James: thanks! | |
older newer | first last |