public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bjoern dot m dot haase at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/19885] [4.0 Regression] avr dwarf-2 support is broken for head 4.0
Date: Fri, 11 Feb 2005 22:56:00 -0000 [thread overview]
Message-ID: <20050211190433.25574.qmail@sourceware.org> (raw)
In-Reply-To: <20050210232514.19885.bjoern.m.haase@web.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
------- Additional Comments From bjoern dot m dot haase at web dot de 2005-02-11 19:04 -------
Subject: Re: [4.0 Regression] avr dwarf-2 support is broken for head 4.0
Am Freitag, 11. Februar 2005 00:36 schrieb ericw at evcohs dot com:
> ------- Additional Comments From ericw at evcohs dot com 2005-02-10 23:36
> ------- As an aside, DWARF2 is about to become the default debugging
> information used in WinAVR, for both Atmel's AVR Studio and for use with
> avr-gdb/avr-insight. So this one is crucial for having a successful 4.0.0
> release for the avr target.
Hi Eric,
brief question:
As far as I know you have monitored Thorleif Sandes attempts of getting the
dwarf support working for avr-studio. Do you remember that it was necessary
at the time to implement bug-fixes for getting it functional for gcc 3.4. ?
Yours,
Björn
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19885
next prev parent reply other threads:[~2005-02-11 19:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 5:59 [Bug c/19885] New: dwarf-2 support is broken for head 4.0.0 bjoern dot m dot haase at web dot de
2005-02-11 5:59 ` [Bug middle-end/19885] [4.0 Regression] avr dwarf-2 support is broken for head 4.0 pinskia at gcc dot gnu dot org
2005-02-11 6:05 ` bjoern dot m dot haase at web dot de
2005-02-11 6:06 ` pinskia at gcc dot gnu dot org
2005-02-11 7:56 ` ericw at evcohs dot com
2005-02-11 8:18 ` bjoern dot m dot haase at web dot de
2005-02-11 8:44 ` bjoern dot m dot haase at web dot de
2005-02-11 11:47 ` [Bug debug/19885] " pinskia at gcc dot gnu dot org
2005-02-11 22:51 ` bjoern dot m dot haase at web dot de
2005-02-11 22:56 ` bjoern dot m dot haase at web dot de [this message]
2005-03-05 19:58 ` [Bug debug/19885] [4.0/4.1 Regression] avr dwarf-2 support is broken for head 4.0/4.1 pinskia at gcc dot gnu dot org
2005-03-17 6:33 ` tsandnes at atmel dot com
2005-05-06 7:44 ` bjoern dot m dot haase at web dot de
2005-06-26 18:15 ` [Bug target/19885] " pinskia at gcc dot gnu dot org
2005-06-27 17:09 ` bjoern dot m dot haase at web dot de
2005-07-26 23:46 ` steven at gcc dot gnu dot org
2005-07-27 6:21 ` bjoern dot m dot haase at web dot de
2005-07-27 6:48 ` bjoern dot m dot haase at web dot de
2005-07-27 8:56 ` giovannibajo at libero dot it
2005-07-27 8:57 ` giovannibajo at libero dot it
2005-07-27 18:47 ` bjoern dot m dot haase at web dot de
2005-07-27 22:33 ` cvs-commit at gcc dot gnu dot org
2005-07-27 23:37 ` cvs-commit at gcc dot gnu dot org
2005-07-27 23:39 ` giovannibajo at libero dot it
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=20050211190433.25574.qmail@sourceware.org \
--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).