Skip to content

Conversation

@vitalybuka
Copy link
Collaborator

@vitalybuka vitalybuka commented Oct 14, 2024

I find multiline 'RUN:' statements hard to read.

*\\\n; RUN: * -> for ./llvm/test/Instrumentation/

Created using spr 1.3.4
@fmayer
Copy link
Contributor

fmayer commented Oct 15, 2024

I generally prefer the wrapped lines but if you feel strongly go ahead.

@vitalybuka
Copy link
Collaborator Author

vitalybuka commented Oct 15, 2024

I generally prefer the wrapped lines but if you feel strongly go ahead.

Yes, I'd like to do so very much.
Most common info I look in these lines are difference in compiler options between them. And it's much easier to see if they are semi-aligned. The tail with FileCheck is usually irrelevant.

Bug if it's needed there is wrap on/off in most editors.

I need to think hard to difference in the first one, and it's obvious in the second.

image
image

@fmayer
Copy link
Contributor

fmayer commented Oct 15, 2024

Wouldn't that make one per line better for diffing? That's what I generally do for long command lines to read / diff them.

Copy link
Contributor

@fmayer fmayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I don't feel strongly.

@vitalybuka vitalybuka merged commit fe7f5f9 into main Oct 15, 2024
9 checks passed
@vitalybuka vitalybuka deleted the users/vitalybuka/spr/nfcintrumentation-dont-brake-long-run-lines branch October 15, 2024 17:45
DanielCChen pushed a commit to DanielCChen/llvm-project that referenced this pull request Oct 16, 2024
I find multiline 'RUN:' statements hard to read.

` *\\\n; RUN: *` -> ` ` for  ./llvm/test/Instrumentation/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants