Re: Gcc Digest, Vol 15, Issue 5

Re: Gcc Digest, Vol 15, Issue 5

[Gary Oblock]

I've got to say appearances can be deceptive
in GCC and struct _modif_basket *[4061] is not
necessarily equal to struct _modif_basket *[4061]
even though the printed representation is
the same...

Gary
________________________________
From: Gcc <gcc-bounces@gcc.gnu.org> on behalf of gcc-request@gcc.gnu.org <gcc-request@gcc.gnu.org>
Sent: Tuesday, May 4, 2021 1:48 PM
To: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Gcc Digest, Vol 15, Issue 5

[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]


Send Gcc mailing list submissions to
        gcc@gcc.gnu.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://gcc.gnu.org/mailman/listinfo/gcc
or, via email, send a message with subject or body 'help' to
        gcc-request@gcc.gnu.org

You can reach the person managing the list at
        gcc-owner@gcc.gnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gcc digest..."

Re: Gcc Digest, Vol 15, Issue 5

[Martin Jambor]

Hi,

On Wed, May 05 2021, Gary Oblock via Gcc wrote:
> I've got to say appearances can be deceptive
> in GCC and struct _modif_basket *[4061] is not
> necessarily equal to struct _modif_basket *[4061]
> even though the printed representation is
> the same...

In these cases it is handy to use the -fdump-.*-uid dumps, as for
example in -fdump-tree-release_ssa-uid

When invoking dumping from the code, the flag for it TDF_UID.

Martin