public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49937] [4.7 Regression] g++.dg/tree-ssa/fwprop-align.C
Date: Tue, 09 Aug 2011 20:26:00 -0000	[thread overview]
Message-ID: <bug-49937-4-VQZC0fOmgv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49937-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-08-09 20:25:14 UTC ---
(In reply to comment #5)
> BIGGEST_ALIGNMENT is the
> "biggest alignment that any data type can require on this machine, in bits"
> "this is not the biggest alignment that is supported, just the biggest
> alignment that, when violated, may cause a fault".

Hence its use is suboptimal except as a fallback or when the *preferred*
alignment isn't stated, like in "LOCAL_ALIGNMENT (blob, BIGGEST_ALIGNMENT)".

Maybe it should be renamed to something matching its use, like
MAXIMUM_OF_MININUM_ALIGNMENTS_FOR_CPU_DATA_ACCESS...


  parent reply	other threads:[~2011-08-09 20:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 20:24 [Bug middle-end/49937] New: " hp at gcc dot gnu.org
2011-08-02  9:47 ` [Bug middle-end/49937] " rguenth at gcc dot gnu.org
2011-08-09  0:05 ` hp at gcc dot gnu.org
2011-08-09 11:39 ` hp at gcc dot gnu.org
2011-08-09 12:20 ` [Bug tree-optimization/49937] " rguenth at gcc dot gnu.org
2011-08-09 13:23 ` rguenth at gcc dot gnu.org
2011-08-09 15:38 ` hp at gcc dot gnu.org
2011-08-09 20:26 ` hp at gcc dot gnu.org [this message]
2011-08-10  0:01 ` hp at gcc dot gnu.org
2011-08-10  8:51 ` rguenth at gcc dot gnu.org
2011-08-10  8:53 ` rguenth 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-49937-4-VQZC0fOmgv@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).