Hi Everyone,
Currently we uses i386, i486 and i586 within x86 build.
Do we have a plan to cleanup it and replace to just x86?
-Dmitry
--
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...
On 2012-08-15 10:38, Dmitry Samersoff wrote:
Hi Everyone,
Currently we uses i386, i486 and i586 within x86 build.
Not only the 32-bit Intel architecture, but the 64-bit as well has
naming confusions.
Unfortunately, it is not that simple to just replace everything with x86.
1) Some things
Magnus,
Thank you for the background.
I understand that big architecture names cleanup contains lots of
underwater stones.
It's why I'm asking just for one piece of this mess - I would like
to have {i386,i486,i586} changed to the single name.
-Dmitry
On 2012-08-15 15:52, Magnus Ihse Bursie
On 2012-08-15 14:15, Dmitry Samersoff wrote:
Magnus,
Thank you for the background.
I understand that big architecture names cleanup contains lots of
underwater stones.
It's why I'm asking just for one piece of this mess - I would like
to have {i386,i486,i586} changed to the single name.
The
On Aug 15, 2012, at 10:38 AM, Dmitry Samersoff wrote:
Hi Everyone,
Currently we uses i386, i486 and i586 within x86 build.
Yeah, historic stuff. This is a more difficult problem than it seems, as
Magnus says.
Do we have a plan to cleanup it and replace to just x86?
Where we can, in
amd64 was very company specific and as far as I knew, we were favoring x64, but
I have no objection to x86_64.
But in some places, like the jre/lib/ARCH name, we are kind of stuck with
amd64, but now that I think about it,
I'm not exactly sure why we would be stuck with any directory name like
2012/8/15 4:52 -0700, magnus.ihse.bur...@oracle.com:
Unfortunately, it is not that simple to just replace everything with x86.
Sad, but true.
...
2) Changing names on files or directories (unfortunately) makes version
control
harder. If files are to be moved around all over the place
