public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mendell@ca.ibm.com,
	nobody@gcc.gnu.org
Subject: Re: c++/7459: Missing '*' in unwind-dw2.c ?
Date: Thu, 19 Dec 2002 18:23:00 -0000	[thread overview]
Message-ID: <20021220022349.14089.qmail@sources.redhat.com> (raw)

Synopsis: Missing '*' in unwind-dw2.c ?

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Thu Dec 19 18:23:48 2002
State-Changed-Why:
    Mark,
    I have looked so often at this report, and never really
    understood it. Could you describe a little bit in more
    detail why you think this?
    
    Unfortunately, cvs annotate does not tell who wrote
    the code, so I cannot CC: anyone with more knowledge :-(
    
    Thanks
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7459


             reply	other threads:[~2002-12-20  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 18:23 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-09 15:05 bangerth
2003-01-09  3:06 mendell
2002-07-31 13:16 mendell

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=20021220022349.14089.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mendell@ca.ibm.com \
    --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).