[Development] Requesting Feature Freeze exception for CTF tracing backend

[Volker Hilsheimer]

Agree. There are a couple of open design questions in the comments, but this functionality will enable better profiling support on top of Qt 6.5, and should otherwise not be in the way. We should be able iterate over the implementation without any unpredictable side effects.

The general tracing functionality is opt-in, also the new common trace format support, and there are no new APIs added, so no impact on the upcoming header review.

Nevertheless, this comes with build system changes and a bunch of new code, so would be great if this could be merged soon after the break, at the latest mid January.

Volker


> On 12 Dec 2022, at 20:05, Tuukka Turunen via Development <development at qt-project.org> wrote:
> 
> Hi,
> 
> It would be good to have these in. 
> 
> Yours,
> 
> Tuukka
> 
> Lähettäjä: Development <development-bounces at qt-project.org> käyttäjän Antti Määttä via Development <development at qt-project.org> puolesta
> Lähetetty: perjantaina, joulukuuta 9, 2022 3:41 ip.
> Vastaanottaja: development at qt-project.org <development at qt-project.org>
> Aihe: [Development] Requesting Feature Freeze exception for CTF tracing backend 
>   Hi,
>   Following two changes CTF tracing backend (https://bugreports.qt.io/browse/QTBUG-106399, https://codereview.qt-project.org/c/qt/qtbase/+/440749) and
> related tool for generating tracepoints files (https://bugreports.qt.io/browse/QTBUG-107238, https://codereview.qt-project.org/c/qt/qtbase/+/436672) were not finished on time before feature freeze. 
>   The first change extends the existing Q_TRACE mechanism with a new platform independent backend based on CTF format. The second one is a tool that makes it easier to generate tracepoint files for the existing tracegen tool.
>   The changes are required for application level profiling and are the basis for further development in that area. It would be beneficial to get those changes in for the LTS 6.5 release.
>   The changes are currently in review and should not have work left in them unless something comes up based on new comments.
>   Regards,
> Antti Määttä
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development