public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yang Yujie <yangyujie@loongson.cn>
To: Sam James <sam@gentoo.org>
Cc: Yang Yujie <yangyujie@loongson.cn>,
	Jeff Law <jeffreyalaw@gmail.com>,
	 Florian Weimer <fweimer@redhat.com>,
	ro@cebitec.uni-bielefeld.de, mikestump@comcast.net,
	 gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Adjust for the new permerror -Wincompatible-pointer-types
Date: Thu, 7 Dec 2023 09:42:25 +0800	[thread overview]
Message-ID: <ywrdwrbvqbw3x6vycvmbyw3ik27oyuanamfc66rxb4cb4wv5pm@ebs7myjkpczm> (raw)
In-Reply-To: <87ttouhjxl.fsf@gentoo.org>

On Thu, Dec 07, 2023 at 01:35:23AM +0000, Sam James wrote:
> 
> Yang Yujie <yangyujie@loongson.cn> writes:
> 
> > On Wed, Dec 06, 2023 at 10:45:22AM -0700, Jeff Law wrote:
> >> 
> >> 
> >> On 12/6/23 05:12, Florian Weimer wrote:
> >> > * Yang Yujie:
> >> > 
> >> > > From: Yang Yujie <yangyujie@loongson.cn>
> >> > > Subject: [PATCH] testsuite: Adjust for the new permerror
> >> > >   -Wincompatible-pointer-types
> >> > > To: gcc-patches@gcc.gnu.org
> >> > > Cc: ro@CeBiTec.Uni-Bielefeld.DE, mikestump@comcast.net, fweimer@redhat.com,
> >> > >   Yang Yujie <yangyujie@loongson.cn>
> >> > > Date: Wed,  6 Dec 2023 10:29:31 +0800 (9 hours, 42 minutes, 7 seconds ago)
> >> > > Message-ID: <20231206022931.33437-1-yangyujie@loongson.cn>
> >> > > 
> >> > > r14-6037 turned -Wincompatible-pointer-types into a permerror,
> >> > > which causes the following tests to fail.
> >> > > 
> >> > > gcc/testsuite/ChangeLog:
> >> > > 
> >> > > 	* gcc.dg/fixed-point/composite-type.c: replace dg-warning with dg-error.
> >> > > ---
> >> > >   .../gcc.dg/fixed-point/composite-type.c       | 64 +++++++++----------
> >> > >   1 file changed, 32 insertions(+), 32 deletions(-)
> >> > 
> >> > Looks reasonable to me, but I can't approve it.
> >> We might want to fix that from a policy standpoint :-)
> >> 
> >> Regardless, this is OK for the trunk.  Thanks Yang for taking care of it.  I
> >> don't see you in the maintainers file, so I'll go ahead and push it
> >> momentarily.
> >> 
> >> jeff
> >
> > Thanks for the review!
> >
> > With this patch, I also noticed a few errors in building unpatched older
> > software like expect-5.45.4, perl-5.28.3 and bash-5.0.  Will this also be
> > the case when GCC 14 gets released?
> >
> 
> Old versions of software will need to be patched or built with
> -fpermissive. We are working on fixing supported versions of software
> and sending patches upstream - please do join in if you're able, as
> the more help the better.
> 
> It is normal for software to need porting to newer compilers. For
> example, https://gcc.gnu.org/gcc-10/porting_to.html (-fcommon).
> 
> > Thanks,
> > Yujie
> 
> thanks,
> sam

Got it, thanks.

Yujie


  reply	other threads:[~2023-12-07  1:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  2:29 Yang Yujie
2023-12-06 12:12 ` Florian Weimer
2023-12-06 17:45   ` Jeff Law
2023-12-07  1:30     ` Yang Yujie
2023-12-07  1:35       ` Sam James
2023-12-07  1:42         ` Yang Yujie [this message]
2023-12-07  9:18       ` Florian Weimer
2023-12-08  2:00         ` Yang Yujie

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=ywrdwrbvqbw3x6vycvmbyw3ik27oyuanamfc66rxb4cb4wv5pm@ebs7myjkpczm \
    --to=yangyujie@loongson.cn \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=mikestump@comcast.net \
    --cc=ro@cebitec.uni-bielefeld.de \
    --cc=sam@gentoo.org \
    /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).