Only these two unused variables left, then it's perfect.
Colin Finck <colin@reactos.org>
Differential D96408
Fix warnings when compiling libcxx for Windows with clang-cl /W4 ColinFinck on Feb 10 2021, 4:37 AM. Authored by
Details
Only these two unused variables left, then it's perfect. Colin Finck <colin@reactos.org>
Diff Detail
Event TimelineComment Actions Hmm, when I build libcxx with clang-cl, the build is extremely noisy, with around 100 warnings per source file. These mostly come from -Wall which the build system adds, warning for things in the libcxx headers (which the compiler doesn't consider to be system headers at that point and doesn't mute warnings for). What's your build setup like, do you manage to avoid getting -Wall added, or is it ignoring things in the headers in your case? Comment Actions I'm also getting a very noisy build with -Wall, but here I'm using /W4 (building libc++ in a custom Visual Studio project file). Comment Actions What is blocking this? Comment Actions Just the review throughput and the fact that some reviews get forgotten. Next time you may ping earlier of you see no activity.
Comment Actions FWIW, when building with CMake, we already do try to add -Wno-unused-parameter (which ends up applied also when building with clang-cl), so in that sense these shouldn't be needed when building in such configurations. But if we have a precedent for silencing this kind of unused parameters like this too (which is quite harmless anyway), for silencing them when building libcxx via other custom build systems, then that's certainly good too. Comment Actions Yes. You can see members of the libc++ review group here: https://reviews.llvm.org/project/members/64/ |
The comment on line 123 becomes misleading. Here I suggest following line 86's style:
IMO there should also be one blank line before this function, and one blank line after.