public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/35853] New: [4.4 Regression] -d is still referenced in some cases (documentation) Date: Mon, 07 Apr 2008 01:18:00 -0000 [thread overview] Message-ID: <bug-35853-6528@http.gcc.gnu.org/bugzilla/> (raw) When I noticed PR 35843, I saw that some -dletter was still referenced in some cases: -dv For each of the other indicated dump files (either with -d or -fdump-rtl-pass), dump a representation of the control flow graph suitable for viewing with VCG to file.pass.vcg. -dx Just generate RTL for a function instead of compiling it. Usually used with `r' (-fdump-rtl-expand). Also the sentence above this list is incorrect as the long options don't have a -d letter any more: Most debug dumps can be enabled either passing a letter to the -d option, or with a long -fdump-rtl switch; here are the possible letters for use in letters and pass, and their meanings: -- Summary: [4.4 Regression] -d is still referenced in some cases (documentation) Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35853
next reply other threads:[~2008-04-07 1:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-07 1:18 pinskia at gcc dot gnu dot org [this message] 2008-04-07 1:24 ` [Bug middle-end/35853] " pinskia at gcc dot gnu dot org 2008-04-07 1:25 ` pinskia at gcc dot gnu dot org 2008-04-20 20:45 ` rguenth at gcc dot gnu dot org 2008-06-15 22:50 ` hubicka at gcc dot gnu dot org 2008-10-21 10:22 ` jakub at gcc dot gnu dot org 2008-10-21 23:09 ` jakub at gcc dot gnu dot org 2008-10-21 23:11 ` jakub at gcc dot gnu dot 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-35853-6528@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).