On Tue, 8 May 2012, Richard Sandiford wrote:
> > Are you using a hard-float multilib for your -mabi=32/-mips16 Linux
> > testing?
>
> Yeah. As an example:
>
>http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg00393.html
>
> which doesn't look to bad. Clean fortran results, which I expect
"Maciej W. Rozycki" writes:
>> > and the mips-linux-gnu configuration is not ready yet for MIPS16 testing.
>>
>> Out of interest, what goes wrong? I've been testing -mabi=32/-mips16 on
>> mips64-linux-gnu for some time without difficulty.
>
> I've thought some pieces are missing upstream, but p
Hi Richard,
Resurrecting the issue now that I have new data.
On Wed, 14 Dec 2011, Richard Sandiford wrote:
> > After some thinking I decided the simplest approach will be just emitting
> > the missing location directive in the context of the MIPS16 thunk being
> > built that will apply to th
"Maciej W. Rozycki" writes:
> After some thinking I decided the simplest approach will be just emitting
> the missing location directive in the context of the MIPS16 thunk being
> built that will apply to the actual function prologue. The resulting
> change is included below -- this just repe
Hi,
I've noticed in the presence of a specific MIPS16 function thunk, GCC
fails to emit suitable DWARF-2 location directives, which in turn causes
DWARF-2 line records to provide truncated information. This is probably
best illustrated with an example.
Given the following source code:
$ ca
