public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/3544: SJLJ exceptions with dwarf2 debug broken
Date: Wed, 15 Jan 2003 14:56:00 -0000	[thread overview]
Message-ID: <20030115145602.7112.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/3544; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Richard.Earnshaw@arm.com
Cc: rearnsha@arm.com, <rth@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: middle-end/3544: SJLJ exceptions with dwarf2 debug broken 
Date: Wed, 15 Jan 2003 08:52:17 -0600 (CST)

 > > Synopsis: SJLJ exceptions with dwarf2 debug broken
 > > 
 > > State-Changed-From-To: feedback->closed
 > > State-Changed-By: bangerth
 > > State-Changed-When: Tue Jan 14 15:13:31 2003
 > > State-Changed-Why:
 > >     Maybe fixed. No feedback also.
 > > 
 > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3544
 > 
 > It has been fixed.  But you are wrong to suggest there was no feedback.
 
 Right, I'm sorry. My eyes merged your reply to rth's putting the report 
 into feedback with that latter message. 
 
 Sorry
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-01-15 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 14:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15  9:56 Richard Earnshaw
2003-01-14 23:13 bangerth
2002-06-24  6:06 Richard Earnshaw
2002-06-17 11:26 rth
2002-06-17  2:46 rth
2001-07-03  7:16 Richard Earnshaw

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