From Fedora Project Wiki
No edit summary
No edit summary
Line 1: Line 1:
<!-- All fields on this form are required to be accepted by FESCo.
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
= Make 64-bit the primary arch for 64-bit PowerPC hardware =
= Make 64-bit the primary arch for 64-bit PowerPC hardware =
<!-- The name of your feature -->


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
Provide a means for Fedora on 64-bit PowerPC hardware to have 64-bit as the primary architecture, which would enable users to better exploit their 64-bit PowerPC hardware and avoid restrictions associated with 32-bit applications.
Provide a means for Fedora on 64-bit PowerPC hardware to have 64-bit as the primary architecture, which would enable users to better exploit their 64-bit PowerPC hardware and avoid restrictions associated with 32-bit applications.


== Owner ==
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:maynardj| Maynard Johnson]]
* Name: [[User:maynardj| Maynard Johnson]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* email: <maynardj@us.ibm.com>
* email: <maynardj@us.ibm.com>


== Current status ==
== Current status ==
* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]  
* Targeted release: [[Releases/11 | Fedora 11 ]]  
* Last updated: (February 12, 2009)
* Last updated: 2009-02-12
* Percentage of completion: XX%
* Percentage of completion: n/a?
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
Currently, 32-bit ppc is the default architecture, whether Fedora is installed on 32-bit or 64-bit PowerPC hardware.  This leads to difficulties with software development, integration and installation when trying to use 64-bit programs on 64-bit hardware.  Making 64-bit the default arch on 64-bit hardware is the simplest way to resolve these issues.  This change in primary arch should also be accompanied with changing the default target for the compiler to be 64-bit (i.e., '-m64').  
Currently, 32-bit ppc is the default architecture, whether Fedora is installed on 32-bit or 64-bit PowerPC hardware.  This leads to difficulties with software development, integration and installation when trying to use 64-bit programs on 64-bit hardware.  Making 64-bit the default arch on 64-bit hardware is the simplest way to resolve these issues.  This change in primary arch should also be accompanied with changing the default target for the compiler to be 64-bit (i.e., '-m64').  


Line 34: Line 19:


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
Users who install Fedora on 64-bit PowerPC hardware will have a much more natural and smooth experience between their software and hardware, leading to higher satisfaction.
Users who install Fedora on 64-bit PowerPC hardware will have a much more natural and smooth experience between their software and hardware, leading to higher satisfaction.


== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
The scope of this change request is system-wide.  I believe that, currently, ppc32 and ppc64 packages are built in separate buildroots.  What I believe needs to be done to support this feature is:
The scope of this change request is system-wide.  I believe that, currently, ppc32 and ppc64 packages are built in separate buildroots.  What I believe needs to be done to support this feature is:
 
# a pure ppc64 repo
1) a pure ppc64 repo
# support in anaconda to do the right installation
 
# support in yum
2) support in anaconda to do the right installation
# support in the repo compose scripts to do the multilib stuff properly
 
3) support in yum
 
4) support in the repo compose scripts to do the multilib stuff properly
 


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
Special hardware:  64-bit PowerPC hardware is needed
Special hardware:  64-bit PowerPC hardware is needed
 
# Install the ppc64 build on a 64-bit PowerPC system, installing all base packages (i.e., the ppc64 packages).
 
# Perform standard tests.
1. Install the ppc64 build on a 64-bit PowerPC system, installing all base packages (i.e., the ppc64 packages).
# Ensure that C and C++ compilation of test programs results in 64-bit executables.
 
# Install secondary arch packages (i.e., 32-bit ppc).
2. Perform standard tests.
# Ensure that C and C++ compilation using -m32 is successful.
 
# Run some popular 32-bit applications (from previous Fedora releases) to verify good bi-arch support.
3. Ensure that C and C++ compilation of test programs results in 64-bit executables.
 
4. Install secondary arch packages (i.e., 32-bit ppc).
 
5. Ensure that C and C++ compilation using -m32 is successful.
 
6. Run some popular 32-bit applications (from previous Fedora releases) to verify good bi-arch support.


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Software developers who install Fedora on 64-bit PowerPC hardware will notice that they don't have to bend over backwards to get their software to build 64-bit.  The default 64-bit execution environment will also be appreicated.
Software developers who install Fedora on 64-bit PowerPC hardware will notice that they don't have to bend over backwards to get their software to build 64-bit.  The default 64-bit execution environment will also be appreicated.


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* Since this request is a system-wide change to the build process for PowerPC, there are no known dependencies.
 
Since this request is a system-wide change to the build process for PowerPC, there are no known dependencies.


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* None necessary, revert to previous release behaviour.


None necessary, revert to previous release behaviour.
== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* None
 
None


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
* Users installing or upgrading to Fedora 11 on 64-bit PowerPC hardware should note that the primary architecture is now ppc64.  Package installation will default to ppc64, and compilation of C/C++ source code using Fedora-supplied compilers will default to 64-bit.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
Users installing or upgrading to Fedora 11 on 64-bit PowerPC hardware should note that the primary architecture is now ppc64.  Package installation will default to ppc64, and compilation of C/C++ source code using Fedora-supplied compilers will default to 64-bit.


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/PPC64_as_primary]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/PPC64_as_primary]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->


 
[[Category:FeatureReadyForFesco]]
[[Category:FeatureReadyForWrangler]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 22:47, 19 February 2009

Make 64-bit the primary arch for 64-bit PowerPC hardware

Summary

Provide a means for Fedora on 64-bit PowerPC hardware to have 64-bit as the primary architecture, which would enable users to better exploit their 64-bit PowerPC hardware and avoid restrictions associated with 32-bit applications.

Owner

Current status

  • Targeted release: Fedora 11
  • Last updated: 2009-02-12
  • Percentage of completion: n/a?

Detailed Description

Currently, 32-bit ppc is the default architecture, whether Fedora is installed on 32-bit or 64-bit PowerPC hardware. This leads to difficulties with software development, integration and installation when trying to use 64-bit programs on 64-bit hardware. Making 64-bit the default arch on 64-bit hardware is the simplest way to resolve these issues. This change in primary arch should also be accompanied with changing the default target for the compiler to be 64-bit (i.e., '-m64').

Ideally, this change should not prevent ppc32 software developed on earlier Fedora releases from being executed on Fedora 11. In theory, that implies a full complement of 32-bit runtime libraries to be made available in separate 32-bit packages (the inverse of what is provided today on Fedora). In practice, a reasonable approach may be to focus on providing just a subset of 32-bit libraries -- i.e., the most commonly used libraries.

Benefit to Fedora

Users who install Fedora on 64-bit PowerPC hardware will have a much more natural and smooth experience between their software and hardware, leading to higher satisfaction.

Scope

The scope of this change request is system-wide. I believe that, currently, ppc32 and ppc64 packages are built in separate buildroots. What I believe needs to be done to support this feature is:

  1. a pure ppc64 repo
  2. support in anaconda to do the right installation
  3. support in yum
  4. support in the repo compose scripts to do the multilib stuff properly

How To Test

Special hardware: 64-bit PowerPC hardware is needed

  1. Install the ppc64 build on a 64-bit PowerPC system, installing all base packages (i.e., the ppc64 packages).
  2. Perform standard tests.
  3. Ensure that C and C++ compilation of test programs results in 64-bit executables.
  4. Install secondary arch packages (i.e., 32-bit ppc).
  5. Ensure that C and C++ compilation using -m32 is successful.
  6. Run some popular 32-bit applications (from previous Fedora releases) to verify good bi-arch support.

User Experience

Software developers who install Fedora on 64-bit PowerPC hardware will notice that they don't have to bend over backwards to get their software to build 64-bit. The default 64-bit execution environment will also be appreicated.

Dependencies

  • Since this request is a system-wide change to the build process for PowerPC, there are no known dependencies.

Contingency Plan

  • None necessary, revert to previous release behaviour.

Documentation

  • None

Release Notes

  • Users installing or upgrading to Fedora 11 on 64-bit PowerPC hardware should note that the primary architecture is now ppc64. Package installation will default to ppc64, and compilation of C/C++ source code using Fedora-supplied compilers will default to 64-bit.

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/PPC64_as_primary&oldid=80257"