Dear sirs,
When trying to generate code debuggable by GDB, I meet a problem:
* it seems mips C code will expect a frame pointer = sp after stack
adjustment
* but in cpupara.pas, when we create para info, we don't know yet the
whole stack size, thus the reference offset cannot be set correctly
On Sun, 10 Jun 2012 08:18:36 +0800 (CST)
"Fuxin Zhang" wrote:
>
> >>>
> >>> Please keep copyright in mind when adding new stuff!
> I have removed the link in the wiki and the files from lemote web. Sorry
> for the thinkless action.
> Opening the ABI documents should be a good thing to help its e
On Sat, 09 Jun 2012 20:52:01 +
Mark Morgan Lloyd wrote:
> microc...@zoho.com wrote:
> > On Sat, 9 Jun 2012 09:27:30 +0800 (CST)
> > "Fuxin Zhang" wrote:
> >
> >>> Fuxin, is there a formal 64 bit ABI from MIPS Inc.? I think you said
> >>> earlier the Linux 64 bit ABI is not exactly stable, b
>>>
>>> Please keep copyright in mind when adding new stuff!
I have removed the link in the wiki and the files from lemote web. Sorry
for the thinkless action.
Opening the ABI documents should be a good thing to help its eco-system,
if I have chance I will try to pasuade mips.
>>
>> Absolutely. Ho
microc...@zoho.com wrote:
On Sat, 9 Jun 2012 09:27:30 +0800 (CST)
"Fuxin Zhang" wrote:
Fuxin, is there a formal 64 bit ABI from MIPS Inc.? I think you said
earlier the Linux 64 bit ABI is not exactly stable, but there are a few
other OS running on 64 bit MIPS (OpenBSD and FreeBSD and NetBSD, a
On Sat, 09 Jun 2012 15:40:38 +0200
Florian Klämpfl wrote:
> Am 08.06.2012 14:54, schrieb microc...@zoho.com:
> > On Fri, 8 Jun 2012 17:15:51 +0800 (CST)
> > "Fuxin Zhang" wrote:
> >
> >>
> >>> I made a start at trying to get assembler and backend info into the
> >>> Wiki, my intention was to at
On Sat, 9 Jun 2012 09:27:30 +0800 (CST)
"Fuxin Zhang" wrote:
>
> >
> > Fuxin, is there a formal 64 bit ABI from MIPS Inc.? I think you said
> > earlier the Linux 64 bit ABI is not exactly stable, but there are a few
> > other OS running on 64 bit MIPS (OpenBSD and FreeBSD and NetBSD, as far
> >
Am 09.06.2012 16:44, schrieb Mark Morgan Lloyd:
> Florian Klämpfl wrote:
>> Am 08.06.2012 14:54, schrieb microc...@zoho.com:
>>> On Fri, 8 Jun 2012 17:15:51 +0800 (CST)
>>> "Fuxin Zhang" wrote:
>>>
> I made a start at trying to get assembler and backend info into the
> Wiki, my intention w
Florian Klämpfl wrote:
Am 08.06.2012 14:54, schrieb microc...@zoho.com:
On Fri, 8 Jun 2012 17:15:51 +0800 (CST)
"Fuxin Zhang" wrote:
I made a start at trying to get assembler and backend info into the
Wiki, my intention was to at least have URLs for the various ABIs. I
rather ground to a halt
Am 08.06.2012 14:54, schrieb microc...@zoho.com:
> On Fri, 8 Jun 2012 17:15:51 +0800 (CST)
> "Fuxin Zhang" wrote:
>
>>
>>> I made a start at trying to get assembler and backend info into the
>>> Wiki, my intention was to at least have URLs for the various ABIs. I
>>> rather ground to a halt after
Hi,
09.06.2012 5:27, Fuxin Zhang:
I get a copy from my colleague for N32 ABI, no N64 found yet.See
http://www.lemote.com/upfiles/mips-abi-n32.pdf. I put it here because no
confidential sign in the document. But I am not sure whether it comes from
MIPS as a material to licensee. Will check later.
> Hi,
>
> Based on trunk r21549, I have uploaded all my patches to my branch,
> please help to review and merge if possible.
>
> svn log --stop-on-copy
> http://svn.freepascal.org/svn/fpc/branches/foxsen/mips ：
>
>
> r21564
Hi,
Based on trunk r21549, I have uploaded all my patches to my branch,
please help to review and merge if possible.
svn log --stop-on-copy
http://svn.freepascal.org/svn/fpc/branches/foxsen/mips ：
r21564 | foxsen | 2012-0
>
> On 08 Jun 2012, at 17:57, Fuxin Zhang wrote:
>
>> Since mipsel/mips has most of the code equal(code is endian free or use
>> endian setting in target_info), I would like to propose make such
>> conventions:
>>
>> define mips, cpumips, mips32 for use of common mips related code
>> define mi
On 08 Jun 2012, at 17:57, Fuxin Zhang wrote:
> Since mipsel/mips has most of the code equal(code is endian free or use
> endian setting in target_info), I would like to propose make such
> conventions:
>
> define mips, cpumips, mips32 for use of common mips related code
> define mipsel/mips
15 matches
Mail list logo
