Hi Damian,
my silencing-a-warning patch is about warnings reported when compiling
GCC itself. — There are also warning for internal/artificially created
variables when compiling code with gfortran. This patch was about the
former and I assume that you are seeing the later.
But, otherwise, I concur that both should eventually be fixed.
Tobias
On 9/29/20 1:25 AM, Damian Rouson wrote:
I've been seeing similar messages to this one for quite some time now -- I
think ~1 year. I don't often use unpack so there are likely many other
causes too. I haven't take the time to isolate them, but if I can do so
easily, I'll submit reports.
Damian
On Mon, Sep 28, 2020 at 2:12 PM Tobias Burnus <tob...@codesourcery.com>
wrote:
There are more warnings, but I picked this one which shows up
with default build options for GCC trunk – twice for each
generated file:
../../../../repos/gcc/libgfortran/generated/unpack_i2.c:128:12: warning:
‘rstride’ may be used uninitialized [-Wmaybe-uninitialized]
../../../../repos/gcc/libgfortran/generated/unpack_i2.c:278:12: warning:
‘rstride’ may be used uninitialized [-Wmaybe-uninitialized]
Hence, 13 times these messages (×2 warnings/file + ×2 with multilib) → 53
'warning:'.
Seemingly, the compiler logic has changes as the previous location
used to be sufficient to silence the compiler.
(The warning is right if base_addr = NULL and dim = 0; the latter should
not occur but the compiler does not know this.)
Committed as obvious as r11-3508-g69c56ce673d1e1d4508e82053a32011f807c6088
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München /
Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung,
Alexander Walter
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander
Walter
