User Details
- User Since
- Mar 28 2016, 3:30 AM (251 w, 3 d)
Wed, Jan 20
@awarzynski, @sscalpone added the rule in C++Style.md in fdb58597e859. Perhaps Steve could explain the motivation for deviating from Clang's style guide (https://llvm.org/docs/CodingStandards.html#error-and-warning-messages)? IMO Flang should behave more consistently with Clang, especially if we start sharing more code between the two frontends going forward.
Dec 10 2020
@erikjv Are you still working on this? Or is a better alternative being pursued? IIUC, this functionality is still missing in trunk.
Oct 29 2020
Sep 14 2020
Apologies for the bug and thanks @hliao for the quick fix.
Sep 10 2020
Thanks Sanjay.
Sep 6 2020
Sep 4 2020
Pinging reviewers.
Sep 3 2020
Removed the change to the default value of EarlyCSEDebugHash as per @lebedev.ri's suggestion.
Aug 31 2020
Aug 30 2020
Fixed linter warning.
Added a regression test using the -earlycse-debug-hash option.
Aug 29 2020
Cleaned up unused code.
Moved the fix into matchSelectWithOptionalNotCond instead of duplicating code.
Jun 18 2020
Sorry for the late question, but I don't understand why this kind of folding is not considered reassociation. I thought reassociation was not allowed even when -ffp-contract=fast.
Apr 14 2020
Apr 13 2020
Pair the memory barriers correctly at the same nesting level within the loop.
Add a paired memory barrier to the child thread's path after it finishes writing to its own data and before releasing the parent thread.
Apr 6 2020
Mar 27 2020
Mar 26 2020
@Hahnfeld Thanks for the explanation!
Mar 25 2020
Dec 30 2019
Dec 8 2019
Dec 6 2019
Removed unrelated changes from this patch.
Dec 5 2019
Pinging reviewers.
Nov 29 2019
Add tests for -fopenmp-targets=.
Nov 28 2019
Oct 28 2019
Oct 26 2019
Avoid reading CTR_EL0 on every call to __clear_cache.
I actually read that LKML post before submitting the patch, and I had the same understanding as @ktkachov. I will change the code to cache the result of the MRS instruction as suggested.
Oct 23 2019
Pinging reviewers.
Oct 21 2019
Oct 7 2019
Feb 15 2019
Feb 13 2019
Feb 5 2019
Is there any plan to fix this patch and land it? We use --max-time in our tests and intermittently run into the Python assertion. We can work around the problem by killing lit.py with another timer, but then we lose the report that lit.py produces at the end of the run.
Jan 10 2019
Rebased on trunk.
Removed trailing spaces. NFC.
Jan 8 2019
Pinging reviewers.
Jan 3 2019
Nov 26 2018
Nov 22 2018
Nov 9 2018
Thanks Kristof!
Nov 6 2018
Pinging reviewers....
Nov 1 2018
Added a unit test for lib/Support/Host.cpp and removed some redundant tests.
Oct 30 2018
Oct 29 2018
Oct 25 2018
Oct 24 2018
Oct 23 2018
Updated the patch to avoid using monorepo path names.
Sep 3 2018
Aug 25 2018
Pinging reviewers...
Aug 15 2018
Aug 13 2018
Aug 6 2018
Aug 3 2018
Removed impossible code path from NormalizeBuildVector.