public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/14919] [3.3]: DW_AT_comp_dir is missing
Date: Mon, 12 Apr 2004 15:56:00 -0000	[thread overview]
Message-ID: <20040412153257.30736.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040411221509.14919.hjl@lucon.org>


------- Additional Comments From gdr at integrable-solutions dot net  2004-04-12 15:32 -------
Subject: Re:  [3.3]: DW_AT_comp_dir is missing

"hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| Gaby, this bug is not a regression against 3.2. But it was fixed in the gcc 3.2
| Red Hat branch more tha a year ago. I'd like to bring this bug fix up to gcc 3.3
| branch.

Can you give me a sense of the effects of proposed patches (e.g. results of
testsuites on at least two major evaluation plateforms)?
This is going to be the last non-regression patches appalied to 3.3.4.
I'm going to announce that shortly.  Others would have to wait 3.3.5.

Thanks,

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14919


  parent reply	other threads:[~2004-04-12 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-11 23:18 [Bug debug/14919] New: [3.3 Regression]: " hjl at lucon dot org
2004-04-12  0:22 ` [Bug debug/14919] " hjl at lucon dot org
2004-04-12  0:36 ` pinskia at gcc dot gnu dot org
2004-04-12  0:38 ` pinskia at gcc dot gnu dot org
2004-04-12  1:21 ` hjl at lucon dot org
2004-04-12  5:07 ` pinskia at gcc dot gnu dot org
2004-04-12  6:55 ` hjl at lucon dot org
2004-04-12 15:33 ` [Bug debug/14919] [3.3]: " hjl at lucon dot org
2004-04-12 15:56 ` gdr at integrable-solutions dot net [this message]
2004-04-13 18:44 ` cvs-commit at gcc dot gnu dot org
2004-04-13 19:16 ` pinskia at gcc dot gnu dot org

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=20040412153257.30736.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).