-
Notifications
You must be signed in to change notification settings - Fork 4
Comparing changes
Open a pull request
base repository: m-labs/flickernoise
base: e90101d
head repository: m-labs/flickernoise
compare: 64369d9
- 9 commits
- 17 files changed
- 1 contributor
Commits on Jan 13, 2012
-
parser: add newline after warnings in warn()
... instead of making it part of the warning message.
Configuration menu - View commit details
-
Copy full SHA for 5cc5c8b - Browse repository at this point
Copy the full SHA 5cc5c8bView commit details -
compiler: remove "FPVM, " prefix from error messages
First, this saves precious space for more interesting information. Second, the compiler isn't part of libfpvm anymore, making that prefix a little cryptic.
Configuration menu - View commit details
-
Copy full SHA for 361ab20 - Browse repository at this point
Copy the full SHA 361ab20View commit details -
compiler: when in Flickernoise, make warnings return an error string
I.e., warnings become errors.
Configuration menu - View commit details
-
Copy full SHA for 57792ea - Browse repository at this point
Copy the full SHA 57792eaView commit details -
compiler: make current assignment target part of the compiler state
... instead of tweaking the functions passed by the caller.
Configuration menu - View commit details
-
Copy full SHA for 35a9373 - Browse repository at this point
Copy the full SHA 35a9373View commit details -
compiler: parse() returns success instead of message; pass message in…
… "comm" This way, the caller can decide what to do. Current behaviour is that warnings don't keep us from proceeding, but they're shown in the patch editor. This means that the patch will run but when returning to the patch editor, the warning is shown. Improve this later.
Configuration menu - View commit details
-
Copy full SHA for e057e27 - Browse repository at this point
Copy the full SHA e057e27View commit details -
compiler: prioritize diagnostics so that errors can override warnings
Before, a warning preceding an error would cause the warning message to be shown, not the error message. This only applies to use in Flickernoise. In ptest, warnings don't compete with errors.
Configuration menu - View commit details
-
Copy full SHA for 47718fa - Browse repository at this point
Copy the full SHA 47718faView commit details
Commits on Jan 14, 2012
-
compiler: further cleanup and debugging of diagostic mechanism
This commit contains the following changes: - call diagnostics that can be errors or warnings just "msg", not "error", - errors now have priority over warnings, - streamlined the diagnostic passing a little.
Configuration menu - View commit details
-
Copy full SHA for d886b04 - Browse repository at this point
Copy the full SHA d886b04View commit details -
comment out equations using *_residual in "Unchained - A Matter Of Ta…
…ste" We have no known source for these values, so we may as well let things default to zero. This also makes the patch -Wundefined-clean.
Configuration menu - View commit details
-
Copy full SHA for 4ac760f - Browse repository at this point
Copy the full SHA 4ac760fView commit details -
compiler: enable warnings in Flickernoise and test/patches
Also moved the global variables controlling variables from parser.y to parser_helper.c, consistent with their declaration in parser_helper.h ptest turns off the warnings by default and only enables them if explicitly requested.
Configuration menu - View commit details
-
Copy full SHA for 64369d9 - Browse repository at this point
Copy the full SHA 64369d9View commit details
There are no files selected for viewing