Compiler warnings with GCC 11.1.0

[Blazefrost]

Compiler warnings with GCC 11.1.0

[ckirsch]

@Blazefrost I am surprised it only warns there. Do you have any idea how to avoid that warning?

[Blazefrost]

GCC seems to apply an optimization, as indicated by the .constprop function suffix. I don't know whether an older GCC version already performed this optimization, but I assume the GCC team either improved the optimizer or the analyzer, or both.

The function string_copy is called five times:

• selfie/selfie.c

  Line 5599 in cfb6619

  entry = search_global_symbol_table(string_copy("_bump"), VARIABLE);

• selfie/selfie.c

  Line 5637 in cfb6619

  entry = get_scoped_symbol_table_entry(string_copy("main"), PROCEDURE);

• selfie/selfie.c

  Line 5719 in cfb6619

  create_symbol_table_entry(GLOBAL_TABLE, string_copy("main"), 0, PROCEDURE, UINT64_T, 0, 0);

• selfie/selfie.c

  Line 7258 in cfb6619

  create_symbol_table_entry(GLOBAL_TABLE, string_copy("_bump"), 1, VARIABLE, UINT64_T, 0, -data_size);

• selfie/selfie.c

  Line 7263 in cfb6619

  entry = search_global_symbol_table(string_copy("_bump"), VARIABLE);

So the function is only called with "main" and "_bump" strings which seems to match with the error messages (char[5] and char[6], including the string terminator), and indeed, the function referenced by the warning messages,load_character, casts and dereferences these strings as uint64_t, even though the memory the pointer points to is smaller than an uint64_t.

An easy workaround for now would be to just disable the warning using -Wno-array-bounds

[ckirsch]

@Blazefrost I just committed a fix: 6c31681...fb7c254 Could you please check if that avoids the warnings?

[Blazefrost]

Yes, commit fb7c254 fixed the warnings for me. 👍