public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/13756] [tree-ssa] documentation missing Date: Fri, 13 Aug 2004 10:08:00 -0000 [thread overview] Message-ID: <20040813100838.28910.qmail@sourceware.org> (raw) In-Reply-To: <20040120032630.13756.dnovillo@gcc.gnu.org> ------- Additional Comments From jsm28 at gcc dot gnu dot org 2004-08-13 10:08 ------- Functions without comments above them: gimple-low.c: lower_return_expr gimplify.c: gimple_push_bind_expr gimple_pop_bind_expr gimple_current_bind_expr get_formal_tmp_var gimple_add_tmp_var annotate_one_with_locus annotate_all_with_locus unmark_visited_r gimplify_case_label_expr shortcut_cond_expr tree-alias-ander.c: get_ref pta_make_lam print_out_result tree-alias-common.c: alias_get_name tree-alias-type.c: alias_var_new_with_aterm tree-browser.c: TB_current_chain_node tree-cfg.c: execute_build_cfg remove_useless_stmts_cond remove_useless_stmts_tf remove_useless_stmts_tc remove_useless_stmts_bind remove_useless_stmts_goto remove_useless_stmts_label remove_useless_stmts_1 remove_useless_stmts compute_dominance_frontiers tree_purge_dead_eh_edges tree_purge_all_dead_eh_edges Many more files not checked, but you get the idea. All functions must have comments above them describing what the function does, all its parameters, and its return value if any. A reasonable approximation to a list of undocumented functions in a file can be obtained with perl -ne 'if (/^\/\*/) { $sc = 1; }; if (/^}\n$/) { $sc = 0; }; if (/^[a-z]/ && !$sc) { print $_; }' <source-file.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13756
next prev parent reply other threads:[~2004-08-13 10:08 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-20 3:26 [Bug other/13756] New: tree-ssa documentation missing in the internals manual dnovillo at gcc dot gnu dot org 2004-01-20 3:28 ` [Bug other/13756] [tree-ssa] " pinskia at gcc dot gnu dot org 2004-01-20 3:30 ` dnovillo at redhat dot com 2004-01-20 3:31 ` pinskia at gcc dot gnu dot org 2004-01-28 1:39 ` bosch at gcc dot gnu dot org 2004-03-15 19:09 ` dberlin at gcc dot gnu dot org 2004-04-29 19:37 ` bosch at gcc dot gnu dot org 2004-05-04 4:01 ` dnovillo at gcc dot gnu dot org 2004-05-14 13:26 ` [Bug tree-optimization/13756] [tree-ssa] documentation missing jsm28 at gcc dot gnu dot org 2004-05-21 21:38 ` pinskia at gcc dot gnu dot org 2004-05-31 11:49 ` jsm28 at gcc dot gnu dot org 2004-08-13 10:08 ` jsm28 at gcc dot gnu dot org [this message] 2005-01-05 2:10 ` pinskia at gcc dot gnu dot org 2005-04-21 5:01 ` mmitchel at gcc dot gnu dot org 2005-07-08 1:38 ` mmitchel at gcc dot gnu dot org 2005-09-27 18:21 ` pinskia at gcc dot gnu dot org [not found] <bug-13756-91@http.gcc.gnu.org/bugzilla/> 2005-12-27 0:38 ` pinskia at gcc dot gnu dot org 2007-09-05 19:48 ` rask at gcc dot gnu dot org [not found] <bug-13756-4@http.gcc.gnu.org/bugzilla/> 2021-05-31 0:35 ` pinskia at gcc dot gnu.org 2024-03-26 4:21 ` egallager 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=20040813100838.28910.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).