1 | /**************************************************************************** |
2 | ** |
3 | ** Copyright (C) 2017 The Qt Company Ltd. |
4 | ** Contact: https://www.qt.io/licensing/ |
5 | ** |
6 | ** This file is part of the QtQml module of the Qt Toolkit. |
7 | ** |
8 | ** $QT_BEGIN_LICENSE:LGPL$ |
9 | ** Commercial License Usage |
10 | ** Licensees holding valid commercial Qt licenses may use this file in |
11 | ** accordance with the commercial license agreement provided with the |
12 | ** Software or, alternatively, in accordance with the terms contained in |
13 | ** a written agreement between you and The Qt Company. For licensing terms |
14 | ** and conditions see https://www.qt.io/terms-conditions. For further |
15 | ** information use the contact form at https://www.qt.io/contact-us. |
16 | ** |
17 | ** GNU Lesser General Public License Usage |
18 | ** Alternatively, this file may be used under the terms of the GNU Lesser |
19 | ** General Public License version 3 as published by the Free Software |
20 | ** Foundation and appearing in the file LICENSE.LGPL3 included in the |
21 | ** packaging of this file. Please review the following information to |
22 | ** ensure the GNU Lesser General Public License version 3 requirements |
23 | ** will be met: https://www.gnu.org/licenses/lgpl-3.0.html. |
24 | ** |
25 | ** GNU General Public License Usage |
26 | ** Alternatively, this file may be used under the terms of the GNU |
27 | ** General Public License version 2.0 or (at your option) the GNU General |
28 | ** Public license version 3 or any later version approved by the KDE Free |
29 | ** Qt Foundation. The licenses are as published by the Free Software |
30 | ** Foundation and appearing in the file LICENSE.GPL2 and LICENSE.GPL3 |
31 | ** included in the packaging of this file. Please review the following |
32 | ** information to ensure the GNU General Public License requirements will |
33 | ** be met: https://www.gnu.org/licenses/gpl-2.0.html and |
34 | ** https://www.gnu.org/licenses/gpl-3.0.html. |
35 | ** |
36 | ** $QT_END_LICENSE$ |
37 | ** |
38 | ****************************************************************************/ |
39 | |
40 | #include "qv4functiontable_p.h" |
41 | #include "qv4function_p.h" |
42 | |
43 | #include <assembler/MacroAssemblerCodeRef.h> |
44 | |
45 | #include <QtCore/qfile.h> |
46 | #include <QtCore/qcoreapplication.h> |
47 | |
48 | QT_BEGIN_NAMESPACE |
49 | |
50 | namespace QV4 { |
51 | |
52 | void generateFunctionTable(Function *function, JSC::MacroAssemblerCodeRef *codeRef) |
53 | { |
54 | // This implements writing of JIT'd addresses so that perf can find the |
55 | // symbol names. |
56 | // |
57 | // Perf expects the mapping to be in a certain place and have certain |
58 | // content, for more information, see: |
59 | // https://github.com/torvalds/linux/blob/master/tools/perf/Documentation/jit-interface.txt |
60 | static bool doProfile = !qEnvironmentVariableIsEmpty(varName: "QV4_PROFILE_WRITE_PERF_MAP" ); |
61 | if (Q_UNLIKELY(doProfile)) { |
62 | static QFile perfMapFile(QString::fromLatin1(str: "/tmp/perf-%1.map" ) |
63 | .arg(a: QCoreApplication::applicationPid())); |
64 | static const bool isOpen = perfMapFile.open(flags: QIODevice::WriteOnly); |
65 | if (!isOpen) { |
66 | qWarning(msg: "QV4::JIT::Assembler: Cannot write perf map file." ); |
67 | doProfile = false; |
68 | } else { |
69 | const void *address = codeRef->code().executableAddress(); |
70 | perfMapFile.write(data: QByteArray::number(reinterpret_cast<quintptr>(address), base: 16)); |
71 | perfMapFile.putChar(c: ' '); |
72 | perfMapFile.write(data: QByteArray::number(static_cast<qsizetype>(codeRef->size()), base: 16)); |
73 | perfMapFile.putChar(c: ' '); |
74 | perfMapFile.write(data: Function::prettyName(function, address).toUtf8()); |
75 | perfMapFile.putChar(c: '\n'); |
76 | perfMapFile.flush(); |
77 | } |
78 | } |
79 | } |
80 | |
81 | void destroyFunctionTable(Function *function, JSC::MacroAssemblerCodeRef *codeRef) |
82 | { |
83 | Q_UNUSED(function); |
84 | Q_UNUSED(codeRef); |
85 | |
86 | // It's not advisable to remove things from the perf map file, as it's primarily used to analyze |
87 | // a trace after the application has terminated. We want to know about all functions that were |
88 | // ever jitted then. If the memory ranges overlap, we will have a problem when analyzing the |
89 | // trace. The JIT should try to avoid this. |
90 | } |
91 | |
92 | size_t exceptionHandlerSize() |
93 | { |
94 | return 0; |
95 | } |
96 | |
97 | } // QV4 |
98 | |
99 | QT_END_NAMESPACE |
100 | |