public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david.bolvansky at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/7061] Access of bytes in struct parameters Date: Sat, 11 Jun 2022 13:29:26 +0000 [thread overview] Message-ID: <bug-7061-4-UHDBJZmWBG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-7061-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7061 Dávid Bolvanský <david.bolvansky at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.bolvansky at gmail dot com --- Comment #10 from Dávid Bolvanský <david.bolvansky at gmail dot com> --- llvm emits just: im: # @im shufps xmm0, xmm0, 85 # xmm0 = xmm0[1,1,1,1] ret
next prev parent reply other threads:[~2022-06-11 13:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7061-4@http.gcc.gnu.org/bugzilla/> 2021-09-22 20:26 ` gabravier at gmail dot com 2022-05-30 20:40 ` cvs-commit at gcc dot gnu.org 2022-06-10 14:20 ` cvs-commit at gcc dot gnu.org 2022-06-11 13:29 ` david.bolvansky at gmail dot com [this message] 2022-06-27 6:49 ` cvs-commit at gcc dot gnu.org [not found] <bug-7061-695@http.gcc.gnu.org/bugzilla/> 2005-11-02 8:09 ` rth at gcc dot gnu dot org 2006-02-08 21:10 ` pluto at agmk dot net
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-7061-4-UHDBJZmWBG@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: linkBe 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).