public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35015] New: missing cleanup-modules directive in testsuite/gfortran* Date: Tue, 29 Jan 2008 14:25:00 -0000 [thread overview] Message-ID: <bug-35015-11811@http.gcc.gnu.org/bugzilla/> (raw) $ wget -P gcc/contrib/ \ http://uclibc.org/~aldot/gcc/gfortran.dg-final.cleanup-mods.awk $ chmod +x gcc/contrib/gfortran.dg-final.cleanup-mods.awk $ cd gcc/testsuite $ $ for i in $(grep --exclude='*.svn*' -rl dg-do gfortran*); do ../contrib/gfortran.dg-final.cleanup-mods.awk $i;done 2> /dev/null This scripts emits on stdout a diagnostic message about a) wrong encoding in testcases (CRLF) b) missing cleanup-module directives On stderr, this scripts emits sed scripts to automagically a) fix the wrong encoding b) add missing cleanup-module directives. I put it into public domain, but this can be changes if required. IMHO it would be handy to have this script in gcc/contrib -- Summary: missing cleanup-modules directive in testsuite/gfortran* Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: aldot at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35015
next reply other threads:[~2008-01-29 14:11 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-29 14:25 aldot at gcc dot gnu dot org [this message] 2008-01-29 15:57 ` [Bug fortran/35015] " burnus at gcc dot gnu dot org 2008-01-29 17:10 ` aldot at gcc dot gnu dot org 2008-01-29 20:35 ` burnus at gcc dot gnu dot org 2008-01-29 21:03 ` rep dot dot dot nop at gmail dot com 2008-01-29 21:57 ` aldot at gcc dot gnu dot org 2008-02-03 14:35 ` fxcoudert at gcc dot gnu dot org 2009-01-03 22:48 ` dfranke 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-35015-11811@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).