public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9193: Testsuite error on mips-irix6 with g++.dg/abi/empty6.C (missing -Wabi warning)
Date: Wed, 08 Jan 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030108175603.7609.qmail@sources.redhat.com> (raw)

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

From: Mark Mitchell <mark@codesourcery.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
   "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: c++/9193: Testsuite error on mips-irix6 with
 g++.dg/abi/empty6.C (missing -Wabi warning)
Date: Wed, 08 Jan 2003 09:47:23 -0800

 --On Wednesday, January 08, 2003 12:37:50 PM -0500 "Kaveh R. Ghazi" 
 <ghazi@caip.rutgers.edu> wrote:
 
 >  > From: Mark Mitchell <mark@codesourcery.com>
 >  >
 >  > > and indeed no -Wabi warning is issued.  The failure occurs only when
 > I  > > run the testsuite with -mabi=64, it succeeds without that flag as
 > noted  > > in the test report above.
 >  >
 >  > That's correct behavior; it means that there's no change under that
 > ABI.
 >
 > For my own education, would you please help me understand why the
 > irix6 -mabi=n32 vs -mabi=64 flag affects this, but other 64 bit
 > platforms, or sparc -m64, don't see a change?
 
 Essentially, there's no logical answer.  We were assuming that
 DECL_FIELD_OFFSET meant something it only means sometimes.  On platforms
 where it meant what we thought it meant, we don't need to warn; elsewhere,
 we do.
 
 -- 
 Mark Mitchell                mark@codesourcery.com
 CodeSourcery, LLC            http://www.codesourcery.com


             reply	other threads:[~2003-01-08 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 17:56 Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-03 15:55 ghazi
2003-01-08 17:46 Kaveh R. Ghazi
2003-01-07  1:46 Mark Mitchell
2003-01-06 17:16 ghazi

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=20030108175603.7609.qmail@sources.redhat.com \
    --to=mark@codesourcery.com \
    --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).