public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: Benjamin Kosnik <bkoz@redhat.com>, Phil Edwards <phil@jaj.com>
Cc: law@redhat.com, janis187@us.ibm.com, jakub@redhat.com,
	Franz.Sirl-kernel@lauterbach.com, mark@codesourcery.com,
	gcc@gcc.gnu.org
Subject: Re: GCC 3.2
Date: Wed, 21 Aug 2002 04:31:00 -0000	[thread overview]
Message-ID: <200208210728.40229.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <20020820213115.484595ed.bkoz@redhat.com>

Hi,,

As is will your tests detect any layout issues (changes in sizeof and 
offsetof of structure members) like the datatest.cxx, I abstracted from 
OOo code and sent to Franz?  It was those changes from gcc 2.95.X to gcc 
3.X that made the C++ to uno bridge codeneed to use an alignment 
workaround.

Thanks,

Kevin


On August 21, 2002 12:31, Benjamin Kosnik wrote:
> Just an update for those not monitoring the libstdc++ list.
>
> There's been a discussion of this, and a partial implementation by
> Ulrich, Phil, and myself. It looks like initial implementation is here
>
> http://gcc.gnu.org/ml/libstdc++/2002-08/msg00190.html
>
> Please comment if there are any bright ideas on how to make this better.
>
> thanks,
> benjamin

  reply	other threads:[~2002-08-21  4:31 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-27  1:01 Mark Mitchell
2002-07-27  1:28 ` Joe Buck
2002-07-27  1:30   ` Mark Mitchell
2002-07-27  3:30 ` Zack Weinberg
2002-07-29  4:26   ` Mark Mitchell
2002-07-29  5:00     ` Toon Moene
2002-07-27 16:26 ` Franz Sirl
2002-07-27 18:32   ` Jakub Jelinek
2002-07-30  6:49   ` Jason Merrill
2002-07-31  2:11     ` Jason Merrill
2002-07-31  5:05       ` Jason Merrill
2002-07-31  6:35       ` Neil Booth
2002-07-31  7:14       ` Neil Booth
2002-08-04 10:08         ` Joseph S. Myers
2002-07-31 10:45       ` Mark Mitchell
2002-08-01 14:42         ` Jason Merrill
2002-08-02  4:58           ` PATCH to avoid copying tail padding (was: GCC 3.2) Jason Merrill
2002-08-12  8:47   ` GCC 3.2 Jeff Law
2002-08-12 11:52     ` Jakub Jelinek
2002-08-12 13:14       ` Vladimir Makarov
2002-08-12 13:28       ` Jeff Law
2002-08-12 13:30         ` Jakub Jelinek
2002-08-12 16:42         ` Janis Johnson
2002-08-13  9:46           ` Jeff Law
2002-08-19 11:41             ` Phil Edwards
2002-08-20 21:38               ` Benjamin Kosnik
2002-08-21  4:31                 ` Kevin B. Hendricks [this message]
2002-08-21  9:56                   ` Benjamin Kosnik
2002-08-21 10:24                     ` Kevin B. Hendricks
2002-08-21 11:24                 ` Janis Johnson
2002-08-21 12:02                   ` Phil Edwards
2002-08-21 14:53                     ` Janis Johnson
2002-08-21 20:03                       ` Benjamin Kosnik
2002-07-27 22:19 Benjamin Kosnik
2002-07-28  9:40 ` Jakub Jelinek
     [not found] <Pine.LNX.4.33.0208041756450.30248-100000@kern.srcf.societies.cam.ac.uk>
2002-08-04 10:24 ` Gerald Pfeifer
2002-08-12 19:05 Benjamin Kosnik
2002-10-18 17:23 gcc 3.2 Udo Tremel
2002-10-18 18:08 ` Mike Stump

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=200208210728.40229.kevin.hendricks@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=janis187@us.ibm.com \
    --cc=law@redhat.com \
    --cc=mark@codesourcery.com \
    --cc=phil@jaj.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).