public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tjvries at xs4all dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/31230] debug information depends on gc parameters Date: Mon, 21 Jun 2010 10:20:00 -0000 [thread overview] Message-ID: <20100621102000.9146.qmail@sourceware.org> (raw) In-Reply-To: <bug-31230-230@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from tjvries at xs4all dot nl 2010-06-21 10:20 ------- Created an attachment (id=20953) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20953&action=view) minimal test case of 14 lines, cut down from varasm.i I also ran into this bug, while building gcc 4.3.5 for x86_64-unknown-linux-gnu with make {CFLAGS,BOOT_CFLAGS,STAGE1_CFLAGS}=\"-g3\ -O0\ -dH\". I managed to minimized the test case down to 14 lines. The difference in debug info can be reproduced using: ... $ cc1 varasm.i -O0 -g -quiet -o varasm.s $ cc1 varasm.i -O0 -g -quiet -o varasm.s.0.0 --param ggc-min-expand=0 --param ggc-min-heapsize=0 ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31230
next prev parent reply other threads:[~2010-06-21 10:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-16 20:25 [Bug debug/31230] New: " jsm28 at gcc dot gnu dot org 2007-03-16 20:26 ` [Bug debug/31230] " jsm28 at gcc dot gnu dot org 2007-03-30 21:44 ` wilson at gcc dot gnu dot org 2007-03-30 21:49 ` wilson at gcc dot gnu dot org 2010-06-21 10:20 ` tjvries at xs4all dot nl [this message] 2010-06-21 10:32 ` tjvries at xs4all dot nl [not found] <bug-31230-4@http.gcc.gnu.org/bugzilla/> 2022-12-01 1:42 ` pinskia 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=20100621102000.9146.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: linkBe 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).