[dpwiz]

For #6197, following https://well-typed.com/blog/2023/03/prof-late/

• Any changes that could be relevant to users have been recorded in ChangeLog.md.
• The documentation has been updated, if necessary
  • The change seems to "do the right thing" without bothering users with details. The profiling just works better.

[mpilgrem]

@dpwiz, thanks for the contribution. Sorry for the delay, I needed to read up on the topic. Swapping -fprof-late for -fprof-auto seems sensible (and there is always -fno-prof-late, if a Stack user does not agree). I think the change in behaviour provides an opportunity for improved Stack documentation; I can add that.

A small thing, but I am not sure ghcSupportsProfLate is best placed in Stack.Constants. There are some exceptions, but that module exports mostly close to named literals. I may move it closer to the action.

Also, it seemed to me that it was rather a case of:

-- The strategy recommended by the GHC User's Guide for the
-- automatic insertion of cost centres for profiling:
recommendedProfStrategy :: Version -> String
recommendedProfStrategy ghcVersion
  | ghcVersion >= mkVersion [9, 4, 1] = "-fprof-late"
  | otherwise = "-fprof-auto"

[mpilgrem]

I've rebased on the master branch.

[mpilgrem]

I think a simpler approach can be taken to Cabal's --profiling-detail=none. I've added a commit and the code comment in it explains my reasoning.

EDIT: That allows for simplification elsewhere, which I have reflected in a second commit.

[mpilgrem]

I've framed the change log entry in terms of Stack catching up with the GHC User's Guide's recommendation (that is, this could be viewed as a sort of 'bug fix').