From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Wilson To: Andre McCurdy Cc: gcc AT gcc.gnu.org Subject: Re: MIPS16 -mentry pseudo instruction definitions Date: Mon, 13 Sep 1999 12:32:00 -0000 Message-id: <199909131932.MAA19360@rtl.cygnus.com> References: <19990913125633.17782.rocketmail@web601.yahoomail.com> X-SW-Source: 1999-09/msg00500.html Has anyone ever used this code ?? I believe so, but it has likely been a while, and it may have only been tested on a simulator. Aside from this possible bug, there are no comments which give a clue as to why the stack frame size is fixed at 32bytes, which is the question which really bothers me. Probably it was just chosen as a convenient number. entry has to allocate some amount of stack space, and there is no opcode space to encode the amount, so someone picked a number that seemed right. Big enough to satisfy most frames, but not too big that it would waste too much stack space. Is there any way of tracking down when the -mentry option became part of gcc (and where the code come from) ? It was written by Cygnus. You could try asking LSI. I believe the original specification came from them. According to the ChangeLog file, the entry.S file was written by Mark Alexander, but he isn't at Cygnus anymore, and I don't know how to reach him. The gcc code supporting -mentry was originally written by Ian Taylor, but he isn't at Cygnus anymore either, though he is reachable by mail. It was originally put on a branch, and then merged into (what was then called) EGCS. I believe that the code has never been used after it was merged into egcs, and I also suspect there are bugs in the code resulting from merging problems. Jim From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Wilson To: Andre McCurdy Cc: gcc@gcc.gnu.org Subject: Re: MIPS16 -mentry pseudo instruction definitions Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <199909131932.MAA19360@rtl.cygnus.com> References: <19990913125633.17782.rocketmail@web601.yahoomail.com> X-SW-Source: 1999-09n/msg00500.html Message-ID: <19990930180200.mJFnYU9yXY5_xP-EltdPWr1eNP-5aSx52i9m5iKHDXU@z> Has anyone ever used this code ?? I believe so, but it has likely been a while, and it may have only been tested on a simulator. Aside from this possible bug, there are no comments which give a clue as to why the stack frame size is fixed at 32bytes, which is the question which really bothers me. Probably it was just chosen as a convenient number. entry has to allocate some amount of stack space, and there is no opcode space to encode the amount, so someone picked a number that seemed right. Big enough to satisfy most frames, but not too big that it would waste too much stack space. Is there any way of tracking down when the -mentry option became part of gcc (and where the code come from) ? It was written by Cygnus. You could try asking LSI. I believe the original specification came from them. According to the ChangeLog file, the entry.S file was written by Mark Alexander, but he isn't at Cygnus anymore, and I don't know how to reach him. The gcc code supporting -mentry was originally written by Ian Taylor, but he isn't at Cygnus anymore either, though he is reachable by mail. It was originally put on a branch, and then merged into (what was then called) EGCS. I believe that the code has never been used after it was merged into egcs, and I also suspect there are bugs in the code resulting from merging problems. Jim