➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author a.badger
Recipients Arfrever, a.badger, barry, bkabrda, doko, ncoghlan, rkuska, steve.dower
Date 2015-04-21.13:06:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429621563.36.0.392201083626.issue23966@psf.upfronthosting.co.za>
In-reply-to
Content 
Note for doko/barry: The multiarch/Tuples page should have a section on how the MultiArch Tuples interact with hwcaps (or a link to such a section in a different document).  The rationale for not using Gnu-Triplets in MulitArch/Tuples currently says that we do not want separate entries for (as an example) i386 vs i686 instructions but does not tell why.

https://wiki.debian.org/Multiarch/TheCaseForMultiarch#Mixed_ABIs_and_instruction_set_extensions  says that the i386 vs i686 use case is probably better addressed by glibc's hwcaps but points back to MultiArch/Tuples for rationale.

A section of rationale and example to show how the multiarch tuple and hwcaps complement each other would fix that.
History
Date User Action Args
2015-04-21 13:06:03a.badgersetrecipients: + a.badger, barry, doko, ncoghlan, Arfrever, bkabrda, steve.dower, rkuska
2015-04-21 13:06:03a.badgersetmessageid: <1429621563.36.0.392201083626.issue23966@psf.upfronthosting.co.za>
2015-04-21 13:06:03a.badgerlinkissue23966 messages
2015-04-21 13:06:02a.badgercreate