Re: Ada

2024-06-24 Thread John Howard
>  gcc -v

You might try forcing arm mode without supporting thumb modes.

If I remember right, official Arm document obsoleted Thumb1, which would 
explain the “sorry” message.

gcc.pdf (.html) helps.

Also, there is a separate mailing list for the GCC linker problems. Experts 
might better assist there.

Also, GNAT repo maintainers or AdaCore could help.

GNAT Ada works on RPi. Configuration info from there might help you.

My Raspberry Pi Debian (Bullseye) on AMD64 has GCC 10.2.1 from 20210110.

RPi repos generally don’t update to recent
or development versions of GCC. Older RPi repos are removed to force users to 
upgrade.

Official Debian repos do not support the ArmV6 found in original Raspberry Pi 
or Zero (arm1176JZF-S). But Raspbian Debian does for bare metal gcc with 
noneabi packages (I use Synaptic packager to locate the installed files of 
interest).

For example, my obsoleted Raspbian repo version on RPi 3B+,
/usr/share/doc/gcc-6-doc/gcc.pdf
reveals 
-mcpu=arm1176jzf-s
is sufficient.

and /usr/share/doc/gcc-arm-none-eabi/readme.txt.gz

reveals
Cortex-A* (Hard FP) command line options:
[-mthumb] -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16

or for multilib:
armv7-ar
/thumb
/fpu

- - John

On Jun 24, 2024, at 9:08 AM, Sebastian Huber 
 wrote:

Hello John,

I have some issues on arm and Ada with current versions of GCC, see also:

https://gcc.gnu.org/pipermail/gcc/2024-June/244197.html
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Ada

2024-06-24 Thread John Howard
Thanks.

I will do that.

-- John
(Sorry for all my top-posting. I try to use an iPhone. ‘nuff said.)

On Jun 23, 2024, at 8:01 PM, Joel Sherrill  wrote:

> On Sun, Jun 23, 2024, 12:43 PM John Howard  wrote:
> 
> Johns recently identified and fixed that problem.)


Building gnat is a bit tricky. You need to use a native compiler that is the 
same version as what you are building cross. Sometimes it can be close but the 
same is more reliable.___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Ada

2024-06-23 Thread John Howard
Hello.

I need Ada for RTEMS on Raspberry Pi. I will settle for whichever versions work 
together.

After moving to gitlab, is Ada continuously built and tested for RTEMS?

Today, my non-gitlab RSB 5.3 build failed on Debian with error in GNAT 7.5.0 
for the aspects.adb file. (That Python UTF-8 non-incremental parsing failure 
also occurred, but Chris Johns recently identified and fixed that problem.)

I will move to gitlab only if necessary.

-- John
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


Re: 6.1rc3 CentOS 7 Build Sweep Report

2024-04-17 Thread John Howard
UTF-8 start byte cannot be 0xff.

Off-by-1 bug is possible. Maybe a hidden control character is throwing off the 
count but being stripped away prior to the attempt to convert to UTF-8.

On Apr 17, 2024, at 1:13 PM, Joel Sherrill  wrote:

Hi

6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3 
SCL). Results should be on the build@ list. One odd issue appears to be in the 
rtems-tester.

Testing a riscv-bsp with spike, I get this output. It is repeated with other 
spike/risc-v bsp tests. Any ideas?

Exception in thread _stdout[spike]:
Traceback (most recent call last):
  File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 916, 
in _bootstrap_inner
self.run()
  File "/opt/rh/rh-python36/root/usr/lib64/python3.6/threading.py", line 864, 
in run
self._target(*self._args, **self._kwargs)
  File "/home/joel/rtems-6.1rc3/tools/6/share/rtems/rtemstoolkit/execute.py", 
line 226, in _readthread
data = data.decode(sys.stdout.encoding)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid 
start byte

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


utf32 test

2024-04-06 Thread John Howard
---

testsuites/samples/utf32/init.c | 43 +-

1 file changed, 43 insertions(+), 0 deletion(-)

create mode 100644 testsuites/samples/utf32/init.c



diff --git a/testsuites/samples/utf32/init.c b/testsuites/samples/utf32/init.c

index 83f6342ab3..5ebcdc9ef2 100644

--- /dev/null

+++ b/testsuites/samples/utf32/init.c

@@ -0,0 +1,43 @@

+/*

+ Author: John Howard

+ Date: April 5, 2024

+ Subject: How to compile and execute this test?

+  $ gcc init.c

+  $ mv a.out utf32

+  $ ./utf32

+*/

+

+#include 

+#include “utf32.h”

+

+int main (void)

+{

+ utf32 v;

+ unsigned i;

+

+ printf (“Author: John Howard\n”);

+ v=0xDEADBEEF; printf (“%s %X\n”, “v=0xDEADBEEF; =>”, v);

+ i=v; i=CODEPOINT_(i); printf (“%s %X\n”, “i=v; i=CODEPOINT_(i); =>”, i);

+ v=CONVERT_(v); printf (“%s %X\n”, “v=CONVERT_(v); =>”, v);

+ i=TESTBIT_(v, 0); printf (“%s %X\n”, “i=TESTBIT_(v, 0); =>”, i);

+ v=SETBIT_(v, 0); printf (“%s %X\n”, “v=SETBIT_(v, 0); =>”, v);

+ v=UNSETBIT_(v, 0); printf (“%s %X\n”, “v=UNSETBIT_(v, 0); =>”, v);

+ i=TESTBIT_(v, 31); printf (“%s %X\n”, “i=TESTBIT_(v, 31); =>”, i);

+ v=UNSETBIT_(v, 31); printf (“%s %X\n”, “v=UNSETBIT_(v, 31); =>”, v);

+ v=SETBIT_(v, 31); printf (“%s %X\n”, “v=SETBIT_(v, 31); =>”, v);

+ i=v; i=CODEPOINT_(i); printf (“%s %X\n”, “i=v; i=CODEPOINT_(i); =>”, i);

+ v=CONVERT_(v); printf (“%s %X\n”, “v=CONVERT_(v); =>”, v);

+ i=TESTBIT_(v, 0); printf (“%s %X\n”, “i=TESTBIT_(v, 0); =>”, i);

+ v=UNSETBIT_(v, 0); printf (“%s %X\n”, “v=UNSETBIT_(v, 0); =>”, v);

+ v=SETBIT_(v, 0); printf (“%s %X\n”, “v=SETBIT_(v, 0); =>”, v);

+ i=TESTBIT_(v, 31); printf (“%s %X\n”, “i=TESTBIT_(v, 31); =>”, i);

+ v=UNSETBIT_(v, 31); printf (“%s %X\n”, “v=UNSETBIT_(v, 31); =>”, v);

+ v=SETBIT_(v, 31); printf (“%s %X\n”, “v=SETBIT_(v, 31); =>”, v);

+ i=CODEPOINT_(v); printf (“%s %X\n”, “i=CODEPOINT_(v); =>”, i);

+ printf (“%s %X\n”, “side effect where v is  =>”, v);

+ v=SETMODEL_(v, 0); printf (“%s %X\n”, “v=SETMODEL_(v, 0); VGA 256 color =>”, 
v);

+ v=SETTEXTURE_(v, 0); printf (“%s %X\n”, “v=SETTEXTURE_(v, 0); =>”, v);

+ v=SETTEXTURE_(v, 255); printf (“%s %X\n”, “v=SETTEXTURE_(v, 255); =>”, v);

+ v=SETMODEL_(v, 7); printf (“%s %X\n”, “v=SETMODEL_(v, 7); CUBITS Fiery =>”, 
v);

+ v=UNSETBIT_(v, 23); v=UNSETBIT_(v, 22); v=UNSETBIT_(v, 21); v=SETMODEL_(v, 
1); printf (“%s %X\n”, “v=SETMODEL_(v, 1); CGA 16 color Blink =>”, v);

+}

-- 

2.42.0

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

utf32 support

2024-04-05 Thread John Howard
---

testsuites/samples/utf32/utf32.h | 45 +-

1 file changed, 45 insertions(+), 0 deletion(-)

create mode 100644 testsuites/samples/utf32/utf32.h



diff --git a/testsuites/samples/utf32/utf32.h b/testsuites/samples/utf32/utf32.h

index 83f6342ab3..5ebcdc9ef2 100644

--- /dev/null

+++ b/testsuites/samples/utf32/utf32.h

@@ -0,0 +1,45 @@

+/*

+ Copyright 2024 John Howard

+ All Rights Reserved.

+ CUBITS is a trademark of John Howard.

+ CUBITS means Capital, Underline, Bold, Italic, Texture, and Strike.

+

+ This file is part of the RTEMS.org test suites samples.

+

+ Permission to use, copy, modify, and/or distribute this software for any

+ purpose with or without fee is hereby granted, provided that the above

+ copyright notice and this permission notice appear in all copies.

+

+ THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES

+ WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF

+ MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR

+ ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES

+ WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN

+ ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF

+ OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

+*/

+

+/* Unicode & ISO 10646-2012 character ranges 0..\U. */

+typedef int utf32;

+

+/* Convert UTF32 Big Endian and Little Endian v ranges 0..0x. */

+#define CONVERT_(v) v) & 255) << 24) | v) >> 8) & 255) << 16) | \

+   v) >> 16) & 255) << 8) | (((v) >> 24) & 255))

+

+/* Set zero-based nth bit of v ranges 0..0x. n ranges 0..31. */

+#define SETBIT_(v,n) ((v) |= (1 << (n)))

+

+/* Unset zero-based nth bit of v ranges 0..0x. n ranges 0..31. */

+#define UNSETBIT_(v,n) ((v) &= ~(1 << (n)))

+

+/* Test zero-based nth bit of v ranges 0..0x. n ranges 0..31. */

+#define TESTBIT_(v,n) (((v) & (1 << (n))) != 0)

+

+/* Unicode & ISO 10646-2012 codepoint v ranges 0..0x10. */

+#define CODEPOINT_(v) ((v) &= 0x1F; (((v) > 0x10) ? ((v) & 0x) : 
(v))

+

+/* CUBITS model: VGA, CGA, Custom, Texture, Cloudy, Glory, Shiny, Fiery. */

+#define SETMODEL_(v,m) ((v) |= ((m) << 21))

+

+/* CUBITS Texture ranges 0..255: VGA color index, CGA text attributes. */

+#define SETTEXTURE_(v,m) ((v) |= ((m) << 24))

-- 

2.42.0

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: utf32 support

2024-03-19 Thread John Howard
A 32 bit character type is supported by FreeBSD.

Unicode 2012 says utf32 must be a 32 bit signed integer. Unicode only defines 
the Codepoint character attribute.

RTEMS now uses libBSD and newlib. Need kernel to support the Codepoint range of 
values. Applications can then use additional user-defined character attributes.

— John

P.S.: UTF32 exists for Unicode in 2012 after consolidation from ISO 10646-2012. 
The two standards merged.

On Mar 19, 2024, at 6:20 AM, Frank Kühndel  
wrote:

Hello John,

just a side node:

Strictly speaking UTF32 does not exist [1]. The correct name is UCS-4 (i.e 
store each character in four bytes). "Current plans are that there will never 
be characters assigned outside the 21-bit code space from 0x00 to 0x10" 
[2].

References:

[1] Section "Unicode encodings" in 
https://tldp.org/HOWTO/Unicode-HOWTO-1.html#ss1.2

[2] Section "What are UCS and ISO 10646?" in 
https://www.cl.cam.ac.uk/~mgk25/unicode.html

Greetings,
fk

> On 3/18/24 19:02, Gedare Bloom wrote:
> I think it would be wchar_t support in newlib.
>> On Mon, Mar 18, 2024 at 11:56 AM Joel Sherrill  wrote:
>> What does support for UTF-32 entail? Do you have an idea what software 
>> functions you are looking for?
>> 
>> I see the International Components for Unicode (ICU) has a converter 
>> (https://icu.unicode.org/download) which looks it might be part of a 
>> solution.
>> 
>> Multibyte character methods defined by POSIX would be in newlib.
>> 
>> I'm not well versed in this area so have questions but I think it basically 
>> comes down to what software libraries an application needs and porting those 
>> to RTEMS -- assuming the license is ok.
>> 
>> --joel
>> 
>>> On Mon, Mar 18, 2024 at 12:15 PM John Howard  wrote:
>>> I want to add utf32 support.
>>> 
>>> Where do I start?
>>> 
>>> — John
>>> ___
>>> devel mailing list
>>> devel@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

-- 
embedded brains GmbH & Co. KG
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11

Registergericht: Amtsgericht München
Registernummer: HRA 117265
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

utf32 support

2024-03-18 Thread John Howard
I want to add utf32 support.

Where do I start?

— John
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Trying to run freebsd on qemu

2024-03-14 Thread John Howard
Try at FreeBSD.org.

On Mar 14, 2024, at 10:18 AM, ashish wrote:

I am trying to run freebsd aarch64 12.x on qemu to know whether freebsd  
supports usb or not.

and Error i am getting is this 
```qemu-system-aarch64: device requires 67108864 bytes, block backend provides 
2097152 bytes```

does anyone tried running freebsd aarch 12 or freebsd arm 12 on qemu
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


[DIFF] 5.3 rpi/libpng16.pc: redundant libz

2024-01-29 Thread John Howard
~/development/rtems/5.3/arm-rtems5/raspberrypi/lib/pkgconfig/libpng16.pc
@@ -8,5 +8,5 @@
Version: 1.6.37
Requires: zlib
Libs: -L${libdir} -lpng16
-Libs.private: -lz -lbsd -lm -lz -lrtemsdefaultconfig
+Libs.private: -lbsd -lm -lz -lrtemsdefaultconfig
Cflags: -I${includedir}
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


rtems 5.3 released libbsd hash mismatch

2024-01-13 Thread John Howard
Greetings. New developer here.

I used RSB 5.3 to target RTEMS to RaspberryPi with an AMD64 Debian bullseye.

sha512sum rtems-libbsd-5.3.tar.xz listed in VERSION is hash mismatch.

Correct is:
c84482cb33e178bdc1e4bbb0390a54d4f9c12db1f1614876dd4ae5218d4b26c2aa61d368bf3fafefcbc49e57008de9f636b11c596310d33320a0152002b012de
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel