On Tue, 1 Nov 2016, Paul Burton wrote:
> BTW, do you have a feel for whether there's a good r2k/r3k platform (ideal
> would be some software emulator if any are good enough) that we could hook up
> to our continuous integration system? That would help us to catch any
> regressions like this in
On Tue, 1 Nov 2016, Paul Burton wrote:
> BTW, do you have a feel for whether there's a good r2k/r3k platform (ideal
> would be some software emulator if any are good enough) that we could hook up
> to our continuous integration system? That would help us to catch any
> regressions like this in
On Monday, 31 October 2016 16:27:01 GMT Maciej W. Rozycki wrote:
> Fix a regression introduced with commit 2db9ca0a3551 ("MIPS: Use struct
> mips_abi offsets to save FP context") for MIPS I/I FP signal contexts,
> by converting save/restore code to the updated internal API. Start FGR
> offsets
On Monday, 31 October 2016 16:27:01 GMT Maciej W. Rozycki wrote:
> Fix a regression introduced with commit 2db9ca0a3551 ("MIPS: Use struct
> mips_abi offsets to save FP context") for MIPS I/I FP signal contexts,
> by converting save/restore code to the updated internal API. Start FGR
> offsets
Fix a regression introduced with commit 2db9ca0a3551 ("MIPS: Use struct
mips_abi offsets to save FP context") for MIPS I/I FP signal contexts,
by converting save/restore code to the updated internal API. Start FGR
offsets from 0 rather than SC_FPREGS from $a0 and use $a1 rather than
the offset
Fix a regression introduced with commit 2db9ca0a3551 ("MIPS: Use struct
mips_abi offsets to save FP context") for MIPS I/I FP signal contexts,
by converting save/restore code to the updated internal API. Start FGR
offsets from 0 rather than SC_FPREGS from $a0 and use $a1 rather than
the offset
6 matches
Mail list logo