public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47154] [4.6 Regression] END= does not work in namelist read Date: Tue, 04 Jan 2011 05:17:00 -0000 [thread overview] Message-ID: <bug-47154-4-bVyHXszE5T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47154-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47154 --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-01-04 05:17:18 UTC --- Created attachment 22893 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22893 A proposed patch The regression was caused by: http://gcc.gnu.org/viewcvs?view=revision&revision=166180 I have attached a patch that passes our current namelist tests. The problem is that we were getting more than one call to generate_error, interfering with the END handler in error.c and even trashing some error messages.
next prev parent reply other threads:[~2011-01-04 5:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-02 21:49 [Bug libfortran/47154] New: " tkoenig at gcc dot gnu.org 2011-01-02 21:49 ` [Bug libfortran/47154] " tkoenig at gcc dot gnu.org 2011-01-03 7:35 ` tkoenig at gcc dot gnu.org 2011-01-03 10:35 ` jakub at gcc dot gnu.org 2011-01-03 14:40 ` jvdelisle at gcc dot gnu.org 2011-01-04 5:17 ` jvdelisle at gcc dot gnu.org [this message] 2011-01-04 14:25 ` jvdelisle at gcc dot gnu.org 2011-01-04 14:53 ` jb at gcc dot gnu.org 2011-01-04 18:24 ` jvdelisle at gcc dot gnu.org 2011-01-05 3:53 ` jvdelisle at gcc dot gnu.org 2011-01-05 4:19 ` jvdelisle at gcc dot gnu.org 2011-01-05 4:24 ` jvdelisle 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-47154-4-bVyHXszE5T@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).