Bug#961445: Fixes in upstream repo commits.

2020-08-15 Thread Tim Eves
I believe the upstream commits 19c55e0
<https://github.com/silnrsi/grcompiler/commit/19c55e009386d62468d97948db581cff08962bbb>
and 89fa0b3
<https://github.com/silnrsi/grcompiler/commit/89fa0b3019c4f32b3a50289648fa33c2a2374c60>
in the upstream Github repo should fix this bug. I have tested this on on
32bit emulated MIPS system running Debian 10 and it
passes all the regression tests.
-- 
Tim Eves
Writing Systems Technology - SIL International


Bug#961444: Fix for grcompiler FTBFS on architectures where char is unsigned

2020-08-16 Thread Tim Eves
I've reworked the assert to be explicit about checking the integer range
could fit in a signed 8 bit value in commit
https://github.com/silnrsi/grcompiler/commit/a60a04691c42f3f99543c83f9911c84e44a268fe

Hopefully this will fix the issue and it isn't really managing to generate
an offset outside the -128 <->127 range.
-- 
Tim Eves
Writing Systems Technology - SIL International


Bug#961438: Fix for: grcompiler FTBFS on i386: compare_PigLatinTest_v2 failed

2020-08-17 Thread Tim Eves
A fix for this bug is in upstream commit a9e6dec
<https://github.com/silnrsi/grcompiler/commit/a9e6dec71cbc11c5d637fa342e51867330001862>,
and has been tested against 32 and 64 bit xenial boxes which were both
exhibiting the same bug described here.
--
Tim Eves
Writing Systems Technology - SIL International


Bug#805323: Fwd: Bug #805323: graphite2 ARM HP PA FTBFS

2016-01-04 Thread Tim Eves
Hi Rene,

I also have an RPi2 here so I've used that to test this round of fixes,
this bug should be fixed for good now as I've re-factored the problem code
to a more straightforward form.
I've also fixed the CMake policy warnings.

Thanks for the log that was a big help. I noticed in the log that the cmake
invocation is being passed:

-DGRAPHITE2_NTRACING:bool=1

Whilst it works I believe that is a typo, and it should be:

-DGRAPHITE2_NTRACING:BOOL=ON

Regards,
Tim

On Fri, Dec 18, 2015 at 3:29 AM, Rene Engelhard  wrote:

> forwarded 805323 Tim Eves 
> thanks
>
> Hi Tim,
>
> On Thu, Dec 17, 2015 at 11:37:20AM +0700, Tim Eves wrote:
> >The bug has been fixed in commit
> 594d92c0c0efbd3a87a32260f57e502200c351a7
> >"Fix misaligned access on ARM and HP PA processors during collision".
> >
> >It was a non-32 bit aligned 32bit read, some processors (ARM) are
> stricter
> >about this than others (Intel), which could explain the fact it built
> fine
> >on other BE archs.
>
> Unfortunately the patch doesn't work for me, I still get a build failure
> on armhf.
> (See attached buildlog). gdb'ing core gives
>
> (cowbuilder-unstable)rene@raspberrypi:~/tmp/graphite2-1.3.4/build/tests$
> gdb --core=core
> GNU gdb (Debian 7.10-1) 7.10
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "arm-linux-gnueabihf".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> [New LWP 14630]
> Core was generated by `/usr/bin/python
> /data/tmp/graphite2-1.3.4/tests/fnttxtrender --graphite_library'.
> Program terminated with signal SIGBUS, Bus error.
> #0  0x768e8314 in ?? ()
> (gdb) bt
> #0  0x768e8314 in ?? ()
> #1  0x768e8306 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb)
>
> which is not exactly helpful but the same I get without the patch. (and
> yes, the patch IS applied.)
>
> >We have been regularly testing against armhf on the Qemu Versatile
> Express
> >emulator, under which it turns out this bug is not reproducible.
> Once we
> >tried with real hardware (RPi B+) it showed up.
>
> RPi 2 here.
>
> Regards,
>
> Rene
>



-- 
Tim Eves
NRSI - SIL International