Re: Any plan to cleanup x86 arch names?
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 anyway with Jigsaw, > we might as well fix some names. It is not clear if it's worth the effort to > rename files before such a major restructuring. Agreed. Not only will Jigsaw restructure the source tree, but it will change the layout of $JRE/lib and make other changes that will, no doubt, affect some existing code. If we're going to fix all our old arch names, that would be the right time to do it. - Mark
Re: Any plan to cleanup x86 arch names?
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 this. I think where we can be consistent and avoid adding new names for the same thing, we should. Just not sure this will be floating up as any high priority effort any time soon. -kto On Aug 15, 2012, at 1:52 PM, Magnus Ihse Bursie wrote: > 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 have external requirements for their name, and cannot be > easily changed (or at all). For instance, Java programs expect a specific > os.arch property. Library names must be named amd64 on Solaris (as far as I > understand). Marketing is likely to have their own view on what to name the > packages. Etc. > > 2) Changing names on files or directories (unfortunately) makes version > control harder. If files are to be moved around all over the place anyway > with Jigsaw, we might as well fix some names. It is not clear if it's worth > the effort to rename files before such a major restructuring. > > 3) If we should change all instances that we can, we still have to agree on > *what* to call it. Not everyone thinks that "x86" is the obvious choice. And > even if this is the most common view (I think it is), what about the 64-bit > platform? x86_64? x64? amd64? I've heard people defend all three names. > > I actually posted a proposal for naming cpu's in the new build infra some > time ago (see > http://mail.openjdk.java.net/pipermail/build-infra-dev/2012-June/001019.html). > It boiled down to: > 32-bit Intel: x86 > 64-bit Intel: x86_64 > Intel arctitecture: x86 > > (As reference: > 32-bit Sparc: sparc > 64-bit Sparc: sparcv9 > Sparc architecture: sparc) > > There was some follow-up discussion, mostly on how to identify what different > kinds of names we need. > > /Magnus
Re: Any plan to cleanup x86 arch names?
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 the build process we will try and be consistent, not sure we can fix the source file naming, or system or Java property conventions. -kto > > -Dmitry > > -- > Dmitry Samersoff > Java Hotspot development team, SPB04 > * There will come soft rains ... >
Re: Any plan to cleanup x86 arch names?
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 problem is the same here, though. We can't e.g. go chaning the value
of os.arch or the names of binaries and libraries. It does not really
matter that you want to limit it to one platform. In fact, it would be
easier if you ask "can we clean up the platform name mess of binaries?"
rather than "can we clean up platform X?".
/Magnus
Re: Any plan to cleanup x86 arch names?
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 wrote:
> 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 have external requirements for their name, and cannot be
> easily changed (or at all). For instance, Java programs expect a
> specific os.arch property. Library names must be named amd64 on Solaris
> (as far as I understand). Marketing is likely to have their own view on
> what to name the packages. Etc.
>
> 2) Changing names on files or directories (unfortunately) makes version
> control harder. If files are to be moved around all over the place
> anyway with Jigsaw, we might as well fix some names. It is not clear if
> it's worth the effort to rename files before such a major restructuring.
>
> 3) If we should change all instances that we can, we still have to agree
> on *what* to call it. Not everyone thinks that "x86" is the obvious
> choice. And even if this is the most common view (I think it is), what
> about the 64-bit platform? x86_64? x64? amd64? I've heard people defend
> all three names.
>
> I actually posted a proposal for naming cpu's in the new build infra
> some time ago (see
> http://mail.openjdk.java.net/pipermail/build-infra-dev/2012-June/001019.html).
> It boiled down to:
> 32-bit Intel: x86
> 64-bit Intel: x86_64
> Intel arctitecture: x86
>
> (As reference:
> 32-bit Sparc: sparc
> 64-bit Sparc: sparcv9
> Sparc architecture: sparc)
>
> There was some follow-up discussion, mostly on how to identify what
> different kinds of names we need.
>
> /Magnus
--
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...
Re: Any plan to cleanup x86 arch names?
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 have external requirements for their name, and cannot be easily changed (or at all). For instance, Java programs expect a specific os.arch property. Library names must be named amd64 on Solaris (as far as I understand). Marketing is likely to have their own view on what to name the packages. Etc. 2) Changing names on files or directories (unfortunately) makes version control harder. If files are to be moved around all over the place anyway with Jigsaw, we might as well fix some names. It is not clear if it's worth the effort to rename files before such a major restructuring. 3) If we should change all instances that we can, we still have to agree on *what* to call it. Not everyone thinks that "x86" is the obvious choice. And even if this is the most common view (I think it is), what about the 64-bit platform? x86_64? x64? amd64? I've heard people defend all three names. I actually posted a proposal for naming cpu's in the new build infra some time ago (see http://mail.openjdk.java.net/pipermail/build-infra-dev/2012-June/001019.html). It boiled down to: 32-bit Intel: x86 64-bit Intel: x86_64 Intel arctitecture: x86 (As reference: 32-bit Sparc: sparc 64-bit Sparc: sparcv9 Sparc architecture: sparc) There was some follow-up discussion, mostly on how to identify what different kinds of names we need. /Magnus
Any plan to cleanup x86 arch names?
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 ...
