public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "syq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113180] MIPS: bitops on an long long struct uses ins instead dins (or with -mstrict-align on aarch64)
Date: Mon, 06 May 2024 16:46:57 +0000	[thread overview]
Message-ID: <bug-113180-4-d3z00z9Aqv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113180-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113180

--- Comment #3 from YunQiang Su <syq at gcc dot gnu.org> ---
The argument `to` of `expand_assignment` differs between `strict-align` and
`no-strict-align`.

`debug_tree` states that the `strict-align` one has a `MEMREF` RTL, while 
`no-strict-align` has a `reg` one.

Any idea when the RTL is generated from STMT?

      parent reply	other threads:[~2024-05-06 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 14:08 [Bug target/113180] New: MIPS: bitops on an long long struct uses ins instead dins syq at gcc dot gnu.org
2023-12-31  6:31 ` [Bug middle-end/113180] MIPS: bitops on an long long struct uses ins instead dins (or with -mstrict-align on aarch64) pinskia at gcc dot gnu.org
2023-12-31  6:31 ` pinskia at gcc dot gnu.org
2023-12-31  6:37 ` pinskia at gcc dot gnu.org
2024-05-06 16:46 ` syq at gcc dot gnu.org [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=bug-113180-4-d3z00z9Aqv@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).