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 1001504] New: Fix CYG_REFERENCE_OBJECT macro, add CYGBLD_ATTRIB_UNUSED macro
Date: Fri, 02 Mar 2012 16:42:00 -0000	[thread overview]
Message-ID: <bug-1001504-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=1001504

           Summary: Fix CYG_REFERENCE_OBJECT macro, add
                    CYGBLD_ATTRIB_UNUSED macro
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: Other
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: grant.b.edwards@gmail.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


With gcc 4.6, the "used" attribute only applies to functions, so to
fix compiler warnings conditionally remove it from the
CYG_REFERENCE_OBJECT() macro for gcc >= 4.6.

Define a new CYGBLD_ATTRIB_UNUSED attribute macro that we can use to
tell the compiler that we already know that certain variables may be
unused or set but never referenced (generally when asserts or debugging
are turned off at build-time).

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


             reply	other threads:[~2012-03-02 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 16:42 bugzilla-daemon [this message]
2012-03-03  4:31 ` [Bug 1001504] " bugzilla-daemon
2012-03-03  4:31 ` bugzilla-daemon
2012-03-02 16:42 [Bug 1001504] 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-1001504-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: 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).