From: Jason Merrill <jason@redhat.com>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: gcc@gcc.gnu.org, aph@redhat.com, Jason Merrill <jason@redhat.com>
Subject: Re: On alignment
Date: Tue, 25 Mar 2003 18:41:00 -0000 [thread overview]
Message-ID: <wvlu1drl2kl.fsf@prospero.boston.redhat.com> (raw)
In-Reply-To: <wvl1y0vmhdv.fsf@prospero.boston.redhat.com> (Jason Merrill's message of "Tue, 25 Mar 2003 13:27:08 -0500")
On Tue, 25 Mar 2003 13:27:08 -0500, Jason Merrill <jason@redhat.com> wrote:
> On Tue, 25 Mar 2003 11:22:13 -0500, "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca> wrote:
>
>> If I am not mistaken, a similar approach was used by OpenOffice.org when trying to support
>> both gcc 2.9.5X components and gcc 3.X components
>
> Indeed, it looks like they're trying to do the same thing using the same
> technique that Andrew was. Can anyone tell me whether they applied
> CPPU_GCC3_ALIGN to any long long or double fields?
The comment would appear to suggest otherwise:
// This pragma macro is appended to every first member of a struct,
// iff the struct inherits from a base struct and the first member
// of this structure is not a double or [unsigned] long long.
Sounds like they noticed and worked around this bug. Which makes me more
inclined to go ahead and fix it.
Jason
next prev parent reply other threads:[~2003-03-25 18:32 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 [this message]
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
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=wvlu1drl2kl.fsf@prospero.boston.redhat.com \
--to=jason@redhat.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kevin.hendricks@sympatico.ca \
/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).