Clang PCH性能比标头差吗?

如何解决Clang PCH性能比标头差吗?

我有一组包含在源文件中的标头,这些标头很少/从未更改。解析/解析使用标头的频繁更改的源文件(IDE用例)花费的时间太长(几秒钟)。为了提高性能,我想使用Clang PCH。请注意,我要在Android上以“发布”模式(肯定达到99%)编译libclang(不是最新版本)。

我一直遵循answer to a similar question,但与标头解析(带有100000个#define宏的人工标头)相比,使用PCH的性能要差3倍:

2020-08-11 12:03:53.265 19767-19788 W/TranslationUnitTest: PCH parse time: 0.462277
2020-08-11 12:03:53.265 19767-19788 W/TranslationUnitTest: 0 diagnostics
2020-08-11 12:03:55.768 19767-19788 W/TranslationUnitTest: Source parse time: 1.456947
2020-08-11 12:03:55.768 19767-19788 W/TranslationUnitTest: 0 diagnostics

Java源代码(在Android Instrumentation测试中运行):

final Context context = InstrumentationRegistry.getInstrumentation().getTargetContext();

// create PCH
dir = new File(context.getCacheDir(),String.valueOf(Math.abs(new Random().nextLong())));
dir.mkdirs();

deeperHeaderFile = new File(dir,"deeperHeader.h");
StringBuilder sb = new StringBuilder("#define VAL 1 ");
for (int i=0; i<100000; i++) {
    sb.append("\n");
    sb.append("#define VAL" + i + " " + i);
}
setFileContent(deeperHeaderFile,sb.toString());

headerFile = new File(dir,"header.hxx");
setFileContent(headerFile,"#include \"deeperHeader.h\"");

pchFile = new File(dir,"header.pch");

sourceFile = new File(dir,"source.cpp");
setFileContent(sourceFile,"#include \"header.hxx\"\nint main() { return VAL; }");

// C++ test
Clang.testPch(
    pchFile.getAbsolutePath(),headerFile.getAbsolutePath(),deeperHeaderFile.getAbsolutePath(),sourceFile.getAbsolutePath());

C ++源代码:

class Timer {
public:
    Timer () {
      reset();
    }

    double get () {
      struct timeval now;
      gettimeofday (&now,NULL);

      return now.tv_sec - start_.tv_sec + 1e-6 * (now.tv_usec - start_.tv_usec);
    }

    void reset () {
      gettimeofday (&start_,NULL);
    }

private:
    struct timeval start_;
};

void displayDiagnostics(CXTranslationUnit TU) {
  if (TU == 0) {
    std::cerr << "Parsing error!" << std::endl;
    return;
  }

  int numDiagnostics = clang_getNumDiagnostics (TU);

  __android_log_print(ANDROID_LOG_WARN,TAG,"%d diagnostics",numDiagnostics);

  for (int i=0 ; i<numDiagnostics ; ++i) {
    auto diagnostic = clang_getDiagnostic(TU,i);
    auto string = clang_formatDiagnostic(diagnostic,clang_defaultDiagnosticDisplayOptions());
    auto cString = clang_getCString(string);

    __android_log_print(ANDROID_LOG_WARN,"diag #%d: %s",i,cString);

    clang_disposeString(string);
    clang_disposeDiagnostic(diagnostic);
  }
}

JNIEXPORT void JNICALL Clang_testPch(
    JNIEnv *env,jclass clazz,jstring jPchFilename,jstring jHeaderFilename,jstring jDeeperHeaderFilename,jstring jSourceFilename) {

  char *cPchFilename = string_copy(env,jPchFilename);
  char *cHeaderFilename = string_copy(env,jHeaderFilename);
  char *cDeeperHeaderFilename = string_copy(env,jDeeperHeaderFilename);
  char *cSourceFilename = string_copy(env,jSourceFilename);

  auto Idx = clang_createIndex (0,0);
  CXTranslationUnit TU;
  Timer t;

  {
    char const *args[] = { "-xc++",cHeaderFilename };
    int nargs = 2;

    t.reset();
    TU = clang_parseTranslationUnit(Idx,args,nargs,CXTranslationUnit_ForSerialization);
    auto pchParsetime = t.get();
    __android_log_print(ANDROID_LOG_WARN,"PCH parse time: %f",pchParsetime);
    displayDiagnostics(TU);
    clang_saveTranslationUnit(TU,cPchFilename,clang_defaultSaveOptions(TU));
    clang_disposeTranslationUnit(TU);
  }

  {
    char const *args[] = { "-include-pch",cSourceFilename };
    int nargs = 3;

    t.reset();
    TU = clang_createTranslationUnitFromSourceFile(Idx,0);
    auto parseTime = t.get();
    __android_log_print(ANDROID_LOG_WARN,"Source parse time: %f",parseTime);
    displayDiagnostics(TU);
    clang_disposeTranslationUnit(TU);
  }

  // release
  delete []cPchFilename;
  delete []cHeaderFilename;
  delete []cDeeperHeaderFilename;
  delete []cSourceFilename;
}

我相信文件是用Java编写的(原始原因是我具有clang绑定,并且Java代码具有相同的[坏]性能,所以我更改了要在C ++中测试的代码)

我想念什么吗?有愚蠢的错误吗?有什么建议吗?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-