public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeffrey Oldham <oldham@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/2851: dbxout.c's concat loses information
Date: Sun, 24 Nov 2002 20:26:00 -0000	[thread overview]
Message-ID: <20021118235603.21630.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/2851; it has been noted by GNATS.

From: Jeffrey Oldham <oldham@codesourcery.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, oldham@codesourcery.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: debug/2851: dbxout.c's concat loses information
Date: Mon, 18 Nov 2002 15:50:02 -0800

 bangerth@dealii.org wrote:
 > Synopsis: dbxout.c's concat loses information
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Mon Nov 18 15:35:53 2002
 > State-Changed-Why:
 >     Jeffrey,
 >     I tried to reproduce this, but have no problems to compile
 >     the code. However, maybe that was not the problem you
 >     meant, after all, the report is a little bit terse on
 >     what you expect the code to do or not do :-)
 >     
 >     Can you please see whether this still applies, and if so
 >     give instructions on how to reproduce the effects you want
 >     to demonstrate?
 >     
 >     Thanks
 >       Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2851
 
 I do not even know what the problem was.  Let's drop it.
 
 Thanks,
 Jeffrey D. Oldham
 oldham@codesourcery.com
 


             reply	other threads:[~2002-11-18 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 20:26 Jeffrey Oldham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-24 16:56 bangerth
2002-11-24 15:56 bangerth
2001-05-16 18:46 oldham

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=20021118235603.21630.qmail@sources.redhat.com \
    --to=oldham@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).