public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/55041] prettyprinting/shared_ptr & cxx11 fails on some platforms
Date: Sat, 17 Nov 2012 13:27:00 -0000	[thread overview]
Message-ID: <bug-55041-4-SINhJz0Gpa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55041-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #14 from Mark Wielaard <mark at gcc dot gnu.org> 2012-11-17 13:27:03 UTC ---
>>     dwarf2out.c: For DWARF 4+, output DW_AT_high_pc as constant offset.
>> 
>> 
>> This required a gdb change.
>
> Ah, that should be in http://gcc.gnu.org/gcc-4.8/changes.html then. Mark?

How about something like:

diff -u -r1.57 changes.html
--- htdocs/gcc-4.8/changes.html    14 Nov 2012 04:45:41 -0000    1.57
+++ htdocs/gcc-4.8/changes.html    17 Nov 2012 13:24:24 -0000
@@ -53,6 +53,14 @@
 <h2>General Optimizer Improvements (and Changes)</h2>

   <ul>
+    <li>DWARF4 is now the default when generating DWARF debug information.
+      When -g is used on a platform that uses DWARF debugging information,
+      GCC will now default to -gdwarf-4 -fno-debug-types-section.
+      GDB 7.5, Valgrind 3.8.0 and elfutils 0.154 debug information consumers
+      support DWARF4 by default. Before GCC 4.8 the default version used
+      was DWARF2. To make gcc 4.8 generate an older DWARF version use -g
+      together with -gdwarf-2 or -gdwarf-3.
+    </li>
     <li>A new general optimization level, <code>-Og</code>, has been
       introduced.  It addresses the need for fast compilation and a
       superior debugging experience while providing a reasonable level

On which list should website changes be proposed?


  parent reply	other threads:[~2012-11-17 13:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 18:59 [Bug libstdc++/55041] New: " bkoz at gcc dot gnu.org
2012-10-23 20:54 ` [Bug libstdc++/55041] " redi at gcc dot gnu.org
2012-10-23 21:11 ` paolo.carlini at oracle dot com
2012-10-24 10:43 ` paolo.carlini at oracle dot com
2012-10-24 11:21 ` redi at gcc dot gnu.org
2012-10-24 11:59 ` paolo.carlini at oracle dot com
2012-10-28 12:54 ` redi at gcc dot gnu.org
2012-10-28 13:21 ` redi at gcc dot gnu.org
2012-10-28 13:27 ` redi at gcc dot gnu.org
2012-10-28 13:37 ` redi at gcc dot gnu.org
2012-10-28 13:57 ` redi at gcc dot gnu.org
2012-11-16 18:14 ` redi at gcc dot gnu.org
2012-11-16 20:47 ` tromey at gcc dot gnu.org
2012-11-17  0:48 ` redi at gcc dot gnu.org
2012-11-17 13:27 ` mark at gcc dot gnu.org [this message]
2012-11-20  0:10 ` redi at gcc dot gnu.org
2013-01-24 18:52 ` tromey at gcc dot gnu.org
2013-01-24 18:55 ` bkoz at gcc dot gnu.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=bug-55041-4-SINhJz0Gpa@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).