[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-dev
Subject:    [llvm-dev] Removing the deprecated __xray_log_init API from XRay FDR logging implementation
From:       Petr Hosek via llvm-dev <llvm-dev () lists ! llvm ! org>
Date:       2018-08-31 20:14:40
Message-ID: CABBv4TYd_2jiCOYaYSDwR_jT5U2z=97ybFPqZS7A0Hyh3xEShQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I'd like to remove __xray_log_init function together with FDRLoggingOptions
and BasicLoggingOptions structs from the XRay FDR logging interface.

These functions have been marked as deprecated since May 4, 2018. Now that
7.0 has been branched, I think it should be safe to remove them and it'd
make further refactoring that I'm currently working on much easier, but I
want to check that all users have already moved away from this API and
won't be broken by this change? If nobody raises any objections, I'd send
out a change to remove this API.

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">I&#39;d \
like to remove  __xray_log_init function together with FDRLoggingOptions and  \
BasicLoggingOptions structs from the  XRay FDR logging interface.</div><div \
dir="ltr"><br></div><div dir="ltr">These functions have been marked as deprecated \
since May 4, 2018. Now that 7.0 has been branched, I think it should be safe to \
remove them and it&#39;d make further refactoring that I&#39;m currently working on \
much easier, but I want to check that all users have already moved away from this API \
and won&#39;t be broken by this change? If nobody raises any objections, I&#39;d send \
out a change to remove this API.</div></div></div></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
LLVM Developers mailing list
llvm-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


[prev in list] [next in list] [prev in thread] [next in thread]