public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29313]  New: [middle-end]Possible bogus warning: argument 'type' might be clobbered
Date: Sun, 01 Oct 2006 23:46:00 -0000	[thread overview]
Message-ID: <bug-29313-10743@http.gcc.gnu.org/bugzilla/> (raw)

This warning occurs for libgfortran/io/list_read.c (list_formatted_read_scalar)

It can be cleared up using the 'volatile' on the argument 'type' shown here. 
'type' is never changed anywhere.

static void
list_formatted_read_scalar (st_parameter_dt *dtp, volatile bt type, void *p,
int kind,
                            size_t size)
{
  char c;
  int m;
  jmp_buf eof_jump;

  dtp->u.p.namelist_mode = 0;

  dtp->u.p.eof_jump = &eof_jump;
  if (setjmp (eof_jump))
    {
      generate_error (&dtp->common, ERROR_END, NULL);
      goto cleanup;
    }

 --- snip ---


-- 
           Summary: [middle-end]Possible bogus warning: argument 'type'
                    might be clobbered
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jvdelisle at gcc dot gnu dot org
  GCC host triplet: linux-ppc, darwin-ppc, linux-x86-64


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29313


             reply	other threads:[~2006-10-01 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 23:46 jvdelisle at gcc dot gnu dot org [this message]
2006-10-01 23:50 ` [Bug c/29313] " jvdelisle at gcc dot gnu dot org
2009-12-29 15:49 ` [Bug middle-end/29313] " fxcoudert 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-29313-10743@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: link
Be 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).