public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53472] New: contrib/compare-debug should strip out .comment section Date: Thu, 24 May 2012 13:40:00 -0000 [thread overview] Message-ID: <bug-53472-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53472 Bug #: 53472 Summary: contrib/compare-debug should strip out .comment section Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com From http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00284.html http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53197 Now, as to why for me BUILD_CONFIG isn't bootstrap-debug: configure.ac activates this by default, but then checks if contrib/compare-debug actually works for comparing a debug and non-debug .o file. And for SuSE systems it doesn't, because our system compilers encode some command line options (among them -g) into a special .comment section. Any chance you could adjust the script to strip out the .comment section you mentioned elsewhere, so that you get faster bootstrap with bootstrap-debug testing too?
next reply other threads:[~2012-05-24 13:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-24 13:40 hjl.tools at gmail dot com [this message] 2012-05-24 14:03 ` [Bug bootstrap/53472] " hjl.tools at gmail dot com 2012-05-25 12:31 ` hjl at gcc dot gnu.org 2012-05-25 12:48 ` hjl.tools at gmail 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-53472-4@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: 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).