On Sun, Feb 12, 2023 at 05:34:43PM -0500, Rich Felker wrote:
> On Sun, Feb 12, 2023 at 08:17:04AM +, Bastian Bittorf wrote:
> > On Sat, Feb 11, 2023 at 02:30:44PM -0500, Rich Felker wrote:
> > > > > .hidden __hwcap
> > > > > .long __hwcap-.
> > > > > -1: mflr 4
> > > > > -
On Sun, Feb 12, 2023 at 08:17:04AM +, Bastian Bittorf wrote:
> On Sat, Feb 11, 2023 at 02:30:44PM -0500, Rich Felker wrote:
> > > > .hidden __hwcap
> > > > .long __hwcap-.
> > > > -1: mflr 4
> > > > - lwz 5, 0(4)
> > > > - lwzx 4, 4, 5
> > > > - andis. 4,
On Sat, Feb 11, 2023 at 02:30:44PM -0500, Rich Felker wrote:
> > > .hidden __hwcap
> > > .long __hwcap-.
> > > -1: mflr 4
> > > - lwz 5, 0(4)
> > > - lwzx 4, 4, 5
> > > - andis. 4, 4, 0x80
> > > +1: mflr 6
> > > + lwz 5, 0(6)
> > > + lwzx 6, 6, 5
> > > + andis. 6, 6, 0x80
> > >
On Sat, Feb 11, 2023 at 07:27:39PM +, Bastian Bittorf wrote:
> On Sat, Feb 11, 2023 at 09:01:03AM -0500, Rich Felker wrote:
> > It looks like the powerpc spe longjmp code is clobbering the value
> > argument. Try the attached patch.
>
> > diff --git a/src/setjmp/powerpc/longjmp.S
On Sat, Feb 11, 2023 at 09:01:03AM -0500, Rich Felker wrote:
> It looks like the powerpc spe longjmp code is clobbering the value
> argument. Try the attached patch.
> diff --git a/src/setjmp/powerpc/longjmp.S b/src/setjmp/powerpc/longjmp.S
> index 611389fe..465e4cd7 100644
> ---
On Sat, Feb 11, 2023 at 12:51:47PM +, Bastian Bittorf wrote:
> With OpenWRT i recognized a strange behavior of ash-shell scripts.
> It happens only on target PowerPC, e.g. m68k, arm, mips, x86 are
> unaffected.
to be more clear:
it seems to affect musl, but not glibc build.
bye, Bastian
On Sat, Feb 11, 2023 at 12:51:47PM +, Bastian Bittorf wrote:
> With OpenWRT i recognized a strange behavior of ash-shell scripts.
> It happens only on target PowerPC, e.g. m68k, arm, mips, x86 are
> unaffected.
>
> The visible strange behavior in 'ash' is:
>
> $ test A -gt 5 && echo OK
>
With OpenWRT i recognized a strange behavior of ash-shell scripts.
It happens only on target PowerPC, e.g. m68k, arm, mips, x86 are
unaffected.
The visible strange behavior in 'ash' is:
$ test A -gt 5 && echo OK
ash: A: out of range
OK
Ofcourse this wrong returncode leads to all sorts of
