From: Alan Modra <amodra@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: Nick Clifton <nickc@redhat.com>,
gcc-patches@gcc.gnu.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: RFC: Changing AC_PROG_CC to AC_PROG_CC_C99 in top level configure
Date: Wed, 5 May 2021 16:50:52 +0930 [thread overview]
Message-ID: <20210505072052.GA14297@bubble.grove.modra.org> (raw)
In-Reply-To: <CAB3F184-BD38-4E3E-8988-BF5C855C401B@googlemail.com>
On Wed, May 05, 2021 at 08:05:29AM +0100, Iain Sandoe wrote:
> Alan Modra via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> > On 2021-05-04 8:42 a.m., Nick Clifton wrote:
> > > Hi Guys,
> > >
> > > On 4/30/21 7:36 PM, Simon Marchi wrote:
> > > > I think this fix is obvious enough, I encourage you to push it,
> > >
> > > OK - I have pushed the patch to the mainline branches of both
> > > the gcc and binutils-gdb repositories.
> >
> > Thanks Nick! Incidentally, I checked the AC_PROG_CC_C99 change on
> > both binutils and gcc mainline using gcc-4.9.
> >
> > To build gcc on x86_64 I found the following patch necessary to avoid
> > lots of
> > error: uninitialized const member ‘stringop_algs::stringop_strategy::max’
> > error: uninitialized const member ‘stringop_algs::stringop_strategy::alg’
> > when compiling config/i386/i386-options.c. These can't be cured by
> > configuring with --disable-stage1-checking.
> >
> > diff --git a/gcc/config/i386/i386.h b/gcc/config/i386/i386.h
> > index 97d6f3863cb..cc3b1b6d666 100644
> > --- a/gcc/config/i386/i386.h
> > +++ b/gcc/config/i386/i386.h
> > @@ -73,8 +73,8 @@ struct stringop_algs
> > {
> > const enum stringop_alg unknown_size;
> > const struct stringop_strategy {
> > - const int max;
> > - const enum stringop_alg alg;
> > + int max;
> > + enum stringop_alg alg;
> > int noalign;
> > } size [MAX_STRINGOP_ALGS];
> > };
>
> does this relate to / fix PR 100246 (which seems to fire for some GCC
> versions as well
> as older clang)?
Yes, looks like the same issue. I started making a similar fix to the
one you attached to the PR, then laziness kicked in after noticing the
errors were only given on the const elements.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2021-05-05 7:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:32 Nick Clifton
2021-04-26 19:32 ` Joseph Myers
2021-04-26 20:05 ` Mike Frysinger
2021-04-26 21:31 ` Christian Biesinger
2021-04-27 10:49 ` Nick Clifton
2021-04-27 16:58 ` Joseph Myers
2021-04-30 18:36 ` Simon Marchi
2021-04-30 21:48 ` Jeff Law
2021-05-03 6:28 ` Alan Modra
2021-05-03 14:47 ` Simon Marchi
2021-05-03 16:26 ` Tom Tromey
2021-05-03 21:51 ` Alan Modra
2021-05-03 23:30 ` Simon Marchi
2021-05-04 12:42 ` Nick Clifton
2021-05-04 15:16 ` Simon Marchi
2021-05-05 0:18 ` Alan Modra
2021-05-05 7:05 ` Iain Sandoe
2021-05-05 7:20 ` Alan Modra [this message]
2021-05-05 7:23 ` Iain Sandoe
2021-05-10 8:49 ` Iain Sandoe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210505072052.GA14297@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=idsandoe@googlemail.com \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).