https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118133
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktkachov at gcc dot gnu.org
--- Comment #1 from ktkachov at gcc dot gnu.org ---
I agree with the need to find a new scheme for these .def files.
This reminds me a bit of the days in the arm backend when we used ML scripts to
generate the arm_neon.h header...
I'm a bit hesitant about M4. I know there are many .m4 files in the GCC source
so it's somewhat established, but I also feel those files are rarely touched in
normal development.
But for frequently-extended intrinsics definitions it feels like Python is a
more accessible syntax to most developers that work on the AArch64 backend
these days.
So I'd like to explore whether we could do this in Python instead.
Would it be acceptable to require Python to modify GCC but not to just build
the sources, if we commit the generated file in the repo, like you say?
