Thanks @Sameeranjoshi! Let me import this.

I was trying to dump the CFG from bolt and was trying to analyze it visually using below command. llvm-bolt -dump-dot-all test.clang.out -o test.clang.bolt

I see too many *.dot files generated, while I was trying to analyze what does each file do, I see that there are many files for the same function(int main in my binary).

 main-00_build-cfg.dot
 main-01_validate-internal-calls.dot
 main-02_strip-rep-ret.dot
'main-12_PLT call optimization.dot'
 main-15_split-functions.dot
 main-16_fix-branches.dot
 main-17_reorder-functions.dot
 main-21_peepholes.dot
 main-22_aligner.dot
 main-23_reorder-data.dot
 main-24_finalize-functions.dot
 main-27_retpoline-insertion.dot
 main-28_assign-sections.dot
 main-29_patch-entries.dot
 main-30_inst-lowering.dot
 main-31_lower-annotations.dot

Does this mean the following optimizations passes have run on main function? What do the numbers prefixing the optimization name signify ? When trying to see what's the different with these files, I see no change in the files(verified using vimdiff command), so why too many files?

Ping! I have signed the CLA.

Could you please add more details, I don't quite understand how the new format will look..

The only extension/fix is the support for escaping characters in the name with backslash. I.e. function\ name, would be properly handled for golang.

we should support names with double quotes as well as space. I agree, although

Escaping space in a symbol name with a backslash might be the most straightforward way to add the extend the fdata format. Could you please add more details, I don't quite understand how the new format will look..

About the slash character - I will double check it soon. However, I don't know limitations that could forbid the usage of slash character in the name :)

Is it possible to include double quotes in the real symbol name as well? I've tried to find if a name with double quotes would constitute a valid name in ELF and couldn't find any rule against it. Plus, we don't want to limit ourselves to ELF. In such case, we should support names with double quotes as well as space. Escaping space in a symbol name with a backslash might be the most straightforward way to add the extend the fdata format. We will also get close to full backwards compatibility automatically.

Is the slash character ("/") in the example you gave ("type..eq.[10]interface {}/") part of the valid golang symbol name? If that's the case, we might need to redesign the way we disambiguate local symbols.

For those like me that had the same issue and have landed here : there is no zero_grads(), you should write zero_grad() instead.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mocha (source)	8.1.0 -> 9.0.0

Release Notes

<details> <summary>mochajs/mocha</summary>

v9.0.0

Compare Source

:boom: Breaking Changes

• #​4633: Drop Node.js v10.x support (@​juergba)

• #​4635: import-first loading of test files (@​giltayar)

Mocha is going ESM-first! This means that it will now use ESM import(test_file) to load the test files, instead of the CommonJS require(test_file). This is not a problem, as import can also load most files that require does. In the rare cases where this fails, it will fallback to require(...). This ESM-first approach is the next step in Mocha's ESM migration, and allows ESM loaders to load and transform the test file.

• #​4636: Remove deprecated utils.lookupFiles() (@​juergba)

• #​4638: Limit the size of actual/expected for diff generation (@​juergba)

• #​4389: Refactoring: Consuming log-symbols alternate to code for win32 in reporters/base (@​MoonSupport)

:tada: Enhancements

• #​4640: Add new option --dry-run (@​juergba)

:bug: Fixes

• #​4128: Fix: control stringification of error message (@​syeutyu)

:nut_and_bolt: Other

• #​4646: Deprecate Runner(suite: Suite, delay: boolean) signature (@​juergba)
• #​4643: Update production dependencies (@​juergba)

v8.4.0

Compare Source

:tada: Enhancements

• #​4502: CLI file parsing errors now have error codes (@​evaline-ju)

:bug: Fixes

• #​4614: Watch: fix crash when reloading files (@​outsideris)

:book: Documentation

• #​4630: Add options.require to Mocha constructor for root hook plugins on parallel runs (@​juergba)
• #​4617: Dynamically generating tests with top-level await and ESM test files (@​juergba)
• #​4608: Update default file extensions (@​outsideris)

Also thanks to @​outsideris for various improvements on our GH actions workflows.

v8.3.2

Compare Source

:bug: Fixes

• #​4599: Fix regression in require interface (@​alexander-fenster)

:book: Documentation

• #​4601: Add build to GH actions run (@​christian-bromann)
• #​4596: Filter active sponsors/backers (@​juergba)
• #​4225: Update config file examples (@​pkuczynski)

v8.3.1

Compare Source

:bug: Fixes

• #​4577: Browser: fix EvalError caused by regenerator-runtime (@​snoack)
• #​4574: ESM: allow import from mocha in parallel mode (@​nicojs)

v8.3.0

Compare Source

:tada: Enhancements

• #​4506: Add error code for test timeout errors (@​boneskull)
• #​4112: Add BigInt support to stringify util function (@​JosejeSinohui)

:bug: Fixes

• #​4557: Add file location when SyntaxError happens in ESM (@​giltayar)
• #​4521: Fix require error when bundling Mocha with Webpack (@​devhazem)

:book: Documentation

• #​4507: Add support for typescript-style docstrings (@​boneskull)
• #​4503: Add GH Actions workflow status badge (@​outsideris)
• #​4494: Add example of generating tests dynamically with a closure (@​maxwellgerber)

:nut_and_bolt: Other

• #​4556: Upgrade all dependencies to latest stable (@​AviVahl)
• #​4543: Update dependencies yargs and yargs-parser (@​juergba)

Also thanks to @​outsideris and @​HyunSangHan for various fixes to our website and documentation.

v8.2.1

Compare Source

Fixed stuff.

:bug: Fixes

• #​4489: Fix problematic handling of otherwise-unhandled Promise rejections and erroneous "done() called twice" errors (@​boneskull)
• #​4496: Avoid MaxListenersExceededWarning in watch mode (@​boneskull)

Also thanks to @​akeating for a documentation fix!

v8.2.0

Compare Source

The major feature added in v8.2.0 is addition of support for global fixtures.

While Mocha has always had the ability to run setup and teardown via a hook (e.g., a before() at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are incompatible with this strategy; e.g., a top-level before() would only run for the file in which it was defined.

With global fixtures, Mocha can now perform user-defined setup and teardown regardless of mode, and these fixtures are guaranteed to run once and only once. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do not share context with your test files (but they do share context with each other).

Here's a short example of usage:

// fixtures.js

// can be async or not
exports.mochaGlobalSetup = async function() {
  this.server = await startSomeServer({port: process.env.TEST_PORT});
  console.log(`server running on port ${this.server.port}`);
};

exports.mochaGlobalTeardown = async function() {
  // the context (`this`) is shared, but not with the test files
  await this.server.stop();
  console.log(`server on port ${this.server.port} stopped`);
};

// this file can contain root hook plugins as well!
// exports.mochaHooks = { ... }

Fixtures are loaded with --require, e.g., mocha --require fixtures.js.

For detailed information, please see the documentation and this handy-dandy flowchart to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).

:tada: Enhancements

• #​4308: Support run-once global setup & teardown fixtures (@​boneskull)
• #​4442: Multi-part extensions (e.g., test.js) now usable with --extension option (@​jordanstephens)
• #​4472: Leading dots (e.g., .js, .test.js) now usable with --extension option (@​boneskull)
• #​4434: Output of json reporter now contains speed ("fast"/"medium"/"slow") property (@​wwhurin)
• #​4464: Errors thrown by serializer in parallel mode now have error codes (@​evaline-ju)

For implementors of custom reporters:

• #​4409: Parallel mode and custom reporter improvements (@​boneskull):
  • Support custom worker-process-only reporters (Runner.prototype.workerReporter()); reporters should subclass ParallelBufferedReporter in mocha/lib/nodejs/reporters/parallel-buffered
  • Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (Runner.prototype.linkPartialObjects()); use if strict object equality is needed when consuming Runner event data
  • Enable detection of parallel mode (Runner.prototype.isParallelMode())

:bug: Fixes

• #​4476: Workaround for profoundly bizarre issue affecting npm v6.x causing some of Mocha's deps to be installed when mocha is present in a package's devDependencies and npm install --production is run the package's working copy (@​boneskull)
• #​4465: Worker processes guaranteed (as opposed to "very likely") to exit before Mocha does; fixes a problem when using nyc with Mocha in parallel mode (@​boneskull)
• #​4419: Restore lookupFiles() in mocha/lib/utils, which was broken/missing in Mocha v8.1.0; it now prints a deprecation warning (use const {lookupFiles} = require('mocha/lib/cli') instead) (@​boneskull)

Thanks to @​AviVahl, @​donghoon-song, @​ValeriaVG, @​znarf, @​sujin-park, and @​majecty for other helpful contributions!

v8.1.3

Compare Source

:bug: Fixes

• #​4425: Restore Mocha.utils.lookupFiles() and Webpack compatibility (both broken since v8.1.0); Mocha.utils.lookupFiles() is now deprecated and will be removed in the next major revision of Mocha; use require('mocha/lib/cli').lookupFiles instead (@​boneskull)

v8.1.2

Compare Source

:bug: Fixes

• #​4418: Fix command-line flag incompatibility in forthcoming Node.js v14.9.0 (@​boneskull)
• #​4401: Fix missing global variable in browser (@​irrationnelle)

:lock: Security Fixes

• #​4396: Update many dependencies (@​GChuf)

:book: Documentation

• Various fixes by @​sujin-park, @​wwhurin & @​Donghoon759

v8.1.1

Compare Source

:bug: Fixes

• #​4394: Fix regression wherein certain reporters did not correctly detect terminal width (@​boneskull)

</details>

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

一言でいうと

1サンプルをどこまでデータ拡張で増やしてよいか検証した研究。データ拡張を行うほど精度が高く、学習時間が短くなることを確認。16倍の拡張でImageNetのSOTAを記録(モデルはNFNet-F5、最適化手法はSAM)。データ全体の分散は下がるが、個々サンプルの分散は上がることに拠る

論文リンク

https://arxiv.org/abs/2105.13343

著者/所属機関

Stanislav Fort, Andrew Brock, Razvan Pascanu, Soham De, Samuel L. Smith

• Stanford University
• DeepMind

投稿日付(yyyy/MM/dd)

2021/5/27

概要

新規性・差分

手法

結果

コメント

一言でいうと

テーブルデータの予測にTransformer x 事前学習を活用した研究。通常のSelf-Attentionに加えサンプル表現間のSelf-Attention(Intersample Attention)を使用。入力にCutMix/潜在表現にMixupを適用し、対照とノイズ復元、2種の損失で学習を行う。Boosting既存手法より高い精度

論文リンク

https://arxiv.org/abs/2106.01342

著者/所属機関

Gowthami Somepalli, Micah Goldblum, Avi Schwarzschild, C. Bayan Bruss, Tom Goldstein

投稿日付(yyyy/MM/dd)

2021/6/2

概要

新規性・差分

手法

結果

コメント

一言でいうと

1モデルで画像/言語双方のタスクを解く手法の提案。画像と画像に関する質問を入力とし、質問に関連する物体領域と回答を出力とする。マルチタスクで学習することで、各タスク専門のモデルより良好な精度を達成。また、破壊的忘却も起こりにくくなる。

論文リンク

https://arxiv.org/abs/2104.00743

著者/所属機関

Tanmay Gupta, Amita Kamath, Aniruddha Kembhavi, Derek Hoiem

• PRIOR @ Allen Institute for AI
• University of Illinois at Urbana-Champaign

投稿日付(yyyy/MM/dd)

2021/4/1

概要

新規性・差分

手法

結果

コメント

The old fdata files might be fixed using simple awk script: awk '{$2 = "\""$2"\""; $5 = "\""$5"\"";print}' prof.fdata

If it is necessary we can remove this error and use parseString(NameSeparator) if NameSeparator was found and FieldSeparator if it was not. But if it possible for for you @rafaelauler to replace old fdata you use without quotes with new one - I suggest just to use new variant.

This patch is part of preparation for golang support. The golang symbols might have spaces in the name (for example "type..eq.[10]interface {}/"). Since fdata uses spaces as field separator such names brakes fdata format, so I suggest to use quotes for symbol names to avoid such errors.

Vladislav Khmelevsky, Advanced Software Technology Lab, Huawei

Add forgotten cflags Vladislav Khmelevsky, Advanced Software Technology Lab, Huawei