All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4375] New: prevent unused-but-set warning on "ret" in makedevs.c
Date: Sat, 22 Oct 2011 04:04:08 +0000 (UTC)	[thread overview]
Message-ID: <bug-4375-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=4375

           Summary: prevent unused-but-set warning on "ret" in makedevs.c
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: d_mo1234 at yahoo.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 3673
  --> https://bugs.busybox.net/attachment.cgi?id=3673
patch file

The makedevs program assigns "ret", but never reads from it.  (It always
returns 0.)  While using gcc 4.6.0 for an OMAP target, I got an unused-but-set
warning on "ret", which coupled with a -Werror that was set somewhere, bringing
the buildroot compile to a halt.  So I have attached a patch that tests "ret",
and prints out a warning if there were any failures.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2011-10-22  4:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22  4:04 bugzilla at busybox.net [this message]
2011-10-23 17:50 ` [Buildroot] [Bug 4375] prevent unused-but-set warning on "ret" in makedevs.c bugzilla at busybox.net

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-4375-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.