public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44903] [4.6 Regression] FAIL: gcc.dg/pr35258.c execution test
Date: Sun, 11 Jul 2010 22:37:00 -0000 [thread overview]
Message-ID: <20100711223713.32529.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44903-276@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from rguenth at gcc dot gnu dot org 2010-07-11 22:37 -------
(In reply to comment #11)
> Subject: Re: [4.6 Regression] FAIL: gcc.dg/pr35258.c execution test
>
> > > The above testcase doesn't work with 4.5 and I doubt it ever worked on
> > > PA. The pointer passed to foo is used as is. It's only the memcpy special
> > > case that is handled by 4.5 and earlier.
> >
> > On i?86 we get correct 1-byte alignment for the pointer access while on
> > my ia64-cross the MEM has 4-byte alignment which is wrong. t is properly
> > 1-byte aligned (and pointer-to packed structs for example will work only
> > because there's a handled_component_ref around the pointer dereference).
>
> On hppa64, I see
>
> (insn 7 6 8 3 xxx.c:3 (set (reg:SI 71)
> (mem:SI (reg/v/f:DI 69 [ p ]) [0 *p_1(D)+0 S4 A32])) -1 (nil))
>
> in expand. The alignment is passed into the move expander.
For reference, on i?86 I see (on the 4.5 branch):
(insn 6 5 7 3 t.c:3 (set (reg:SI 62)
(mem:SI (reg/v/f:DI 60 [ p ]) [0 S4 A8])) -1 (nil))
and on trunk:
(insn 6 5 7 3 t.c:3 (set (reg:SI 62)
(mem:SI (reg/v/f:DI 60 [ p ]) [0 *p_1(D)+0 S4 A8])) -1 (nil))
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44903
next prev parent reply other threads:[~2010-07-11 22:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 15:17 [Bug tree-optimization/44903] New: " danglin at gcc dot gnu dot org
2010-07-10 19:46 ` [Bug tree-optimization/44903] [4.6 Regression] " danglin at gcc dot gnu dot org
2010-07-10 21:29 ` [Bug target/44903] " rguenth at gcc dot gnu dot org
2010-07-10 23:35 ` dave at hiauly1 dot hia dot nrc dot ca
2010-07-11 10:47 ` rguenth at gcc dot gnu dot org
2010-07-11 15:17 ` dave at hiauly1 dot hia dot nrc dot ca
2010-07-11 16:24 ` rguenth at gcc dot gnu dot org
2010-07-11 16:33 ` danglin at gcc dot gnu dot org
2010-07-11 16:55 ` dave at hiauly1 dot hia dot nrc dot ca
2010-07-11 22:04 ` rguenth at gcc dot gnu dot org
2010-07-11 22:22 ` dave at hiauly1 dot hia dot nrc dot ca
2010-07-11 22:37 ` rguenth at gcc dot gnu dot org [this message]
2010-07-13 13:53 ` rguenth at gcc dot gnu dot org
2010-07-13 17:41 ` mikpe at it dot uu dot se
2010-07-14 0:19 ` danglin at gcc dot gnu dot org
2010-07-23 12:14 ` rguenth at gcc dot gnu dot org
2010-07-26 12:22 ` rguenth at gcc dot gnu dot org
2010-07-26 12:45 ` rguenth at gcc dot gnu dot org
2010-07-26 12:46 ` rguenth at gcc dot gnu dot org
2010-07-28 0:22 ` dave at hiauly1 dot hia dot nrc dot ca
2010-07-28 10:33 ` rguenth at gcc dot gnu dot org
2010-07-28 10:33 ` rguenth at gcc dot gnu dot 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=20100711223713.32529.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).