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 target/113180] New: MIPS: bitops on an long long struct uses ins instead dins
Date: Sat, 30 Dec 2023 14:08:29 +0000	[thread overview]
Message-ID: <bug-113180-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113180
           Summary: MIPS: bitops on an long long struct uses ins instead
                    dins
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: syq at gcc dot gnu.org
  Target Milestone: ---

```
struct yy {
        int x:32;
        int a:12;
        int b:12;
        int c:4;
        int d:4;
};

struct yy xx (struct yy a, long long b) {
        a.d = b;
        return a;
}
```

One DINS is enough for this ops, while currently the result is:

```
        dsra    $2,$4,32
        daddiu  $sp,$sp,-32
        ins     $2,$5,28,4
        sd      $4,16($sp)
        sw      $2,20($sp)
        ld      $3,16($sp)
        move    $2,$0
        sll     $4,$3,0
        dext    $4,$4,0,32
        dins    $2,$4,0,32
        dsrl    $3,$3,32
        dins    $2,$3,32,32
        jr      $31
        daddiu  $sp,$sp,32
```

             reply	other threads:[~2023-12-30 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 14:08 syq at gcc dot gnu.org [this message]
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

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@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).