public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39954] [4.5 Regression] Revision 146817 caused unaligned access in gcc.dg/torture/pr26565.c
Date: Wed, 29 Apr 2009 00:33:00 -0000 [thread overview]
Message-ID: <20090429003331.4192.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39954-682@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from hjl dot tools at gmail dot com 2009-04-29 00:33 -------
(In reply to comment #6)
> Andrew is right. There is no "known" alignment (or misalignment) as far
> as the gimple code is concerned, only the natural alignment:
>
> send_probe (struct outdata * outdata, struct timeval * tp)
> {
> struct timeval * D.1240;
> D.1240_2 = &outdata_1(D)->tv;
> memcpy (D.1240_2, tp_3(D), 8); [tail call]
> return;
> }
>
How does gimple handle
typedef int foo __attribute__ ((aligned(1)));
void
bar (foo *p, char *b)
{
__builtin_memcpy (p, b, 30);
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39954
next prev parent reply other threads:[~2009-04-29 0:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 21:52 [Bug middle-end/39954] New: [4.5 Regression] Unaligned " hjl dot tools at gmail dot com
2009-04-28 21:54 ` [Bug middle-end/39954] " pinskia at gcc dot gnu dot org
2009-04-28 21:59 ` hjl dot tools at gmail dot com
2009-04-28 22:04 ` rguenth at gcc dot gnu dot org
2009-04-28 22:21 ` pinskia at gcc dot gnu dot org
2009-04-28 23:44 ` [Bug middle-end/39954] [4.5 Regression] Revision 146817 caused unaligned " hjl dot tools at gmail dot com
2009-04-28 23:48 ` pinskia at gcc dot gnu dot org
2009-04-29 0:17 ` matz at gcc dot gnu dot org
2009-04-29 0:33 ` hjl dot tools at gmail dot com [this message]
2009-04-29 0:42 ` hjl dot tools at gmail dot com
2009-04-29 0:44 ` pinskia at gcc dot gnu dot org
2009-04-29 11:33 ` joseph at codesourcery dot com
2009-04-29 11:39 ` matz at gcc dot gnu dot org
2009-05-05 15:48 ` mmitchel at gcc dot gnu dot org
2009-05-05 15:59 ` hjl dot tools at gmail dot com
2009-05-06 9:49 ` matz at gcc dot gnu dot org
2009-05-06 11:09 ` rguenth at gcc dot gnu dot org
2009-05-06 11:21 ` matz at gcc dot gnu dot org
2009-05-06 11:46 ` rguenther at suse dot de
2009-05-06 11:58 ` matz at gcc dot gnu dot org
2009-05-06 20:39 ` matz at gcc dot gnu dot org
2009-05-06 21:02 ` rguenther at suse dot de
2009-05-06 21:39 ` matz at suse dot de
2009-05-06 21:56 ` matz at gcc dot gnu dot org
2009-05-06 21:56 ` rguenther at suse dot de
2009-05-10 18:40 ` danglin at gcc dot gnu dot org
2009-06-17 20:38 ` sje at cup dot hp dot com
2009-06-18 11:26 ` matz at gcc dot gnu dot org
2010-01-18 11:12 ` rguenth at gcc dot gnu dot org
2010-01-18 11:24 ` rguenth at gcc dot gnu dot org
2010-01-18 11:43 ` rguenth at gcc dot gnu dot org
2010-01-18 13:00 ` rguenth at gcc dot gnu dot org
2010-01-18 13:00 ` 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=20090429003331.4192.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).