On 9/8/22 11:29, Chung-Lin Tang wrote:
Hi Joseph,
Jan-Benedict reported a build-bot error for the nios2 port under
--enable-werror-always:
options-save.cc: In function 'bool cl_target_option_eq(const cl_target_option*,
const cl_target_option*)':
options-save.cc:9291:38: error: comparison between two arrays
[-Werror=array-compare]
9291 | if (ptr1->saved_custom_code_status != ptr2->saved_custom_code_status
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
options-save.cc:9291:38: note: use unary '+' which decays operands to pointers or
'&'component_ref' not supported by dump_decl<declaration error>[0] !=
&'component_ref' not supported by dump_decl<declaration error>[0]' to compare the
addresses
options-save.cc:9294:37: error: comparison between two arrays
[-Werror=array-compare]
9294 | if (ptr1->saved_custom_code_index != ptr2->saved_custom_code_index
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...
This is due to an array-typed TargetSave state in config/nios2/nios2.opt:
...
TargetSave
enum nios2_ccs_code saved_custom_code_status[256]
TargetSave
int saved_custom_code_index[256]
...
This patch adjusts the generated array state compare from 'ptr1->array' into
'&ptr1->array[0]' in gcc/optc-save-gen.awk,
seems sufficient to pass the tougher checks.
Tested by ensuring the compiler builds, which should be sufficient here.
Okay to commit to mainline?
Martin added the array support in r219636, any thoughts?
It seems to me that the warning is pointing out that comparing the
address of the array is nonsensical, and we should remove it and just
have the memcmp.
Thanks,
Chung-Lin
* optc-save-gen.awk: Adjust array compare to use '&ptr->name[0]'
instead of 'ptr->name'.
