From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Garrett Cooper <yanegomi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] Avoid linker error with clang 3.0
Date: Sun, 09 Dec 2012 14:23:37 +0100 [thread overview]
Message-ID: <50C490D9.1000301@acm.org> (raw)
In-Reply-To: <alpine.BSF.2.00.1212090306300.64779-Fqwm7F1mg36Nj9Bq2fkWzw@public.gmane.org>
On 12/09/12 12:07, Garrett Cooper wrote:
> It seems that there's a bug when linking inlined functions with clang; this
> issue will need to be upstreamed and reverified with clang 3.2.
>
> Signed-off-by: Garrett Cooper <yanegomi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> osmtest/osmtest.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/osmtest/osmtest.c b/osmtest/osmtest.c
> index 68b0e40..4f56106 100644
> --- a/osmtest/osmtest.c
> +++ b/osmtest/osmtest.c
> @@ -3068,7 +3068,7 @@ Exit:
> return (status);
> }
>
> -inline uint32_t osmtest_path_rec_key_get(IN const ib_path_rec_t * const p_rec)
> +static uint32_t osmtest_path_rec_key_get(IN const ib_path_rec_t * const p_rec)
> {
> return (p_rec->dlid << 16 | p_rec->slid);
> }
Why was the "inline" keyword dropped ? You didn't explain that in the patch description.
Bart.
--
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
next prev parent reply other threads:[~2012-12-09 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 11:07 [PATCH 3/3] Avoid linker error with clang 3.0 Garrett Cooper
[not found] ` <alpine.BSF.2.00.1212090306300.64779-Fqwm7F1mg36Nj9Bq2fkWzw@public.gmane.org>
2012-12-09 13:23 ` Bart Van Assche [this message]
[not found] ` <50C490D9.1000301-HInyCGIudOg@public.gmane.org>
2012-12-09 19:06 ` Garrett Cooper
[not found] ` <CAGH67wS1P43ssD+-VFyCupLw3CT8U73wT-aT6N2AS5ddWApAoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-09 19:28 ` Garrett Cooper
[not found] ` <CAGH67wQt48zEp0KiN44w=wfYZy+FA6oc=ehuAHUL2QBo=A1nhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-09 21:47 ` Garrett Cooper
[not found] ` <ABB9B291-3AB5-4AE6-8CE2-5FE691E1AE02-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-12-10 6:06 ` Jason Gunthorpe
[not found] ` <20121210060600.GA30472-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-12-10 6:12 ` Garrett Cooper
[not found] ` <CAGH67wQ9ER9JLHR9ZKmzwMaGuV4m_5LdsHbKZvfYw1ekojik2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-11 10:08 ` Garrett Cooper
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=50C490D9.1000301@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yanegomi-Re5JQEeQqe8AvxtiuMwx3w@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 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.