Re: pdumper on Solaris 10

[Pip Cet]

"Po Lu" <luangruo@yahoo.com> writes:

> Pip Cet <pipcet@protonmail.com> writes:
>
>> "Eli Zaretskii" <eliz@gnu.org> writes:
>>
>>>> > Modern x86 CPUs can handle 64-bit values just fine, thank you.
>>>>
>>>> Modern x86 CPUs running 32-bit code (x86, not x32) still need two
>>>> register names for each 64-bit value.  With 8 GPRs, that's a significant
>>>> problem. So, no, "just fine" isn't accurate here.
>>>
>>> I again disagree.  And you forget other registers.
>>
>> I think this is a perfect example of why discussions with Eli are so
>> hard. What do you disagree with? Which mysterious "other registers" do
>> you mean? Why do you think I "forget" about them, with the implication
>> that I do not understand the x86 architecture?
>
> I think it's clear that users of the 32-bit PC architecture are expected
> to sacrifice some performance by their choice.  Why cannot the question
> whether the tradeoffs are acceptable be reserved to those users?  The
> mere existence of the USE_WIDE_INT MinGW configuration is evidence
> enough that users exist who do not need our arbitrary judgement.

I have no idea what you're responding to here.  Of course users will
continue to be able to use 32-bit PCs, and there is no "arbitrary
judgement" in anything I proposed.  I propose to remove WIDE_EMACS_INT
(if that is what you're talking about?  I honestly don't know) because
it's no longer necessary to make any tradeoffs there, not because I
think that no one should ever have used it.

Pip