From: Peter Bergner <bergner@linux.ibm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] rs6000: Don't ICE when we disassemble an MMA variable [PR101322]
Date: Thu, 1 Sep 2022 09:17:07 -0500 [thread overview]
Message-ID: <6099d400-1030-e6ae-f114-5ad630b7bd03@linux.ibm.com> (raw)
In-Reply-To: <f4845a62-1f48-b4fb-cc8d-20565651028b@linux.ibm.com>
On 9/1/22 3:29 AM, Kewen.Lin wrote:
>> I have no idea why ptr_vector_*_type would behave differently here than
>> build_pointer_type (vector_*_type_node). Using the build_pointer_type()
>> fixed it for me, so that's why I went with it. :-) Maybe this is a bug
>> in lto???
>
> Thanks for your time to reproduce this!
>
> The only difference is that ptr_vector_*_type are built from the
> qualified_type based on vector_*_type_node, instead of directly from
> vector_*_type_node. I'm interested to have a further look at this later.
If you look into this, please let me know. I'd like to know what you
find out.
Peter
next prev parent reply other threads:[~2022-09-01 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 3:50 Peter Bergner
2022-08-31 9:22 ` Kewen.Lin
2022-08-31 13:59 ` Peter Bergner
2022-08-31 18:53 ` Peter Bergner
2022-08-31 20:51 ` Segher Boessenkool
2022-08-31 22:01 ` Peter Bergner
2022-08-31 23:08 ` Segher Boessenkool
2022-08-31 23:29 ` Peter Bergner
2022-09-01 8:29 ` Kewen.Lin
2022-09-01 14:17 ` Peter Bergner [this message]
2022-09-05 8:11 ` Kewen.Lin
2022-09-01 8:28 ` Kewen.Lin
2022-09-01 14:41 ` Segher Boessenkool
2022-08-31 15:58 ` Segher Boessenkool
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=6099d400-1030-e6ae-f114-5ad630b7bd03@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.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).