Fix: add gcc -Og check and fix its false positive warnings #814

Merged

t-mat merged 2 commits from dev into dev

2023-03-09 11:12:53 -06:00

t-mat commented

2023-03-06 08:50:31 -06:00

(Migrated from github.com)

Before adding gcc-12 and -Og test to our CI, I'd like to fix gcc -Og issue.
See also #810

Actually, this is a false positve of gcc -Og. So there must be another ways to avoid this warning.
But since it seems there's easy / safe / explicit fix for it with negilible const, I'd like to it to XXH3_INITSTATE().
( See advice https://github.com/Cyan4973/xxHash/issues/810#issuecomment-1455245974 from @easyaspi314 )

Before adding `gcc-12` and `-Og` test to our CI, I'd like to fix `gcc -Og` issue. See also #810 Actually, this is a false positve of `gcc -Og`. So there must be another ways to avoid this warning. But since it seems there's easy / safe / explicit fix for it with negilible const, I'd like to it to `XXH3_INITSTATE()`. ( See advice https://github.com/Cyan4973/xxHash/issues/810#issuecomment-1455245974 from @easyaspi314 )

t-mat commented

2023-03-07 16:22:15 -06:00

(Migrated from github.com)

note: Test badge shows red ❌ , but it actually means "some tests are skipped". #817 fixes this issue.

Cyan4973 (Migrated from github.com) approved these changes

2023-03-08 17:34:50 -06:00

No reviewers

Cyan4973

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Cyan4973/xxHash!814

No description provided.

Rows
Columns