Re: [EXTERNAL] Re: 64-bit integer typedef's and -fpic lead to infinite loop and growing memory use in port to x86-32

["Barnes, Richard" <Richard.Barnes@stratus.com>]

I found the problem, and it was a mistake I made elsewhere that resulted in %edx being busy everywhere. I have fixed it and consider the issue resolved.

Richard Barnes

________________________________
From: Barnes, Richard <Richard.Barnes@stratus.com>
Sent: Friday, May 28, 2021 3:59 PM
To: H.J. Lu <hjl.tools@gmail.com>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: 64-bit integer typedef's and -fpic lead to infinite loop and growing memory use in port to x86-32

Our OS is not built with gcc. It is built with native compilers and linkers. It sounds like you are talking about cross compiling, which is something we have considered but hope to avoid.

Richard Barnes
________________________________
From: H.J. Lu <hjl.tools@gmail.com>
Sent: Friday, May 28, 2021 3:52 PM
To: Barnes, Richard <Richard.Barnes@stratus.com>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: 64-bit integer typedef's and -fpic lead to infinite loop and growing memory use in port to x86-32

[EXTERNAL SENDER: This email originated from outside of Stratus Technologies. Do not click links or open attachments unless you recognize the sender and know the content is safe.]

On Fri, May 28, 2021 at 12:42 PM Barnes, Richard
<Richard.Barnes@stratus.com> wrote:
>
> Unfortunately, our OS is only a 32-bit OS. It's ABI is only a 32-bit ABI. As you imply, if we had a 64-bit OS, we would have more registers and more memory and would probably avoid this problem. Also, libgcc2.c is supposed to be built natively by the gcc-10.2.0 compiler you have just created.
>

Are you aware that you can build a 32-bit OS with x86-64?  You can try
-mx32 with
GCC on Ubuntu.  You will get more registers as well as IP relative addressing.


--
H.J.