This is a doc change documenting that option -mtune does not perform any CPU type specific tuning but exists for compatability reasons with GCC.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/docs/ClangCommandLineReference.rst | ||
---|---|---|
2738 | "Accepts any value, for compatibility with GCC. Does not perform any CPU-specific tuning." In email I said:
To me, this patch's wording implies that Clang is promising to keep -mtune as a no-op forever. If Bob puts -mtune=supercalifragilistic in his Makefile today, and then in the future Clang starts emitting an "unknown target" error, will Bob point to this documentation as evidence that Clang promised to accept -mtune=supercalifragilistic as a no-op? So I would rather say: "Accepted for compatibility with GCC. Currently has no effect." |
That wording looks good to me. I've accepted the change, but worth waiting a day or so to see if there are any objections or suggestions.
"Accepts any value, for compatibility with GCC. Does not perform any CPU-specific tuning."
In email I said:
To me, this patch's wording implies that Clang is promising to keep -mtune as a no-op forever. If Bob puts -mtune=supercalifragilistic in his Makefile today, and then in the future Clang starts emitting an "unknown target" error, will Bob point to this documentation as evidence that Clang promised to accept -mtune=supercalifragilistic as a no-op?
So I would rather say:
"Accepted for compatibility with GCC. Currently has no effect."