Remove heading/trailing white spaces when matching OMP_TARGET_OFFLOAD
value.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Some options have their own logic to skip white spaces, but not all option values are handled like that.
So, your question is why we don't do this for other options?
Comment Actions
@jdoerfert , to reiterate what @hbae said, the trimming functionality is there for almost all (if not all) the environment variable parsing routines. It's seen mostly with the SKIP_WS() macro and manual manipulations of char* next, scan. The kmp_trimmed_str_t is supposed to just make it a bit simpler, especially for the case of a one-token environment variable. Is it the way the trimming is performed that you don't like?
Comment Actions
typo: spcaes
LG, all I tried to say is that we should be consistent across env vars. Accepting whitespaces around stuff is probably the right choice.