public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: tromey@redhat.com
Cc: Jason Merrill <jason@redhat.com>,
	Jamie Lokier <jamie@shareable.org>, Andrew Haley <aph@redhat.com>,
	gcc@gcc.gnu.org
Subject: Re: On alignment
Date: Wed, 23 Apr 2003 19:33:00 -0000	[thread overview]
Message-ID: <m3of2xav7s.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <87lly1f5ir.fsf@fleche.redhat.com>

Tom Tromey <tromey@redhat.com> writes:

| >>>>> "Jason" == Jason Merrill <jason@redhat.com> writes:
| 
| [ about  struct foo { double x; } ]
| 
| Tom> I'd like to find the most future-proof way to do this.  In the above,
| Tom> is __alignof__(foo::x) the best way?  I'm only concerned with
| Tom> alignment of fields.
| 
| Jason> It is since my recent patch to do all alignment calculation for
| Jason> fields in layout_decl.
| 
| I can't do this.
| 
|     struct aligner { double field; };
| 
|     int compute () { return __alignof__ (aligner::field); }
| 
| fleche. gcc -c y.cc
| y.cc: In function `int compute()':
| y.cc:1: error: invalid use of non-static data member `aligner::field'
| y.cc:3: error: from this location

The following does the job:

    template<typename T>
      struct object_alignment {

         struct helper {
            T& datum;
            helper();
         };

         static helper instance;

         enum { value = __alignof__ (instance.datum) };
      };

To be used as object_alignment<T>::value.

| I can use __alignof__(aligner), but my concern is that eventually this
| will yield "8" instead of "4" on x86.

With the above, the following

     #include <iostream>

     int main()
     {
        std::cout << object_alignment<double>::value
                  << std::endl;
     }

outputs "8" on an i686-pc-linux-gnu.

Enjoy ;-)

-- Gaby

  parent reply	other threads:[~2003-04-23 19:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 16:48 Kevin B. Hendricks
2003-03-25 18:39 ` Jason Merrill
2003-03-25 18:41   ` Jason Merrill
2003-03-25 19:14     ` Kevin B. Hendricks
2003-03-25 19:57       ` Jason Merrill
2003-04-22 11:36         ` Andrew Haley
2003-04-22 12:05           ` Nathan Sidwell
2003-04-22 12:37             ` Andrew Haley
2003-04-22 13:15           ` Andreas Schwab
2003-04-23 13:32             ` Jamie Lokier
2003-04-23 16:07               ` Jason Merrill
2003-04-23 17:41               ` Tom Tromey
2003-04-23 18:06                 ` Jason Merrill
2003-04-23 18:42                   ` Tom Tromey
2003-04-23 19:13                     ` Jason Merrill
2003-04-23 19:43                       ` Gabriel Dos Reis
2003-04-23 20:23                         ` Tom Tromey
2003-04-23 21:45                           ` Gabriel Dos Reis
2003-04-24  7:00                           ` Jason Merrill
2003-04-24 11:45                             ` Andrew Haley
2003-05-01 23:50                               ` Tom Tromey
2003-05-02 13:08                                 ` Gabriel Dos Reis
2003-05-05 14:56                                   ` Jason Merrill
2003-05-08  9:58                                     ` Gabriel Dos Reis
2003-04-23 19:33                     ` Gabriel Dos Reis [this message]
2003-04-24  1:32                     ` Jamie Lokier
2003-03-25 21:27       ` Tom Tromey
2003-03-26 12:58         ` Andrew Haley
2003-03-26 22:26           ` Mark Mitchell
2003-03-25 18:57   ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23 19:47 Robert Dewar
2003-04-23 19:34 Joern Rennecke
2003-04-22 17:19 Robert Dewar
2003-04-22 14:43 Robert Dewar
2003-04-22 15:13 ` Andrew Haley
2003-04-22 16:22   ` Jason Merrill
2003-04-22 16:26     ` Nicola Pero
2003-04-22 17:19       ` Andrew Haley
2003-04-22 18:46       ` Jason Merrill
2003-04-22 17:17     ` Andrew Haley
2003-03-21  0:25 Jason Merrill
2003-03-21 11:49 ` Andrew Haley
2003-03-21 15:18   ` Andrew Haley
2003-03-21 19:31   ` Tom Tromey
2003-03-21 15:39 ` Michael Matz
2003-03-21 15:41   ` Andrew Haley
2003-03-22  0:25     ` Jason Merrill
2003-03-22  9:35       ` Tom Tromey
2003-03-22 10:31       ` Andrew Haley
2003-03-25  2:52         ` Jason Merrill
2003-03-25 10:16           ` Andrew Haley

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=m3of2xav7s.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=aph@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jamie@shareable.org \
    --cc=jason@redhat.com \
    --cc=tromey@redhat.com \
    /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).