https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126123
Drea Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Target Milestone|--- |17.0
Last reconfirmed| |2026-07-06
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Drea Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Avinash Jayakar from comment #1)
> I think the Darwin's assembler has to be updated to recognize the EH
> parameter.
It is frozen in time. Sorry. The normal way this is handled is adding a
configure test to test if EH parameter is accepted or not. See
r17-2093-g97d9016b230cca98a for one example of doing this but for aarch64.
Or even this:
case $target in
*-*-aix*) conftest_s=' .machine "pwr5"
.csect .text[[PR]]
mfcr 3,128';;
*-*-darwin*) conftest_s=' .text
mfcr r3,128';;
*) conftest_s=' .machine power4
.text
mfcr 3,128';;
esac
gcc_GAS_CHECK_FEATURE([mfcr field support],
gcc_cv_as_powerpc_mfcrf,,
[$conftest_s],,
[AC_DEFINE(HAVE_AS_MFCRF, 1,
[Define if your assembler supports mfcr field.])])
Or the others.
