public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/48459] [4.6/4.7 Regression] avr: Assertion failure with -gdwarf-2
Date: Tue, 14 Jun 2011 09:48:00 -0000	[thread overview]
Message-ID: <bug-48459-4-wHokNBVidH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48459-4@http.gcc.gnu.org/bugzilla/>

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

Georg-Johann Lay <gjl at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gjl at gcc dot gnu.org

--- Comment #19 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-06-14 09:46:21 UTC ---
(In reply to comment #17)

> A full build for AVR fails, but that seems to be related to other
> open bugs.

What bugs? 

I can build avr-gcc SVN 175011 from today without problems on i686-pc-linux-gnu
+ gcc 4.3.2.

Target: avr
Configured with: ../../gcc.gnu.org/trunk/configure --target=avr
--prefix=/local/gnu/install/gcc-4.7 --disable-nls --disable-shared
--enable-languages=c,c++
Thread model: single
gcc version 4.7.0 20110614 (experimental) (GCC)

GNU assembler version 2.21 (avr) using BFD version (GNU Binutils) 2.21

GMP 5.0.1
MPFR 3.0.0
MPC 0.8.2


  parent reply	other threads:[~2011-06-14  9:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 11:56 [Bug other/48459] New: " avr at gjlay dot de
2011-04-06  0:20 ` [Bug debug/48459] [4.7 Regression] " pinskia at gcc dot gnu.org
2011-04-21 10:03 ` gjl at gcc dot gnu.org
2011-04-22  7:45 ` [Bug debug/48459] [4.6/4.7 " gjl at gcc dot gnu.org
2011-06-09 14:01 ` anitha.boyapati at atmel dot com
2011-06-09 14:19 ` jason at gcc dot gnu.org
2011-06-09 16:54 ` anitha.boyapati at atmel dot com
2011-06-09 17:01 ` anitha.boyapati at atmel dot com
2011-06-09 18:10 ` jason at gcc dot gnu.org
2011-06-10  4:15 ` anitha.boyapati at atmel dot com
2011-06-10  5:24 ` jason at gcc dot gnu.org
2011-06-10  7:39 ` anitha.boyapati at atmel dot com
2011-06-10 16:25 ` jason at gcc dot gnu.org
2011-06-13  6:54 ` anitha.boyapati at atmel dot com
2011-06-13  7:15 ` anitha.boyapati at atmel dot com
2011-06-13  7:31 ` eric.weddington at atmel dot com
2011-06-13  7:57 ` anitha.boyapati at atmel dot com
2011-06-13 14:46 ` jason at gcc dot gnu.org
2011-06-13 19:29 ` rth at gcc dot gnu.org
2011-06-14  7:01 ` anitha.boyapati at atmel dot com
2011-06-14  9:11 ` gjl at gcc dot gnu.org
2011-06-14  9:48 ` gjl at gcc dot gnu.org [this message]
2011-06-14 13:28 ` rth at gcc dot gnu.org
2011-06-14 13:32 ` rth at gcc dot gnu.org
2011-06-14 16:32 ` gjl at gcc dot gnu.org
2011-06-14 19:14 ` rth at gcc dot gnu.org
2011-06-14 19:18 ` rth at gcc dot gnu.org
2011-06-15  2:38 ` anitha.boyapati at atmel dot com
2011-06-15 14:42 ` rth at gcc dot gnu.org
2011-06-16  6:35 ` anitha.boyapati at atmel dot com
2011-06-16  6:38 ` anitha.boyapati at atmel dot com
2011-06-16 13:55 ` rth at gcc dot gnu.org
2011-06-17  7:09 ` anitha.boyapati at atmel dot com
2011-06-17 15:52 ` rth at gcc dot gnu.org
2011-06-17 16:06 ` rth at gcc dot gnu.org
2011-06-20  5:02 ` anitha.boyapati at atmel dot com

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=bug-48459-4-wHokNBVidH@http.gcc.gnu.org/bugzilla/ \
    --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).