public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45629] libgfortran/io/list_read.c:1872:10: warning: variable 'elem' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered] Date: Sat, 16 Oct 2010 22:07:00 -0000 [thread overview] Message-ID: <20101016220700.NDV1-pn9tO7YXF334Am2MfZ242MbPDbY-6cUM6z-RJw@z> (raw) In-Reply-To: <bug-45629-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45629 --- Comment #1 from Janne Blomqvist <jb at gcc dot gnu.org> 2010-10-16 22:07:19 UTC --- Created attachment 22068 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22068 Preliminary patch Preliminary patch for getting rid of setjmp/longjmp, instead using an errno-style flag variable.
next parent reply other threads:[~2010-10-16 22:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45629-4@http.gcc.gnu.org/bugzilla/> 2010-10-16 22:07 ` jb at gcc dot gnu.org [this message] 2010-10-16 22:10 ` jb at gcc dot gnu.org 2010-10-16 23:22 ` jvdelisle at gcc dot gnu.org 2010-11-01 7:28 ` jb at gcc dot gnu.org 2010-11-01 23:33 ` jb at gcc dot gnu.org 2010-11-02 12:56 ` jb at gcc dot gnu.org 2010-11-04 19:40 ` jb 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=20101016220700.NDV1-pn9tO7YXF334Am2MfZ242MbPDbY-6cUM6z-RJw@z \ --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).