public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/8684: ABI Issue:   gcc3.2 is not reusing tail-padding..
Date: Tue, 03 Dec 2002 12:36:00 -0000	[thread overview]
Message-ID: <20021203203602.4611.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8684; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: RE: c++/8684: ABI Issue:   gcc3.2 is not reusing tail-padding..
Date: Tue, 3 Dec 2002 14:35:00 -0600 (CST)

 ---------- Forwarded message ----------
 Date: Tue, 3 Dec 2002 12:08:57 -0800
 From: "Davasam, Sunil K" <sunil.k.davasam@intel.com>
 To: bangerth@dealii.org
 Subject: RE: c++/8684: ABI Issue:   gcc3.2 is not reusing tail-padding..
 
 Sorry for the late reply. I tried with intel 6.0,7.0 compilers on Linux.
 In both cases I am getting same result. Here are the details.
 
 [skdavasa@crystal tmp]$ cat t4.cpp 
 #include <stdio.h>
 
 struct C1 {
        int i;
        char c;
 };
 
 struct C2 : C1 {
        char c;
 };
 
 int main()
 {
         printf("sizeof (C1) = %d\n", sizeof (C1) );
         printf("sizeof (C2) = %d\n", sizeof (C2) );
         return 0;
 }
 
 [skdavasa@crystal tmp]$ icpc t4.cpp 
 t4.cpp
 [skdavasa@crystal tmp]$ a.out
 sizeof (C1) = 8
 sizeof (C2) = 8
 [skdavasa@crystal ~/tmp]$ icpc -V
 Intel(R) C++ Compiler for 32-bit applications, Version 6.0.1   Build 20021018Z
 Copyright (C) 1985-2002 Intel Corporation.  All rights reserved.
 
 [skdavasa@crystal ~/tmp]$ source ~/.ia32_productrc 70
 [skdavasa@crystal ~/tmp]$ icpc -V
 Intel(R) C++ Compiler for 32-bit applications, Version 7.0   Build 20021021Z
 Copyright (C) 1985-2002 Intel Corporation.  All rights reserved.
 
 [skdavasa@crystal ~/tmp]$ icpc t4.cpp 
 [skdavasa@crystal ~/tmp]$ a.out
 sizeof (C1) = 8
 sizeof (C2) = 8
 ---
       
 Thanks & Regards,
 -Sunil.
 
 
 -----Original Message-----
 From: bangerth@dealii.org [mailto:bangerth@dealii.org]
 Sent: Tuesday, November 26, 2002 7:30 PM
 To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org;
 Davasam, Sunil K
 Subject: Re: c++/8684: ABI Issue: gcc3.2 is not reusing tail-padding..
 
 
 Synopsis: ABI Issue:   gcc3.2 is not reusing tail-padding..
 
 State-Changed-From-To: open->feedback
 State-Changed-By: bangerth
 State-Changed-When: Tue Nov 26 19:29:32 2002
 State-Changed-Why:
     Between 3.1.1 and 3.2, a number of ABI bugs have been fixed.
     This may be one of them. The question I have for you, is
     which version of the Intel compiler you have been using?
     If I use icc 6.0 on Linux, I get 8 and 12, so exactly
     the same results as with gcc3.2. So to me it seems as if
     they were now compatible in this respect.
     
     Thanks
       Wolfgang
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8684
 


             reply	other threads:[~2002-12-03 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 12:36 Wolfgang Bangerth [this message]
2002-12-03 12:44 bangerth
2003-01-24 16:56 Giovanni Bajo
2003-01-24 17:17 nathan

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=20021203203602.4611.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).