public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.COM>
To: mark@codesourcery.com (Mark Mitchell)
Cc: jbuck@synopsys.COM (Joe Buck), gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: GCC 3.0.3
Date: Thu, 22 Nov 2001 00:04:00 -0000	[thread overview]
Message-ID: <200111292151.NAA08704@atrus.synopsys.com> (raw)
In-Reply-To: <5070000.1007065383@gandalf.codesourcery.com> from "Mark Mitchell" at Nov 29, 2001 12:23:03 PM

I wrote:
> > I'd like to see the fix to PR #4447 back-ported from the trunk to 3.0.3.
> > Actually I don't think any porting is needed, as it's a fix to mangle.c,
> > which hasn't had many changes; no, it doesn't change the ABI because
> > hitting the relevant code caused a core dump before.
> >
> > This PR is an ICE and a regression from 2.95.x.
> >
> > I believe that the relevant patch is
> >
> > 2001-11-17  Kriang Lerdsuwanakij  <lerdsuwa@users.sourceforge.net>
> >
> > 	* mangle.c (write_expression): Handle CAST_EXPR, STATIC_CAST_EXPR,
> > 	CONST_CAST_EXPR.
> > 	* operators.def: Add CAST_EXPR, STATIC_CAST_EXPR, CONST_CAST_EXPR.

Mark writes:
> Yes, this is OK.  Please apply the patch.

I don't have write access, so we'll need a volunteer to apply the patch.

Joe

WARNING: multiple messages have this Message-ID
From: Joe Buck <jbuck@synopsys.COM>
To: mark@codesourcery.com (Mark Mitchell)
Cc: jbuck@synopsys.COM (Joe Buck), gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: GCC 3.0.3
Date: Thu, 29 Nov 2001 13:51:00 -0000	[thread overview]
Message-ID: <200111292151.NAA08704@atrus.synopsys.com> (raw)
Message-ID: <20011129135100.0NV5lkidtiW3HdZgz2NPSA6LKPVNNJ1uIR5XZpajh4A@z> (raw)
In-Reply-To: <5070000.1007065383@gandalf.codesourcery.com>

I wrote:
> > I'd like to see the fix to PR #4447 back-ported from the trunk to 3.0.3.
> > Actually I don't think any porting is needed, as it's a fix to mangle.c,
> > which hasn't had many changes; no, it doesn't change the ABI because
> > hitting the relevant code caused a core dump before.
> >
> > This PR is an ICE and a regression from 2.95.x.
> >
> > I believe that the relevant patch is
> >
> > 2001-11-17  Kriang Lerdsuwanakij  <lerdsuwa@users.sourceforge.net>
> >
> > 	* mangle.c (write_expression): Handle CAST_EXPR, STATIC_CAST_EXPR,
> > 	CONST_CAST_EXPR.
> > 	* operators.def: Add CAST_EXPR, STATIC_CAST_EXPR, CONST_CAST_EXPR.

Mark writes:
> Yes, this is OK.  Please apply the patch.

I don't have write access, so we'll need a volunteer to apply the patch.

Joe

  reply	other threads:[~2001-11-29 21:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:24 Mark Mitchell
2001-11-21 22:25 ` Joe Buck
2001-11-21 23:26   ` Mark Mitchell
2001-11-22  0:04     ` Joe Buck [this message]
2001-11-22  0:14       ` Mark Mitchell
2001-11-22  2:58         ` Joe Buck
2001-11-22  7:35           ` Mark Mitchell
2001-11-29 17:16             ` Mark Mitchell
2001-11-29 16:15           ` Joe Buck
2001-11-29 14:25         ` Mark Mitchell
2001-11-29 13:51       ` Joe Buck
2001-11-29 12:28     ` Mark Mitchell
2001-11-23 14:47   ` fix for PR 4447: is this really correct? Joe Buck
2001-11-24 20:36     ` Kriang Lerdsuwanakij
2001-11-30 23:02       ` Kriang Lerdsuwanakij
2001-12-01 16:08       ` Joe Buck
2001-12-02  3:12         ` Kriang Lerdsuwanakij
2001-12-03  9:42           ` Mark Mitchell
2001-12-01 17:32       ` Alexandre Oliva
2001-11-30 11:20     ` Joe Buck
2001-11-29 11:51   ` GCC 3.0.3 Joe Buck
2001-11-23 14:48 ` Stephane Carrez
2001-11-23 15:52   ` Jakub Jelinek
2001-11-30 11:47     ` Jakub Jelinek
2001-11-30 11:27   ` Stephane Carrez
2001-12-03  8:34   ` Mark Mitchell
2001-11-24 21:15 ` Toon Moene
2001-11-30 23:39   ` Toon Moene
2001-11-29 10:24 ` Mark Mitchell

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=200111292151.NAA08704@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@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).