From: Andrew MacLeod <amacleod@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix a few incorrect accesses.
Date: Wed, 7 Dec 2022 09:58:51 -0500 [thread overview]
Message-ID: <af9d8786-3f36-258c-183c-9e34072559d2@redhat.com> (raw)
In-Reply-To: <87359r34rb.fsf@euler.schwinge.homeip.net>
On 12/7/22 05:08, Thomas Schwinge wrote:
> Hi Andrew!
>
> On 2022-12-02T09:12:23-0500, Andrew MacLeod via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> This consists of 3 changes which stronger type checking has indicated
>> are non-compliant with the type field.
> I'm curious what that "stronger type checking" is?
>
Remnants of an old project which replaces the uses of trees to represent
types everywhere in GCC with a new type pointer. This provided much
stronger compile time type checking. These few places in the patch
caused compile time errors because the accesses were not type nodes.
They were hanging around in an old branch from 2017 I was looking at, so
I figured it was time to get them into trunk :-)
Anddrew
prev parent reply other threads:[~2022-12-07 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:12 Andrew MacLeod
2022-12-02 14:52 ` Richard Biener
2022-12-02 17:02 ` Andrew MacLeod
2022-12-07 10:08 ` Thomas Schwinge
2022-12-07 14:58 ` Andrew MacLeod [this message]
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=af9d8786-3f36-258c-183c-9e34072559d2@redhat.com \
--to=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.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).