Displaying 3 results from an estimated 3 matches for "r23921".
Did you mean:
r239821
2020 Nov 10
1
unusual use of getenv
...ile where this trick
> is used "LinkAllPasses.h" should give a hint what it is used for.
> Looking into the entire history of the file, I have no idea how one
> would have concluded this whas a Windows thing. It first occurred in
> 1c5b428ff8234cef705bf57bc1418deb4db25c83 (SVN r23921) when Windows
> support was not yet a thing.
I concluded this was a windows thing because the origin of the code
seems to be in 00d5508496c1ec0540da5714b0ed66e64b623df5 which uses the
windows only `GetCurrentProcess` instead of `getenv`. Chris Lattner then
changed it to use `getenv` in 63e504ff...
2020 Nov 10
0
unusual use of getenv
...6. The name of the file where this trick
is used "LinkAllPasses.h" should give a hint what it is used for.
Looking into the entire history of the file, I have no idea how one
would have concluded this whas a Windows thing. It first occurred in
1c5b428ff8234cef705bf57bc1418deb4db25c83 (SVN r23921) when Windows
support was not yet a thing.
LLVM tools themselves, like opt, call some function for each LLVM
component directly (such as initializeCore()) to achieve the same
thing. Howwer clang does include LinkAllPasses.h (in cc1_main.cpp).
All that matters is that there is a strong reference to...
2020 Nov 02
4
unusual use of getenv
Oh, right, this stuff. I guess the non-windows solution might've been a
volatile read, for instance? So maybe not so much that the general
machinery isn't needed, but that perhaps MSVC does something interesting
with a volatile read or whatever other solution might've been used.
Hmm, not sure why the whole file was added only when MSVC support was added
- if it is a "static