public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm: fixing compilation issues in some header files
Date: Wed, 02 Jun 2010 00:18:56 +0300	[thread overview]
Message-ID: <4C057940.1020106@dev.mellanox.co.il> (raw)
In-Reply-To: <20100601192205.GV28549@me>

On 01-Jun-10 10:22 PM, Sasha Khapyorsky wrote:
> Hi Yevgeny,
>
> On 14:58 Tue 01 Jun     , Yevgeny Kliteynik wrote:
>>
>> On 24-Mar-10 5:50 PM, Yevgeny Kliteynik wrote:
>>> All the compilation issues refer to implicit casting
>>> from "void*" to "some_struct_t*"
>>
>> This was detected when compiling a code that includes these
>> headers with g++ compiler. The headers should be able to compile
>> by g++ (they have 'extern "C"').
>
> Well let's apply the patch since we have 'extern "C"'.
>
> But this raises another question. All affected header files are OpenSM
> internals and OpenSM is written in C (not C++). So why 'extern "C"'
> should be here at all? Do you know?
>
>> But the problem is not only
>> with g++ - it is with typing in general. I may be wrong, but I
>> feel that every new gcc version is more strongly typed.
>
> AFAIR (anytype *) to (void *) casting is not needed (doing implicitly)
> in C and this is already part of some basic standards.

True, but the problem is not (anytype *) to (void *) casting.
It's the other way around: (void *) to (anytype *) casting.

-- Yevgeny
  
> Sasha
>

--
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

  reply	other threads:[~2010-06-01 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 15:50 [PATCH] opensm: fixing compilation issues in some header files Yevgeny Kliteynik
     [not found] ` <4BAA34B2.9060808-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-06-01 11:58   ` Yevgeny Kliteynik
     [not found]     ` <4C04F5E7.8030904-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-06-01 19:22       ` Sasha Khapyorsky
2010-06-01 21:18         ` Yevgeny Kliteynik [this message]
     [not found]           ` <4C057940.1020106-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-06-02  1:03             ` Sasha Khapyorsky
2010-06-02  7:29               ` Yevgeny Kliteynik
     [not found]                 ` <4C06084D.3070101-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2010-06-02 15:18                   ` Sasha Khapyorsky
2010-06-02 15:30                     ` Hal Rosenstock
     [not found]                       ` <AANLkTinyMA8WyFPee755nelj9gxJKTP7mQChYlDkUF4J-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-02 16:05                         ` Sasha Khapyorsky
2010-06-02 16:28                         ` Roland Dreier
2010-06-01 19:23   ` Sasha Khapyorsky

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=4C057940.1020106@dev.mellanox.co.il \
    --to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sashak-smomgflXvOZWk0Htik3J/w@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