public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101849] MMA built-in dies with a verify_gimple failed error
Date: Thu, 12 Aug 2021 18:06:27 +0000 [thread overview]
Message-ID: <bug-101849-4-Q0hholFGfa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101849-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101849
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #4)
> Is there a benefit of one over the other? ...other than the build2 code
> being simpler since we'd just pass in the type we want.
So the following seems to work which seems a little simpler than what I
submitted. I'll test this along with a little beefier test case with multiple
offsets, with some not constant.
tree ptr_t = build_pointer_type (vector_pair_type_node);
tree mem = build2 (MEM_REF, vector_pair_type_node,
build2 (POINTER_PLUS_EXPR, ptr_t, ptr, offset),
build_int_cst (ptr_t, 0));
next prev parent reply other threads:[~2021-08-12 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 17:39 [Bug target/101849] New: " bergner at gcc dot gnu.org
2021-08-10 17:40 ` [Bug target/101849] " bergner at gcc dot gnu.org
2021-08-10 17:41 ` bergner at gcc dot gnu.org
2021-08-10 21:23 ` bergner at gcc dot gnu.org
2021-08-11 7:24 ` rguenth at gcc dot gnu.org
2021-08-11 22:20 ` bergner at gcc dot gnu.org
2021-08-12 18:06 ` bergner at gcc dot gnu.org [this message]
2021-08-19 22:34 ` cvs-commit at gcc dot gnu.org
2021-09-02 19:09 ` cvs-commit at gcc dot gnu.org
2021-09-03 1:48 ` cvs-commit at gcc dot gnu.org
2021-09-03 2:31 ` bergner at gcc dot gnu.org
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=bug-101849-4-Q0hholFGfa@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).