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 target/50566] New: [avr]: Add support for better logging similar to -mdeb Date: Thu, 29 Sep 2011 11:00:00 -0000 [thread overview] Message-ID: <bug-50566-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50566 Bug #: 50566 Summary: [avr]: Add support for better logging similar to -mdeb Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: target AssignedTo: gjl@gcc.gnu.org ReportedBy: gjl@gcc.gnu.org CC: eric.weddington@atmel.com Target: avr -mdeb lets avr-gcc print log information as a file is being compiled but it's hard to depict from the information - what function is just being compiled - what pass gcc is in - ... Forover, it would be nice to have a printf-like function to print formatted output together with trees, RTXes, register classes, rtx codes, etc.
next reply other threads:[~2011-09-29 10:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-29 11:00 gjl at gcc dot gnu.org [this message] 2011-09-29 11:23 ` [Bug target/50566] " gjl at gcc dot gnu.org 2011-09-29 11:58 ` gjl at gcc dot gnu.org 2011-09-29 16:41 ` gjl at gcc dot gnu.org 2011-09-29 16:47 ` gjl at gcc dot gnu.org 2011-09-30 15:49 ` gjl at gcc dot gnu.org 2011-10-04 8:24 ` gjl at gcc dot gnu.org 2011-11-25 11:32 ` gjl 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-50566-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).