public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/7061] Access of bytes in struct parameters
Date: Wed, 02 Nov 2005 08:09:00 -0000 [thread overview]
Message-ID: <20051102080929.2935.qmail@sourceware.org> (raw)
In-Reply-To: <bug-7061-695@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rth at gcc dot gnu dot org 2005-11-02 08:09 -------
And there is nothing Alpha specific about this. Any target which passes
structures in registers can show it. For instance, ia64:
f1:
.prologue
.body
.mmi
st2 [r12] = r32
nop 0
mov r14 = r12
;;
.mmi
ld1 r15 = [r14], 1
;;
ld1 r8 = [r14]
nop 0
;;
.mib
nop 0
add r8 = r8, r15
br.ret.sptk.many b0
.endp f1#
.align 16
.global f2#
.proc f2#
f2:
.prologue
.body
.mii
nop 0
extr.u r8 = r32, 8, 8
zxt1 r32 = r32
;;
.mib
nop 0
add r8 = r8, r32
br.ret.sptk.many b0
--
rth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC host triplet|alphapca56-*-linux-gnu |
GCC target triplet|alphapca56-*-linux-gnu |
Summary|Alpha: Access of bytes in |Access of bytes in struct
|struct parameters |parameters
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7061
next prev parent reply other threads:[~2005-11-02 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-7061-695@http.gcc.gnu.org/bugzilla/>
2005-11-02 8:06 ` [Bug rtl-optimization/7061] Alpha: " rth at gcc dot gnu dot org
2005-11-02 8:09 ` rth at gcc dot gnu dot org [this message]
2006-02-08 21:10 ` [Bug rtl-optimization/7061] " pluto at agmk dot net
[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
2022-06-27 6:49 ` cvs-commit 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=20051102080929.2935.qmail@sourceware.org \
--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).