Change Details

On the fallback path, we hardcode the X_ prefix to the compiler info variables. Since the only non-CC in _cc_vars is XCC this works for us at the moment, but potentially breaks for anyone adding another compiler type to _cc_vars, clobbering the wrong variables and leaving the correct variables unset. Instead we should be more general and use the X_ variable's contents as the prefix.

On the fallback path, we hardcode the X_ prefix to the info variables. Since the only prefixed tool in _cc_vars/_ld_vars is XCC/XLD this works for us at the moment, but potentially breaks for anyone adding another tool type to _cc_vars/_ld_vars, clobbering the wrong variables and leaving the correct variables unset. Instead we should be more general and use the X_ variable's contents as the prefix.

On the fallback path, we hardcode the X_ prefix to the compiler infoinfo variables. variables. Since the only non-CCprefixed tool in _cc_vars/_ld_vars is XCC/XLD this works for us ats for us at the moment, but potentially breaks for anyone adding another compiler ttool type to _cc_vars/_ld_vars, clobbering the wrong variables and leaving the correct leaving the correct variables unset. Instead we should be more general and use the X_ and use the X_ variable's contents as the prefix.