torproject / tor Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre formatter cleanups #1610
Closed
Closed
Pre formatter cleanups #1610
Conversation
This is an automated commit, generated by: perl -i -pe 'next if /define/; s/((?:ENABLE|DISABLE)_GCC_WARNING)\(([A-Za-z0-9_\-]+)\)/$1(\"-W$2\")/' src/*/*/*.[ch] src/*/*.[ch]
We were actually omitting the semicolon in a few places, leading to confusing indentation and some cocci failures.
Also, include torerr.h from ht.h if we are using raw_assert. Otherwise, our includes need to be ordered so that ht.h comes after util_log.h.
Otherwise our compilation depends on include order.
This gives us the definition of tor_x509_cert_impl_t, and makes us less dependent on include order.
This frees us from some dependencies on include order.
This frees us from a dependency on include order.
Doing this gives us a valid uint64_t type, freeing us from dependencies on include order.
Using these frees us from several dependencies on include order.
Doing this frees us from some assumptions about include order.
This frees us from some dependencies on include order.
This frees us from some dependencies on include order.
This lets us avoid a dependency on include order.
Without this include, our compilation depends more on include order.
This fixes a case where our compilation would depend on include order.
This prevents a dependency on include order.
Without this change, compilation success depends on include order in several tricky ways.
This change means that authmode.h no longer needs to see or_options_t, and frees us from an ordering dependency.
This frees us from a dependency on include order.
We use bool, so we should include stdbool.
Pull Request Test Coverage Report for Build 7581
|
tlyu
reviewed
Dec 16, 2019
src/lib/cc/compat_compiler.h
Outdated
| # define ENABLE_GCC_WARNING(warningopt) \ | ||
| PRAGMA_DIAGNOSTIC_(pop) | ||
| #else /* !(defined(__clang__) || GCC_VERSION >= 406) */ | ||
| /* older version of gcc: no push/pop support. */ | ||
| # define DISABLE_GCC_WARNING(warningopt) \ | ||
| PRAGMA_DIAGNOSTIC_(ignored PRAGMA_JOIN_STRINGIFY_(-W,warningopt)) | ||
| PRAGMA_DIAGNOSTIC_(ignored PRAGMA_JOIN_STRINGIFY_ warningopt) |
Should probably completely delete PRAGMA_JOIN_STRINGIFY_ as was done on L73. Same on L81.
Preprocessor substitution of empty token for undefined macros probably makes this compile, but we probably shouldn't leave it lying around.
…nfuse clang-format less Remove remaining uses of PRAGMA_JOIN_STRINGIFY_: these should have gone away entirely. Caught by Taylor.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
No description provided.
The text was updated successfully, but these errors were encountered: