This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Annoying silly warning emitted by gcc?
- From: Warren D Smith <warren dot wds at gmail dot com>
- To: Joe Buck <joe dot buck at synopsys dot com>
- Cc: Andrew Pinski <pinskia at gmail dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Wed, 23 Jan 2019 21:05:15 -0500
- Subject: Re: Annoying silly warning emitted by gcc?
- References: <CAAJP7Y1Dc0DWBO7UsTcYxjsofx9a8zQOtKFc=UhvY2Ck5h3GmA@mail.gmail.com> <CA+=Sn1mSjOW7TpJ1UpcQj+DxdqcFA19-0iCefWOa3QcA7gwLBQ@mail.gmail.com> <CCD865889A560649BA947E1B934A8D7D023F73536A@US01WEMBX2.internal.synopsys.com>
The x=x "initialization" idea by paulkoning@comcast.net
failed to turn off the warning for me.
Joe Buck may be right that gcc "already does the right thing"
but actually I was dealing with not a 64-bit wide, but
actually a 128-bit-wide type, which might
later become 256-wide or even 512; and to load it with 0s actually needs a lot
of loading of constants from the instruction stream.
--
Warren D. Smith
http://RangeVoting.org <-- add your endorsement (by clicking
"endorse" as 1st step)