From joe.casey@usa.net Tue Aug 29 19:57:38 2000 Received: from aw161.netaddress.usa.net (aw161.netaddress.usa.net [204.68.24.61]) by spog.gaertner.de (8.8.8/8.8.8/Nase) with SMTP id TAA25573 for <bugs@gaertner.de>; Tue, 29 Aug 2000 19:57:37 +0200 Received: (qmail 1679 invoked by uid 60001); 29 Aug 2000 17:57:35 -0000 Received: from 204.68.24.61 by aw161 for [24.4.254.1] via web-mailer(34FM.0700.4.03) on Tue Aug 29 17:57:35 GMT 2000 Message-Id: <20000829175735.1678.qmail@aw161.netaddress.usa.net> Date: 29 Aug 00 11:57:35 MDT From: joe.casey@usa.net To: bugs@gaertner.de Subject: Suitability of J-Unix for use with 32-bit embedded Linux systems >Number: 37 >Category: j-unix >Synopsis: Suitability of J for use with 32-bit embedded Linux systems >Confidential: no >Severity: serious >Priority: medium >Responsible: neitzel >State: closed >Class: support >Submitter-Id: net >Arrival-Date: Sat Sep 16 19:48:31 MET DST 2000 >Last-Modified: Sat Sep 16 20:10:54 MET DST 2000 >Originator: Joe Casey >Organization: UCF Inc. >Release: j 4.02a >Environment: embedded systems >Description: I have questions regarding the applicability of J for certain intended applications using 32-bit microprocessors/microcontrollers. Further, I understand that the use of J may be restricted by the processor selection (e.g. J/WinCE demands a Hitachi SH3 or SH4 or else a MIPS processor). Would you be so kind as to shed some light on the suitability of use of the Linux version of J/Unix in the following instances: Embedded Linux systems without a hardware floating point processor Embedded Linux systems without memory management Embedded Linux systems without a file system Embedded Linux systems with certain specified processors (e.g. is an Intel microprocessor ever required)? Are there any other CPU restrictions? >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: neitzel State-Changed-When: Sat Sep 16 19:49:17 MET DST 2000 State-Changed-Why: Hello Joe, first: sorry for answering that late, your PR got stuck in the system and was noticed only because we rebooted it after a few months of smooth running.... The J engine depends on the following things: - a good standard math library - a good deal of the standard C library (but not too much) - standard memory handling (ie., standard malloc/free and no particular constraints w.r.t. stack frames). Architecturally, J 4.0[1234] used non-portable code which prevented its use on many non-Intel CPUs, notably RISC-style archictectures. This is currently addressed with the work on 4.05. Beyond that, "could I run J on special embedded system X?" will always have to be answered for that particular system X. It would also be required to have system X at hand, including a suitable C development environment. Martin . >Unformatted: