Hi Paul,

Thanks for letting us know. There's currently a patch on our review site
that solves the implicit fallthrough problem (
https://gem5-review.googlesource.com/c/public/gem5/+/8541). I haven't seen
the uninitialized warning, though.


Jason Lowe-Power
Assistant Professor, Computer Science Department
University of California, Davis
3049 Kemper Hall

On Thu, Feb 22, 2018 at 5:56 AM Paul V. Gratz <pgr...@gratz1.com> wrote:

> Hi All,
> I just did a clean clone of the latest github on my Ubuntu 17.10 system
> (gcc 7.2.0).  In this setup builds fail due to two warnings (because
> -Werror is on in the build scripts).
> First in decode-method.cc.inc there are some case statements that have
> fallthrough conditions.  To get around this I added:
> main.Append(CXXFLAGS=['-Wno-implicit-fallthrough'])
> to the SConstruct file (is this the right way to do this?).
> Second, in neon64_mem.hh there are some potentially uninitialized
> variables.  To get around this I added maybe-uninitialized to the CCFLAGS:
>    main.Append(CCFLAGS=['-Werror',
>                         '-Wno-error=deprecated-declarations',
>                         '-Wno-error=deprecated',
>                         '-Wno-error=maybe-uninitialized',
>                        ])
> After this the build completes cleanly.  Probably those warnings should be
> fixed in the source code directly but I am not yet well versed enough in
> how gem5 works to do that yet.  I'm guessing that these warnings are new
> with my gcc version is why I don't see anyone posting on here about them
> yet..
> Paul
> --
> -----------------------------------------
> Paul V. Gratz
> Associate Professor
> ECE Dept, Texas A&M University
> Office: 333M WERC
> Phone: 979-488-4551 <(979)%20488-4551>
> http://cesg.tamu.edu/faculty/paul-gratz/
> _______________________________________________
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
gem5-users mailing list

Reply via email to