public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/48124] [4.3/4.4/4.5/4.6/4.7 Regression] likely wrong code bug
Date: Tue, 15 Mar 2011 10:27:00 -0000 [thread overview]
Message-ID: <bug-48124-4-E2uJaquoA7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48124-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48124
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-15 10:21:04 UTC ---
Hm, e has alignment of 8 bytes and f of 4 but the assembler doesn't pad
e's size to 8 byte multiples appearantly
.data
.align 8
.type e, @object
.size e, 12
e:
.byte 0
.byte 0
.byte 0
.byte 0
.value 0
.byte 0
.byte 0
.byte 1
.byte 0
.zero 2
.align 4
.type f, @object
.size f, 4
f:
.long 1
this is probably a more general problem also with the vectorizer which
happily increases alignment of global variables independed on if their
size is a multiple of that alignment.
If the asm output machinery does not try to handle padding to multiples
of alignment size then that's the bug I guess.
next prev parent reply other threads:[~2011-03-15 10:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 20:36 [Bug c/48124] New: " regehr at cs dot utah.edu
2011-03-14 21:53 ` [Bug middle-end/48124] [4.3/4.4/4.5/4.6/4.7 Regression] " jakub at gcc dot gnu.org
2011-03-14 22:09 ` jakub at gcc dot gnu.org
2011-03-15 10:27 ` rguenth at gcc dot gnu.org [this message]
2011-03-15 11:09 ` jakub at gcc dot gnu.org
2011-03-15 12:58 ` aldyh at redhat dot com
2011-03-31 15:05 ` jakub at gcc dot gnu.org
2011-04-10 10:43 ` rguenth at gcc dot gnu.org
2011-05-20 7:15 ` jakub at gcc dot gnu.org
2011-06-27 12:28 ` rguenth at gcc dot gnu.org
2012-02-01 12:36 ` [Bug middle-end/48124] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-02-01 12:49 ` rguenth at gcc dot gnu.org
2012-02-01 12:59 ` rguenth at gcc dot gnu.org
2012-02-01 13:06 ` rguenth at gcc dot gnu.org
2012-02-01 13:58 ` rguenth at gcc dot gnu.org
2012-02-01 14:17 ` rguenth at gcc dot gnu.org
2012-02-01 14:54 ` rguenth at gcc dot gnu.org
2012-02-01 15:48 ` rguenth at gcc dot gnu.org
2012-02-21 12:04 ` rguenth at gcc dot gnu.org
2012-03-13 13:04 ` [Bug middle-end/48124] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-03-14 10:59 ` [Bug middle-end/48124] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-14 11:04 ` [Bug middle-end/48124] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-05-30 15:24 ` [Bug middle-end/48124] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-05-30 15:35 ` ebotcazou at gcc dot gnu.org
2012-05-31 9:21 ` rguenther at suse dot de
2012-05-31 10:39 ` ebotcazou at gcc dot gnu.org
2012-05-31 10:43 ` rguenther at suse dot de
2012-05-31 10:49 ` jakub at gcc dot gnu.org
2012-05-31 11:01 ` rguenther at suse dot de
2012-06-01 10:21 ` rguenther at suse dot de
2012-06-03 8:23 ` ebotcazou at gcc dot gnu.org
2012-06-04 8:44 ` rguenth at gcc dot gnu.org
2012-06-04 8:45 ` [Bug middle-end/48124] [4.5/4.6 " rguenth at gcc dot gnu.org
2012-07-02 11:06 ` rguenth at gcc dot gnu.org
2013-04-12 16:25 ` [Bug middle-end/48124] [4.6 " jakub 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-48124-4-E2uJaquoA7@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).