public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"aoliva@redhat.com" <aoliva@redhat.com>,
	"jason@redhat.com" <jason@redhat.com>
Subject: Re: PR 8134: C++ crash
Date: Wed, 16 Oct 2002 13:02:00 -0000	[thread overview]
Message-ID: <324520000.1034792868@warlock.codesourcery.com> (raw)
In-Reply-To: <3DAC62E6.4030002@codesourcery.com>



--On Tuesday, October 15, 2002 07:48:06 PM +0100 Nathan Sidwell 
<nathan@codesourcery.com> wrote:

> Mark Mitchell wrote:
>> PR 8134 is a crash in force_store_init_value on the branch; it is a
>> regression.
>
>> a) Nothing
>> b) Move my changes over.
>> c) Revert Alexandre's patch.

Jason wishes there was another choice, but thus far hasn't been able
to come up with one.

Gaby and Benjamin think that my large patch is bug-free.

Nathan isn't so optimistic.

I'm not so optimistic either.  I know my new patch is right in concept,
but I'm not sure it's bugless.  I don't think it's prudent to move over
a patch that substantial when it hasn't received more than a week or two
of testing.

So, I'm going to go with (c).  I'll be updating the caveats HTML page
with information about this.  The good news is that pointers-to-members
are rare, programs relying on zero-initialization of them are rarer,
and there is always a work-around -- explicitly initialize the
pointer-to-member.

I hope people use pointers-to-members a lot on IPF.  The whole deal here
is that we're trying to save an addition per use of a pointer to data
member on a machine that doesn't have base+offset addressing.  I have
this bad feeling that I've spent more time implementing this stuff than
will ever be saved by all the programs in the world running for all time
on architectures where this will help...)

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

  reply	other threads:[~2002-10-16 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 12:15 Mark Mitchell
2002-10-15 12:37 ` Gabriel Dos Reis
2002-10-15 12:59 ` Nathan Sidwell
2002-10-16 13:02   ` Mark Mitchell [this message]
2002-10-16 13:23     ` Nathan Sidwell
2002-10-16 13:24       ` Mark Mitchell
2002-10-15 15:38 ` Jason Merrill
2002-10-15 16:41   ` Mark Mitchell
2002-10-15 12:25 Benjamin Kosnik
2002-10-16  4:03 Reichelt

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=324520000.1034792868@warlock.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=nathan@codesourcery.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).