Re: Glob to match bare-metal SuperH target triple in config.gcc seems wrong (sh*-superh-elf)?
Project / Subsystem
gcc / gcc
Date
2026-04-18
Proposer
Oleg Endo <[email protected]>
Source type
public_inbox
Consensus
Proposed
Sentiment
5/10
Technical tradeoffs
- • Changing the glob may break existing configurations.
- • Leaving it as-is may cause confusion and incorrect target matching.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- [email protected]
- source_type
- public_inbox
- title
- Re: Glob to match bare-metal SuperH target triple in config.gcc seems wrong (sh*-superh-elf)?
- headline
- Glob to match bare-metal SuperH target triple in config.gcc seems wrong
- tldr
- The glob "sh*-superh-elf" in config.gcc may incorrectly identify SuperH bare-metal targets.
- stakes
- Incorrect target triples can lead to build configuration errors.
- proposer
- Oleg Endo <[email protected]>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- 5
- sentiment_rationale
- Discussion is neutral, exploring potential issues with a configuration glob.
- technical_tradeoffs
-
- • Changing the glob may break existing configurations.
- • Leaving it as-is may cause confusion and incorrect target matching.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • configuration
- • target triple
- • SuperH
- bugzilla_url
- —
- date
- 2026-04-18T00:00:00.000Z
Re: Glob to match bare-metal SuperH target triple in config.gcc seems wrong (sh*-superh-elf)?
A discussion arose about the glob expression “sh*-superh-elf” used in config.gcc to match embedded SuperH targets. The concern is that the “superh” token, which appears to be a manufacturer name, might be causing the glob to miss some valid target triples like “sh-elf”. The discussion suggests that the expression is confusing and could benefit from clarification.