EXTRA_HC_OPTS workflow under hadrian.

This allows passing of arbitrary flags to ghc from the command line.

The main use case for me so far is to generate dumps for an arbitrary combination of dump flags.

Sometimes I wanted to look at the simplifier output for a certain file.

Sometimes I wanted to dump the asm code for all files to see how common certain patterns are. Sometimes the same for Cmm. Sometimes I want to dump two passes to be able to cross reference between them.

These are usually on-off things and the exact flags often differ. So imo custom build profiles are not a good solution for this.

Trac metadata

Trac field	Value
Version	8.6.3
Type	FeatureRequest
TypeOfFailure	OtherFailure
Priority	normal
Resolution	Unresolved
Component	Build System (Hadrian)
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture

changed weight to 5

added Tfeature request Trac import hadrian labels

This wouldn't be too difficult to implement, perhaps you could give it a shot yourself?

For now I'm sticking with make (not just for this reason). Maybe once the cost/benefit tradeoff for that decision changes.

Hmm, isn't this supported out of the box with the args field of Flavour? https://gitlab.haskell.org/ghc/ghc/blob/master/hadrian/doc/user-settings.md#command-line-arguments

@AndreasK Maybe this is what you refer to with "custom build profiles", but if that's the case, could you let us know why this is not a good enough solution?

@alp Personally I consider the requirement to edit a file for one-off tasks like getting core dumps for stage2 files a step back.

It's good that it's possible through editing the Flavour. But it's still slightly more annoying than doing the same with make currently.

mentioned in issue #16769 (closed)

@AndreasK In order to address this and other related Hadrian "UX issues", I opened #16769 (closed). Feedback appreciated.

added Pnormal label

changed milestone to %Make removal

I believe this use-case should be addressed by #16769 (closed).

closed