This the above patch not acceptable for reasons? I'm hitting this and any solution I can think of would be really annoying (ex: set -pgml=my-ld and reorder arguments).
Add Ord to WarningFlag as requested to ease HLS support.
Closes #19087
oops, I didn't see 4690 handles this.
Thomas Main DuBuisson (3209fa48) at 19 Sep 19:31
Fix #19087 Add Ord to WarningFlag
... and 40 more commits
Add Ord to WarningFlag as requested to ease HLS support.
Closes #19087
Thomas Main DuBuisson (2e93aeef) at 19 Sep 19:04
Fix #19087 Add Ord to WarningFlag
Issue #17039 calls out a failure situation which is usually OOM but sometimes an RTS bug. The old error message barfed and said to file a ticket for a GHC bug. This commit changes that message to strongly suggest the issue might be OOM and not immediately link the bug report. This type of messaging and subsequent stg_exit() is consistent with other allocation failures in OSMem.c.
Fixes #17039
Thomas Main DuBuisson (6bffd76e) at 12 Sep 16:28
Update error message to suggest the user consider OOM over RTS bug.
HPC is sort of neglected. I see it has an XML output option but no JSON output option. Most of the world operates on JSON or prefers to as the format is easier to read (as a human), better libraries exist, and sufficient.
Worse, the output format was shortsightedly made as a single flag of --xml-output
instead of a more extensible --output-format <format>
.
We should deprecated the flag, introduce a ne w--output-format
flag and add JSON support. Aeson or similar would make it easy, but I'm not sure where the community stands on adding build dependencies to HPC - are we conservative as with Cabal or more lenient?
@mpickering Do you mean "It seems hard to make progress on this front without ..."? That's what I am, a user with a vision of how it should work, or at least a use case that isn't currently satisfied. Happy to make a PR but the first step is usually an explorative issue to shake loose any objections or conflicting work, so here we are.
HPC is sort of neglected. I see it has an XML output option but no JSON output option. Most of the world operates on JSON or prefers to as the format is easier to read (as a human), better libraries exist, and sufficient.
Worse, the output format was shortsightedly made as a single flag of --xml-output
instead of a more extensible --output-format <format>
.
We should deprecated the flag, introduce a ne w--output-format
flag and add JSON support. Aeson or similar would make it easy, but I'm not sure where the community stands on adding build dependencies to HPC - are we conservative as with Cabal or more lenient?
I see #12935 says:
This is a continuation of #4012 (closed), which was resolved in 8.0.2 by making interface files deterministic
Should we close this ticket?