Pushed, thanks for feedback
On 2/26/23 11:54 PM, Tobias Burnus wrote:
Just side remarks, the 0 init in the patch is fine.
On 27.02.23 03:53, Jerry D via Gcc-patches wrote:
regarding PACK: since this is a bogus warning as the compiler does
not realize that dim >= 1, wouldn't a
gcc_assert (dim
Just side remarks, the 0 init in the patch is fine.
On 27.02.23 03:53, Jerry D via Gcc-patches wrote:
regarding PACK: since this is a bogus warning as the compiler does
not realize that dim >= 1, wouldn't a
gcc_assert (dim >= 1);
Note: gcc_assert only exists in the compiler itself; in libgfo
Hi Jerry,
I should have clarified in my posts that the warnings are on the use of
sstride[0], mstride[0] or both.
In a sense it is a
regression. It showed up when builds started to use -Wmaybe-unitialized.
I think this is OK for trunk now, and backport for up to whenever
-Wmaybe-uninitial
On 2/26/23 12:59 PM, Harald Anlauf wrote:
Hi Jerry,
regarding PACK: since this is a bogus warning as the compiler does
not realize that dim >= 1, wouldn't a
gcc_assert (dim >= 1);
in the right place achieve the same effect, since the first argument
must be an array?
(It's different for SPREAD
Hi Jerry,
regarding PACK: since this is a bogus warning as the compiler does
not realize that dim >= 1, wouldn't a
gcc_assert (dim >= 1);
in the right place achieve the same effect, since the first argument
must be an array?
(It's different for SPREAD, though, where SOURCE may be scalar).
Che
