Skip to content

Conversation

jimbxb
Copy link
Collaborator

@jimbxb jimbxb commented Apr 20, 2025

Closes #477
Closes #478

Copy link
Owner

@pschachte pschachte left a comment

Choose a reason for hiding this comment

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

This looks fine, so I'll pull it, despite the problem with the CI system you reported.

@pschachte pschachte merged commit 9c2c83e into pschachte:master Apr 24, 2025
1 check failed
@jimbxb jimbxb deleted the jb/qol-options branch April 24, 2025 01:23
@pschachte
Copy link
Owner

BTW, I don't think logging to /var/log is a good idea, given the intent of /var/log and the purpose of wybemk logging. The former is intended for logging aspects of the normal execution of system programs, while the latter is intended for debugging the compiler. I don't know of any other compilers that log to /var/log.

@jimbxb
Copy link
Collaborator Author

jimbxb commented Apr 24, 2025

That's probably right.

The main intent of the log file flag was because I'd often find myself routing the logs to a file and analysing that. Scrolling through stderr in the terminal isn't fun, and can slow down the terminal considerably when the verbose loggers are turned on.

@pschachte
Copy link
Owner

Yep. I always write the log to a file. You've probably seen me accidentally commit a file called LOG to the repo, and then have to delete it later.

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.

Route logs to a specified file. Add compiler flag to control path of llc binary
2 participants