Endianness not detected correctly due to AC_RUN_IFELSE macros

Open
#64,541 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start with the linked pyconfig.h and trace the AC_RUN_IFELSE macros involved in endianness detection, especially in a cross-build. Check the relevant configuration behavior and compare the generated values with the target platform's actual endianness. Done means endianness is detected correctly without relying on an invalid target execution result.

Written by the indexing model from the issue text.

Description

build interpreter-core type-bug
BPO 20342
Nosy @doko42, @gpshead, @mdickinson, @vstinner, @moreati
Files
  • pyconfig.h
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2014-01-22.08:44:31.459>
labels = ['interpreter-core', 'type-bug', 'build']
title = 'Endianness not detected correctly due to AC_RUN_IFELSE macros'
updated_at = <Date 2022-02-07.08:51:47.053>
user = 'https://bugs.python.org/zaytsev'

    bugs.python.org fields:

    activity = <Date 2022-02-07.08:51:47.053>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Cross-Build']
creation = <Date 2014-01-22.08:44:31.459>
creator = 'zaytsev'
dependencies = []
files = ['33613']
hgrepos = []
issue_num = 20342
keywords = []
message_count = 8.0
messages = ['208760', '208765', '208772', '208780', '208786', '412719', '412720', '412723']
nosy_count = 6.0
nosy_names = ['doko', 'gregory.p.smith', 'mark.dickinson', 'vstinner', 'zaytsev', 'Alex.Willmer']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20342'
versions = ['Python 3.4']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.