public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] opensm: fixing unused-but-set warnings in compilation
Date: Fri, 29 Jul 2011 12:15:03 +0300	[thread overview]
Message-ID: <20110729091503.GD2055@calypso.mtl.com> (raw)
In-Reply-To: <20110711174518.GB2084-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On 20:45 Mon 11 Jul     , Alex Netes wrote:
> Latest GCC 4.6 include -Wunused-* flags as part of the -Wall flag, causing
> many warnings during OpenSM compilation.
> 
> This patch series tries to clean these warnings.
> Where possible, unused variables were just deleted.
> In other cases where some variables are used only when specific compilation
> flags are used (DEBUG, VENDOR_RMPP_SUPPORT, etc') this variables marked as
> __attribute__((unused)) meaning that the variable is meant to be possibly
> unused.
> 
> More info:
> http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
> http://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/Variable-Attributes.html#Variable-Attributes
> 
> 
> -- Alex
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

Applied.
-- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-07-29  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 17:45 [PATCH 0/3] opensm: fixing unused-but-set warnings in compilation Alex Netes
     [not found] ` <20110711174518.GB2084-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2011-07-29  9:15   ` Alex Netes [this message]

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=20110729091503.GD2055@calypso.mtl.com \
    --to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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