public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibolton at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43976] warning about increased alignment during casting printed even though variable is properly aligned
Date: Wed, 08 Sep 2010 10:02:00 -0000	[thread overview]
Message-ID: <20100908100205.1456.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43976-7726@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from ibolton at gcc dot gnu dot org  2010-09-08 10:02 -------
Confirmed on latest 4.4, 4.5 and 4.6 (trunk).

Related GCC documentation on alignment of structure fields is here:
http://gcc.gnu.org/onlinedocs/gcc-4.5.0/gcc/Variable-Attributes.html#Variable-Attributes

In the short-term, one workaround is to write the code as follows:

#include <stdio.h>

struct Foo
{
    char c[sizeof(int)];
} __attribute__((aligned(4)));

char junk;
Foo f;

int main()
{
    int *i = reinterpret_cast<int *>(&f);
    *i = 0x44434241;
    printf("%c %c %c %c", f.c[0], f.c[1], f.c[2], f.c[3]);
}

By aligning the structure Foo to 4 bytes, you can successfully cast a Foo* to
an int* and then initialise all four chars in one go.  (Without the type
attribute for the struct Foo, you still get the warning.)  My example prints "A
B C D".

FYI: I have tracked down the alleged offending code mentioned in an earlier
comment to build_c_cast() in c-typeck.c.


-- 

ibolton at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
      Known to fail|                            |4.4.5 4.5.2 4.6.0
   Last reconfirmed|0000-00-00 00:00:00         |2010-09-08 10:02:04
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43976


      parent reply	other threads:[~2010-09-08 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 14:40 [Bug c++/43976] New: " thiago at kde dot org
2010-05-04 17:27 ` [Bug middle-end/43976] " pinskia at gcc dot gnu dot org
2010-05-04 19:40 ` thiago at kde dot org
2010-05-05 19:18 ` hp at gcc dot gnu dot org
2010-05-05 19:40 ` thiago at kde dot org
2010-09-08 10:02 ` ibolton at gcc dot gnu dot org [this message]

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=20100908100205.1456.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).