554526 – New use expand: CPU_FLAGS_ARM

Bug 554526 - New use expand: CPU_FLAGS_ARM

Summary: New use expand: CPU_FLAGS_ARM

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Eclasses (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo ARM Porters

URL:
Whiteboard:
Keywords:

Duplicates (1):	602724 (view as bug list)
Depends on:
Blocks:

Reported:	2015-07-11 17:31 UTC by Manuel Rüger (RETIRED)
Modified:	2019-09-11 18:17 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Manuel Rüger (RETIRED) gentoo-dev

2015-07-11 17:31:28 UTC

We should adopt the pattern from CPU_FLAGS_X86 and use them for ~arm.

Initial set could be:
CPU_FLAGS_ARM="armv4 armv5 armv5te armv6 armv6t2 armv7 armv8 armvfp neon"

This would avoid confusions with useflags enabling net-libs/neon.

Comment 1 Michał Górny archtester

2017-03-03 22:32:28 UTC

So, FWICS:

a. USE=neon is used by quite a few packages,

b. USE=armv7 is used by games-board/stockfish,

c. other USE=armv* are used by ffmpeg&libav.

However, the real used set is smaller than the one listed on the bug. Was the original request wider than used, or did support for e.g. armv4 get removed? If the former, what are the criteria for choosing which ARM versions to include and which are to be skipped?

Comment 2 SpanKY gentoo-dev

2017-03-06 23:06:22 UTC

none of the armv# flags should be global or used by packages.  those are the same thing as -march=armv# and packages should use that instead if they really want to do something.

neon makes sense as a CPU flag.

Comment 3 SpanKY gentoo-dev

2017-03-06 23:06:39 UTC

*** Bug 602724 has been marked as a duplicate of this bug. ***

Comment 4 Michał Górny archtester

2019-09-11 18:17:47 UTC

This was committed already.