"Maciej W. Rozycki" writes:
> On Tue, 8 May 2012, Richard Sandiford wrote:
>> > gcc-mips16-gp-pseudo-loc.patch
>> > Index: gcc-fsf-trunk-quilt/gcc/config/mips/mips.c
>> > ===
>> > --- gcc-fsf-trunk-quilt.orig/gcc/config/mips/mips.c
On Tue, 8 May 2012, Richard Sandiford wrote:
> > gcc-mips16-gp-pseudo-loc.patch
> > Index: gcc-fsf-trunk-quilt/gcc/config/mips/mips.c
> > ===
> > --- gcc-fsf-trunk-quilt.orig/gcc/config/mips/mips.c 2012-05-02
> > 23:42:46.185566469 +
"Maciej W. Rozycki" writes:
> gcc-mips16-gp-pseudo-loc.patch
> Index: gcc-fsf-trunk-quilt/gcc/config/mips/mips.c
> ===
> --- gcc-fsf-trunk-quilt.orig/gcc/config/mips/mips.c 2012-05-02
> 23:42:46.185566469 +0100
> +++ gcc-fsf-trunk-
Hi,
I have been investigating some failures in the MIPS16 GDB test suite that
appeared to me that was caused by some weird out-of place line
information.
For example we get this in gdb.base/break.exp, where a breakpoint is set
at main and the beginning of the function (after removing some
"
