public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001525] New: Fix compiler warnings in bsd_tcpip files. Date: Wed, 07 Mar 2012 18:46:00 -0000 [thread overview] Message-ID: <bug-1001525-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001525 Summary: Fix compiler warnings in bsd_tcpip files. Product: eCos Version: CVS Platform: All OS/Version: Other Status: NEW Severity: minor Priority: low Component: TCP/IP AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: grant.b.edwards@gmail.com CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=1625) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1625) Fix compiler warnings in several bsd_tcpip files. This patch fixes compiler warnings in several bsd_tcpip files generated by gcc 4.6.2 (mostly about variables that are set and never referenced). This patch doesn't deal with files under netinet6 - they will be handled in another patch. Variables that were set but only referenced in conditionally compiled code are marked with CYGBLD_ATTRIB_UNUSED. Variables that were set but never referenced at all have been removed. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2012-03-07 18:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-07 18:46 bugzilla-daemon [this message] 2012-03-09 3:50 ` [Bug 1001525] " bugzilla-daemon 2012-03-09 15:03 ` bugzilla-daemon 2012-03-09 19:25 ` bugzilla-daemon -- strict thread matches above, loose matches on Subject: below -- 2012-03-07 18:46 [Bug 1001525] New: " bugzilla-daemon
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-1001525-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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).