public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53037] warn_if_not_aligned(X)
Date: Thu, 19 Apr 2012 16:02:00 -0000	[thread overview]
Message-ID: <bug-53037-4-wCIjoMmJuw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53037-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> 2012-04-19 16:00:41 UTC ---
(In reply to comment #3)
> Logically, about half of u64's will be properly aligned at the moment... Linus'

No necessarily. For

u64 x;
int y;
u64 z;

both x and z may be 4 byte aligned.

> request is that we flag the currently misaligned __[su]64's as __compat_[su]64
> and make __[su]64 aligned, so at least *new* interfaces will be properly
> aligned.

Is this feature only used for function parameters?


  parent reply	other threads:[~2012-04-19 16:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 22:59 [Bug c/53037] New: warn_if_not_aligned(X) hjl.tools at gmail dot com
2012-04-19  0:35 ` [Bug c/53037] warn_if_not_aligned(X) hjl.tools at gmail dot com
2012-04-19 15:48 ` hjl.tools at gmail dot com
2012-04-19 15:53 ` hpa at zytor dot com
2012-04-19 16:02 ` hjl.tools at gmail dot com [this message]
2012-04-19 16:07 ` hpa at zytor dot com
2012-04-19 16:54 ` hjl.tools at gmail dot com
2012-04-19 16:59 ` hpa at zytor dot com
2012-04-19 17:09 ` hjl.tools at gmail dot com
2012-04-19 17:12 ` hpa at zytor dot com
2012-04-19 17:22 ` hjl.tools at gmail dot com
2012-04-19 17:42 ` hpa at zytor dot com
2012-04-19 20:16 ` hjl.tools at gmail dot com
2012-04-19 20:19 ` hjl.tools at gmail dot com
2012-04-19 20:24 ` hpa at zytor dot com
2012-04-19 20:42 ` hjl.tools at gmail dot com
2012-04-19 21:07 ` hjl.tools at gmail dot com
2013-02-13 10:39 ` paolo.carlini at oracle dot com
2022-03-29  8:16 ` vries 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-53037-4-wCIjoMmJuw@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).