Author: David Blaikie
Date: 2021-03-11T17:51:31-08:00
New Revision: bd2bdad19e5a3bf910da7c2d1936a7e18b47c084
URL:
https://github.com/llvm/llvm-project/commit/bd2bdad19e5a3bf910da7c2d1936a7e18b47c084
DIFF:
https://github.com/llvm/llvm-project/commit/bd2bdad19e5a3bf910da7c2d1936a7e18b47c084.diff
Author: David Blaikie
Date: 2021-11-14T13:35:22-08:00
New Revision: 5de369056dee2c4de81625cb05a5c212a0bdc053
URL:
https://github.com/llvm/llvm-project/commit/5de369056dee2c4de81625cb05a5c212a0bdc053
DIFF:
https://github.com/llvm/llvm-project/commit/5de369056dee2c4de81625cb05a5c212a0bdc053.diff
Author: David Blaikie
Date: 2021-11-14T20:45:16-08:00
New Revision: 400eb59adf43b29af3117c163cf770e6d6e514f7
URL:
https://github.com/llvm/llvm-project/commit/400eb59adf43b29af3117c163cf770e6d6e514f7
DIFF:
https://github.com/llvm/llvm-project/commit/400eb59adf43b29af3117c163cf770e6d6e514f7.diff
Author: David Blaikie
Date: 2021-11-14T20:45:16-08:00
New Revision: 604446aa6b41461e2691c9f4253e9ef70a5d68e4
URL:
https://github.com/llvm/llvm-project/commit/604446aa6b41461e2691c9f4253e9ef70a5d68e4
DIFF:
https://github.com/llvm/llvm-project/commit/604446aa6b41461e2691c9f4253e9ef70a5d68e4.diff
Author: David Blaikie
Date: 2021-11-14T20:45:16-08:00
New Revision: b2589e326ba4407d8314938a4f7498086e2203ea
URL:
https://github.com/llvm/llvm-project/commit/b2589e326ba4407d8314938a4f7498086e2203ea
DIFF:
https://github.com/llvm/llvm-project/commit/b2589e326ba4407d8314938a4f7498086e2203ea.diff
Author: David Blaikie
Date: 2021-11-14T21:09:11-08:00
New Revision: 50fdd7df827137c8465abafa82a6bae7c87096c5
URL:
https://github.com/llvm/llvm-project/commit/50fdd7df827137c8465abafa82a6bae7c87096c5
DIFF:
https://github.com/llvm/llvm-project/commit/50fdd7df827137c8465abafa82a6bae7c87096c5.diff
Author: Paul Pluzhnikov
Date: 2022-10-18T20:48:00Z
New Revision: 5b773dcd2de0c4844814266a90dac14c349b8f18
URL:
https://github.com/llvm/llvm-project/commit/5b773dcd2de0c4844814266a90dac14c349b8f18
DIFF:
https://github.com/llvm/llvm-project/commit/5b773dcd2de0c4844814266a90dac14c349b8f18.diff
LO
Author: David Blaikie
Date: 2022-10-26T22:00:49Z
New Revision: 7846d590033e8d661198f4c00f56f46a4993c526
URL:
https://github.com/llvm/llvm-project/commit/7846d590033e8d661198f4c00f56f46a4993c526
DIFF:
https://github.com/llvm/llvm-project/commit/7846d590033e8d661198f4c00f56f46a4993c526.diff
LOG:
Author: David Blaikie
Date: 2022-10-26T22:18:51Z
New Revision: ec273d3e3a8c3bcb2cf98f893f28bee5bf9b30af
URL:
https://github.com/llvm/llvm-project/commit/ec273d3e3a8c3bcb2cf98f893f28bee5bf9b30af
DIFF:
https://github.com/llvm/llvm-project/commit/ec273d3e3a8c3bcb2cf98f893f28bee5bf9b30af.diff
LOG:
Author: David Blaikie
Date: 2022-10-27T20:41:22Z
New Revision: e4ec6ce8a75c208b49b163c81cda90dc7373c791
URL:
https://github.com/llvm/llvm-project/commit/e4ec6ce8a75c208b49b163c81cda90dc7373c791
DIFF:
https://github.com/llvm/llvm-project/commit/e4ec6ce8a75c208b49b163c81cda90dc7373c791.diff
LOG:
Posted, awaiting approval.
On Fri, Oct 28, 2022 at 5:23 AM Aaron Ballman wrote:
>
> Also, please be sure to post something to
> https://discourse.llvm.org/c/announce/46 with the potentially-breaking
> tag applied to it.
>
> ~Aaron
>
> On Thu, Oct 27, 2022 at 8:19 PM Hubert Tong via Phabricator vi
Author: David Blaikie
Date: 2022-10-28T22:29:50Z
New Revision: 97c1b0094ad6f628927223b53300c9296ae72f44
URL:
https://github.com/llvm/llvm-project/commit/97c1b0094ad6f628927223b53300c9296ae72f44
DIFF:
https://github.com/llvm/llvm-project/commit/97c1b0094ad6f628927223b53300c9296ae72f44.diff
LOG:
Please include some details about the reason for a revert in the
revert commit message in addition to the precanned revision/subject
quoting
On Wed, Oct 26, 2022 at 1:16 AM Matheus Izvekov via cfe-commits
wrote:
>
>
> Author: Matheus Izvekov
> Date: 2022-10-26T10:14:27+02:00
> New Revision: a88eb
Author: David Blaikie
Date: 2022-08-17T00:35:05Z
New Revision: 06c70e9b998ca289630ee1629ec09b6dd51b29b9
URL:
https://github.com/llvm/llvm-project/commit/06c70e9b998ca289630ee1629ec09b6dd51b29b9
DIFF:
https://github.com/llvm/llvm-project/commit/06c70e9b998ca289630ee1629ec09b6dd51b29b9.diff
LOG:
Author: David Blaikie
Date: 2022-08-19T04:00:21Z
New Revision: d4e0fe62b1aa090527c0cc289cdf3eef0370f064
URL:
https://github.com/llvm/llvm-project/commit/d4e0fe62b1aa090527c0cc289cdf3eef0370f064
DIFF:
https://github.com/llvm/llvm-project/commit/d4e0fe62b1aa090527c0cc289cdf3eef0370f064.diff
LOG:
Seems like a bug in the GCC9 warning - any chance we can disable it?
(is it fixed in later versions of GCC?)
I can't seem to reproduce this with godbolt at least with basic
examples - it'd be good to know how bad the thing is we're working
around so we know if we want to keep working around it, or
Thanks for the link - fair enough. We'll see how ubiquitous the
constexpr-creating-sort-of-unused-variables situation is. If it comes
up a lot we might want to disable the warning for GCC 9.
On Mon, Aug 22, 2022 at 7:58 PM chuanqi.xcq wrote:
>
> Hi David,
>
> This is the reproduce link from god
Author: Jonathan Camilleri
Date: 2022-09-22T17:08:41Z
New Revision: 4cd7529e4caa00fa7ba27d9de18adea3c702ad8f
URL:
https://github.com/llvm/llvm-project/commit/4cd7529e4caa00fa7ba27d9de18adea3c702ad8f
DIFF:
https://github.com/llvm/llvm-project/commit/4cd7529e4caa00fa7ba27d9de18adea3c702ad8f.diff
Author: Azat Khuzhin
Date: 2022-10-04T20:03:36Z
New Revision: 16512898956857b13e566165ba9a195be81d325f
URL:
https://github.com/llvm/llvm-project/commit/16512898956857b13e566165ba9a195be81d325f
DIFF:
https://github.com/llvm/llvm-project/commit/16512898956857b13e566165ba9a195be81d325f.diff
LOG:
Author: David Blaikie
Date: 2022-10-04T20:17:29Z
New Revision: 2e1c1d6d72879cafc339ad035b1b5a6d1c8cc130
URL:
https://github.com/llvm/llvm-project/commit/2e1c1d6d72879cafc339ad035b1b5a6d1c8cc130
DIFF:
https://github.com/llvm/llvm-project/commit/2e1c1d6d72879cafc339ad035b1b5a6d1c8cc130.diff
LOG:
Author: David Blaikie
Date: 2022-10-04T20:19:17Z
New Revision: 4769976c49be468d7629d513080e6959a25adcfe
URL:
https://github.com/llvm/llvm-project/commit/4769976c49be468d7629d513080e6959a25adcfe
DIFF:
https://github.com/llvm/llvm-project/commit/4769976c49be468d7629d513080e6959a25adcfe.diff
LOG:
Author: David Blaikie
Date: 2022-10-05T20:22:19Z
New Revision: b61860e63e34d955a9841389583978af93c2b97a
URL:
https://github.com/llvm/llvm-project/commit/b61860e63e34d955a9841389583978af93c2b97a
DIFF:
https://github.com/llvm/llvm-project/commit/b61860e63e34d955a9841389583978af93c2b97a.diff
LOG:
Could the underlying API be made more robust to handle StringRefs
rather than null terminated char* in the first place? (like
SourceManager::getCharacterData could return StringRef? Presumably at
some layer it already knows how long the file is - the underlying
MemoryBuffer, in this case)
On Thu,
On Mon, Oct 10, 2022 at 11:13 AM Sam McCall wrote:
>
> On Mon, 10 Oct 2022, 19:57 David Blaikie, wrote:
>>
>> Could the underlying API be made more robust to handle StringRefs
>> rather than null terminated char* in the first place? (like
>> SourceManager::getCharacterData could return StringRef?
Author: David Blaikie
Date: 2022-10-13T21:13:19Z
New Revision: 9363071303ec59bc9e0d9b989f08390b37e3f5e4
URL:
https://github.com/llvm/llvm-project/commit/9363071303ec59bc9e0d9b989f08390b37e3f5e4
DIFF:
https://github.com/llvm/llvm-project/commit/9363071303ec59bc9e0d9b989f08390b37e3f5e4.diff
LOG:
Author: David Blaikie
Date: 2022-10-14T19:32:57Z
New Revision: 037f856681268c793c660389b4d6407367e68190
URL:
https://github.com/llvm/llvm-project/commit/037f856681268c793c660389b4d6407367e68190
DIFF:
https://github.com/llvm/llvm-project/commit/037f856681268c793c660389b4d6407367e68190.diff
LOG:
If the switch is exhaustive (covers all the enumerators in an
enumeration), we usually use an llvm_unreachable at the end, rather
than a return. Could you change this to an llvm_unreachable?
On Mon, Oct 17, 2022 at 3:52 PM Xiang Li via cfe-commits
wrote:
>
>
> Author: Xiang Li
> Date: 2022-10-17T
Also the static_assert is probably not needed - Clang builds with
-Wswitch-enum, which will warn if a switch over an enum doesn't cover
all the enumerators. We have lots of other switches over enums that
depend on this warning to detect code that needs to be updated when an
enum is modified.
On Mo
On Mon, Oct 17, 2022 at 5:52 PM stan li wrote:
>
> Thanks for the suggestion.
>
>
>
> Updated llvm_unreachable.
>
>
>
> The static_cast not only check the switch cases all covered, also make sure 2
> enums not out of sync.
Ah, OK - thanks for explaining!
>
>
>
>
>
>
>
> Sent from Mail for Win
Author: David Blaikie
Date: 2022-11-18T00:24:40Z
New Revision: a72d8d704178118b254d9ff84a78afb18813b888
URL:
https://github.com/llvm/llvm-project/commit/a72d8d704178118b254d9ff84a78afb18813b888
DIFF:
https://github.com/llvm/llvm-project/commit/a72d8d704178118b254d9ff84a78afb18813b888.diff
LOG:
Nice!
On Sun, Jan 15, 2023 at 12:10 PM Benjamin Kramer via cfe-commits
wrote:
>
>
> Author: Benjamin Kramer
> Date: 2023-01-15T20:59:21+01:00
> New Revision: 931d04be2fc8f3f0505b43e64297f75d526cb42a
>
> URL:
> https://github.com/llvm/llvm-project/commit/931d04be2fc8f3f0505b43e64297f75d526cb42a
>
On Sun, Jun 12, 2022 at 10:17 AM Kazu Hirata via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
>
> Author: Kazu Hirata
> Date: 2022-06-12T10:17:12-07:00
> New Revision: f13019f8367a417075e70effb13dcf58024090b2
>
> URL:
> https://github.com/llvm/llvm-project/commit/f13019f8367a417075e70effb13dcf
Please include details about the reason for a revert in the revert commit
message - helpful for folks following along/looking to see if a given
revert addresses an issue they're seeing, etc.
On Sun, Jun 12, 2022 at 7:47 AM Jez Ng via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
>
> Author: Je
Please include details of what changed between one commit and a recommit of
a patch - helpful for reviewers checking what's changed since the last
commit, double-checking that the patch fully addresses the issues, etc.
On Sun, Jun 12, 2022 at 2:24 PM Jez Ng via cfe-commits <
cfe-commits@lists.llvm
Author: David Blaikie
Date: 2022-06-23T20:15:00Z
New Revision: 517bbc64dbe493644eff8d55fd9566435e930520
URL:
https://github.com/llvm/llvm-project/commit/517bbc64dbe493644eff8d55fd9566435e930520
DIFF:
https://github.com/llvm/llvm-project/commit/517bbc64dbe493644eff8d55fd9566435e930520.diff
LOG:
Author: David Blaikie
Date: 2022-06-24T17:07:47Z
New Revision: 4821508d4db75a535d02b8938f81fac6de66cc26
URL:
https://github.com/llvm/llvm-project/commit/4821508d4db75a535d02b8938f81fac6de66cc26
DIFF:
https://github.com/llvm/llvm-project/commit/4821508d4db75a535d02b8938f81fac6de66cc26.diff
LOG:
Author: David Blaikie
Date: 2022-05-25T03:03:27Z
New Revision: e59f648d698efe58b96e9b6224449b2b8cfa872a
URL:
https://github.com/llvm/llvm-project/commit/e59f648d698efe58b96e9b6224449b2b8cfa872a
DIFF:
https://github.com/llvm/llvm-project/commit/e59f648d698efe58b96e9b6224449b2b8cfa872a.diff
LOG:
Beyond that it may be useful to look at who's been contributing to the
code you're trying to change and consider cc'ing them on the review.
(if they can't help, maybe they can point you to someone who can)
On Fri, May 27, 2022 at 2:23 PM stryku_t via cfe-commits
wrote:
>
> Hi Paul,
>
> Thank you
Author: David Blaikie
Date: 2022-06-02T20:57:31Z
New Revision: cb08f4aa4467cf562b62e542725f5351c5482495
URL:
https://github.com/llvm/llvm-project/commit/cb08f4aa4467cf562b62e542725f5351c5482495
DIFF:
https://github.com/llvm/llvm-project/commit/cb08f4aa4467cf562b62e542725f5351c5482495.diff
LOG:
@@ -0,0 +1,301 @@
+//===- llvm/ADT/PagedVector.h - 'Lazyly allocated' vectors *- C++
+//-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier
@@ -0,0 +1,301 @@
+//===- llvm/ADT/PagedVector.h - 'Lazyly allocated' vectors *- C++
+//-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier
@@ -0,0 +1,301 @@
+//===- llvm/ADT/PagedVector.h - 'Lazyly allocated' vectors *- C++
+//-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier
@@ -7944,9 +7944,13 @@ void ASTReader::PrintStats() {
std::fprintf(stderr, "*** AST File Statistics:\n");
unsigned NumTypesLoaded =
- TypesLoaded.size() - llvm::count(TypesLoaded, QualType());
+ TypesLoaded.size() - std::count(TypesLoaded.materialisedBegin(),
---
@@ -0,0 +1,301 @@
+//===- llvm/ADT/PagedVector.h - 'Lazyly allocated' vectors *- C++
+//-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier
@@ -0,0 +1,301 @@
+//===- llvm/ADT/PagedVector.h - 'Lazyly allocated' vectors *- C++
+//-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier
@@ -2325,6 +2325,7 @@ void
CodeGenModule::SetLLVMFunctionAttributesForDefinition(const Decl *D,
B.addAttribute(llvm::Attribute::Naked);
// OptimizeNone wins over OptimizeForSize and MinSize.
+F->removeFnAttr(llvm::Attribute::OptimizeForDebugging);
--
@@ -1245,6 +1245,27 @@ void Sema::ActOnEndOfTranslationUnit() {
}
}
+// Now we can decide whether the modules we're building need an
initializer.
+if (Module *CurrentModule = getCurrentModule();
+CurrentModule && CurrentModule->isInterfaceOrPartition
dwblaikie wrote:
(aside: I was confused why there was only one commit in this PR, since there'd
been so many updates to it - but I see they've been force pushed, which my
vague understanding is that force pushing can complicate tracking previous
comments and the LLVM convention is not to do so
dwblaikie wrote:
Oh, no worries at all. LLVM 's still figuring out this whole GitHub transition
anyway. I mention it only for future reference and because it might help
reviewers/you if comments are getting missplaced/there's trouble tracking
unaddressed feedback, etc.
Thanks for sticking wit
https://github.com/dwblaikie approved this pull request.
Awesome - love a good readability improvement. Thanks!
https://github.com/llvm/llvm-project/pull/67900
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailm
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
dwblaikie wrote:
> It seems checks are broken on trunk, I see commits merged with failing
> pre-merge tests. They seem to be unrelated to this patch though.
>
> Is there anything else you'd like fixed before mergi
dwblaikie wrote:
> This only affects builds with GCC.
My understanding was that we basically only cared about performance of clang on
clang - that we expect people who want an efficient clang to bootstrap?
Could `always_inline` the function, but those sort of annotations would get out
of date
@@ -106,14 +107,71 @@ static void findReturnsToZap(Function &F,
}
}
-static bool runIPSCCP(
-Module &M, const DataLayout &DL, FunctionAnalysisManager *FAM,
-std::function GetTLI,
-std::function GetTTI,
-std::function GetAC,
-std::function GetDT,
-std:
@@ -106,14 +107,71 @@ static void findReturnsToZap(Function &F,
}
}
-static bool runIPSCCP(
-Module &M, const DataLayout &DL, FunctionAnalysisManager *FAM,
-std::function GetTLI,
-std::function GetTTI,
-std::function GetAC,
-std::function GetDT,
-std:
@@ -106,14 +107,71 @@ static void findReturnsToZap(Function &F,
}
}
-static bool runIPSCCP(
-Module &M, const DataLayout &DL, FunctionAnalysisManager *FAM,
-std::function GetTLI,
-std::function GetTTI,
-std::function GetAC,
-std::function GetDT,
-std:
@@ -106,14 +107,71 @@ static void findReturnsToZap(Function &F,
}
}
-static bool runIPSCCP(
-Module &M, const DataLayout &DL, FunctionAnalysisManager *FAM,
-std::function GetTLI,
-std::function GetTTI,
-std::function GetAC,
-std::function GetDT,
-std:
Author: David Blaikie
Date: 2023-07-18T23:43:41Z
New Revision: b43df5bfe7e7ef358e135b515b0651ec51f635d8
URL:
https://github.com/llvm/llvm-project/commit/b43df5bfe7e7ef358e135b515b0651ec51f635d8
DIFF:
https://github.com/llvm/llvm-project/commit/b43df5bfe7e7ef358e135b515b0651ec51f635d8.diff
LOG:
Author: David Blaikie
Date: 2023-08-14T22:25:42Z
New Revision: 19f2b68095fe727e40079b7c6380b36b6462e691
URL:
https://github.com/llvm/llvm-project/commit/19f2b68095fe727e40079b7c6380b36b6462e691
DIFF:
https://github.com/llvm/llvm-project/commit/19f2b68095fe727e40079b7c6380b36b6462e691.diff
LOG:
Author: David Blaikie
Date: 2023-08-17T05:35:40Z
New Revision: 2993243c45abdb4f2bc3979336d054be165b1134
URL:
https://github.com/llvm/llvm-project/commit/2993243c45abdb4f2bc3979336d054be165b1134
DIFF:
https://github.com/llvm/llvm-project/commit/2993243c45abdb4f2bc3979336d054be165b1134.diff
LOG:
dwblaikie wrote:
This doesn't seem all that useful/important to me - a user can move the body of
the function into an implementation unit rather than putting it in the
interface unit and marking it noinline, right? This is the same recommendation
we'd make if someone wrote a complex function d
dwblaikie wrote:
*shrug* I guess it's OK.
https://github.com/llvm/llvm-project/pull/68501
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/dwblaikie approved this pull request.
https://github.com/llvm/llvm-project/pull/68501
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -0,0 +1,158 @@
+//===- raw_ostream_proxy.h - Proxies for raw output streams -*- C++
-*-===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
https://github.com/dwblaikie edited
https://github.com/llvm/llvm-project/pull/66632
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/dwblaikie approved this pull request.
looks good - a few bits should be committed separately from this change, so
please do those first and then commit this change
https://github.com/llvm/llvm-project/pull/66632
___
cfe-commits mail
@@ -1085,6 +1085,7 @@ The integer codes are mapped to well-known attributes as
follows.
* code 77: ``elementtype``
* code 78: ``disable_sanitizer_instrumentation``
* code 79: ``nosanitize_bounds``
+* code 88: ``optdebug``
dwblaikie wrote:
This could/should be
@@ -2028,6 +2030,8 @@ example:
This attribute suggests that optimization passes and code generator passes
should make choices that try to preserve debug info without significantly
degrading runtime performance.
+This attribute is incompatible with the ``minsize`
dwblaikie wrote:
FWIW, I think we also saw, internally at Google, some significant and
surprising (growth in sections, like .debug_loclists and
.debug_gnu_pubnames/types) that were a bit surprising/not what I'd have
expected of the original committed/reverted patch.
Could you run a clang buil
dwblaikie wrote:
> This is useful when user is forced to use the same type for all bitfields in
> a class to get better [layout](https://godbolt.org/z/ovWqzqv9x) and
> [codegen](https://godbolt.org/z/bdoqvz9e6) from MSVC
Does this issue not apply to other platforms? (I didn't think you could
dwblaikie wrote:
Seems a bit unfortunate/bit of a heavyweight workaround - but I don't
fundamentally object if @AaronBallman or co are OK with the new attribute for
this.
https://github.com/llvm/llvm-project/pull/69104
___
cfe-commits mailing list
cf
dwblaikie wrote:
> Wouldn't it be better to go the other way around? i.e. have a
> `[[clang::compressed_bitfield]]` (or whatever) which influences the ABI, so
> it's possible to do stuff like
>
> ```c++
> [[clang::compressed_bitfield]] bool IsSomething : 1;
> [[clang::compressed_bitfield]] MyE
Author: David Blaikie
Date: 2023-07-31T19:01:44Z
New Revision: 3a100ea901ed79d6a06a5f018be2b4d3bbca51e8
URL:
https://github.com/llvm/llvm-project/commit/3a100ea901ed79d6a06a5f018be2b4d3bbca51e8
DIFF:
https://github.com/llvm/llvm-project/commit/3a100ea901ed79d6a06a5f018be2b4d3bbca51e8.diff
LOG:
Ping on this - please always include details on the reason for a revert.
On Tue, Aug 1, 2023 at 10:09 AM Richard Smith via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> This revert reintroduces a wrong-code bug, can you explain what the
> purpose of the revert is?
>
> On Fri, 28 Jul 2023 at
Author: David Blaikie
Date: 2022-11-22T00:02:09Z
New Revision: 9df8ba631d4612eb8f930c9fe7c6cf39e5deb3af
URL:
https://github.com/llvm/llvm-project/commit/9df8ba631d4612eb8f930c9fe7c6cf39e5deb3af
DIFF:
https://github.com/llvm/llvm-project/commit/9df8ba631d4612eb8f930c9fe7c6cf39e5deb3af.diff
LOG:
Author: Alexey Kreshchuk
Date: 2022-11-23T18:43:06Z
New Revision: 2cea4c239570c37f46ad0003b3d41d9473aca60f
URL:
https://github.com/llvm/llvm-project/commit/2cea4c239570c37f46ad0003b3d41d9473aca60f
DIFF:
https://github.com/llvm/llvm-project/commit/2cea4c239570c37f46ad0003b3d41d9473aca60f.diff
L
Please include the reason for the revert in the revert message (including
links/quotes from buildbots, etc)
On Fri, Mar 20, 2020 at 4:28 PM Adrian Prantl via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
>
> Author: Adrian Prantl
> Date: 2020-03-20T16:27:23-07:00
> New Revision: bde15de3cabff6
Please include the "Differential Revision" line so that Phab picks up
commits like this and ties them into the review (& also makes it
conveniently clickable to jump from the commit mail to the review)
On Thu, Mar 19, 2020 at 5:58 AM Djordje Todorovic via cfe-commits <
cfe-commits@lists.llvm.org>
Why the change? this seems counter to LLVM's style which pretty
consistently uses unreachable rather than assert(false), so far as I know?
On Tue, Mar 10, 2020 at 11:22 AM Aaron Ballman via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
>
> Author: Aaron Ballman
> Date: 2020-03-10T14:22:21-04:0
Does "isIntegerConstantExpr" have side effects that are desired/necessary?
Otherwise please change this to roll the isIntegerConstantExpr into the
assert (so that it is only executed when asserts are enabled)
On Tue, Mar 10, 2020 at 10:11 AM Mikhail Maltsev via cfe-commits <
cfe-commits@lists.llvm
Author: David Blaikie
Date: 2020-03-21T21:17:33-07:00
New Revision: b5eafda8d3ef02f9f78e090725564dd28e573322
URL:
https://github.com/llvm/llvm-project/commit/b5eafda8d3ef02f9f78e090725564dd28e573322
DIFF:
https://github.com/llvm/llvm-project/commit/b5eafda8d3ef02f9f78e090725564dd28e573322.diff
I've reverted this in b5eafda8d3ef02f9f78e090725564dd28e573322 - the
warning isn't accurate/appropriate - this type is safe as it was previously
written (having a protected non-virtual dtor and derived classes being
final with a non-virtual dtor - so there's no way (well, inside the base
class you
Probably worth a bit more detail when recommitting a patch that was
reverted - in the future please include more detail about the reason for
the original revert and the specific changes to the previous version that
address that (so someone who might've reviewed the previous patch can more
quickly e
"a problem" seems a smidge vague - was there a specific explanation for the
kind of problem that was signalled? Or was this fix a bit of a shot in the
dark?
On Sat, Feb 15, 2020 at 10:55 PM Johannes Doerfert via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
>
> Author: Johannes Doerfert
> Date
Also, this patch was reverted and recommitted several times (more than I
think would be ideal) - please include more details in the commit message
about what went wrong, what was fixed, what testing was missed in the first
place and done in subsequent precommit validation (& is there anything more
In the future, please include more detail in the commit message of a
recommit about how the patch addresses the problems that lead to the
previous revert. This makes it easier for someone reviewing the code to
examine the new changes & ensure they're correct/appropriate.
On Mon, Mar 2, 2020 at 3:1
On Sun, Mar 22, 2020 at 6:34 AM Aaron Ballman
wrote:
> On Sat, Mar 21, 2020 at 11:31 PM David Blaikie wrote:
> >
> > Why the change? this seems counter to LLVM's style which pretty
> consistently uses unreachable rather than assert(false), so far as I know?
>
> We're not super consistent (at lea
On Sun, Mar 22, 2020 at 10:40 AM Johannes Doerfert
wrote:
> Some buildbots, I think only Windows buildbots for some reason, crashed
> in this function.
>
> The reason, as described, is that an `llvm::function_ref` cannot be
> copied and then reused. It just happened to work on almost all
> config
On Sun, Mar 22, 2020 at 9:34 AM Aaron Ballman
wrote:
> On Sun, Mar 22, 2020 at 12:19 PM David Blaikie wrote:
> >
> > On Sun, Mar 22, 2020 at 6:34 AM Aaron Ballman
> wrote:
> >>
> >> On Sat, Mar 21, 2020 at 11:31 PM David Blaikie
> wrote:
> >> >
> >> > Why the change? this seems counter to LLVM
Author: David Blaikie
Date: 2020-03-22T18:43:39-07:00
New Revision: 0d0b90105f92f6cd9cc7004d565834f4429183fb
URL:
https://github.com/llvm/llvm-project/commit/0d0b90105f92f6cd9cc7004d565834f4429183fb
DIFF:
https://github.com/llvm/llvm-project/commit/0d0b90105f92f6cd9cc7004d565834f4429183fb.diff
ones) don't like it we need to
> investigate why. As mentioned, I had a problem recreating the problem
> locally before.
>
> Cheers,
>Johannes
>
>
> On 3/22/20 1:37 PM, Arthur O'Dwyer wrote:
> > On Sun, Mar 22, 2020 at 1:48 PM David Blaikie via cfe-commits &
Author: David Blaikie
Date: 2020-03-22T22:43:44-07:00
New Revision: 2ec59a0a40f4ec02e6b2dbe5f12261959c191aa9
URL:
https://github.com/llvm/llvm-project/commit/2ec59a0a40f4ec02e6b2dbe5f12261959c191aa9
DIFF:
https://github.com/llvm/llvm-project/commit/2ec59a0a40f4ec02e6b2dbe5f12261959c191aa9.diff
Ah, thanks. (I'm going to see about renaming/restructuring that API - to
return Optional and be called 'get' rather than 'is' to make this
more clear)
On Mon, Mar 23, 2020 at 5:04 AM Mikhail Maltsev
wrote:
> Yes, it does. isIntegerConstantExpr assigns a value to CoprocNoAP.
>
> --
> Regards,
>
On Mon, Mar 23, 2020 at 5:24 AM Aaron Ballman
wrote:
> On Sun, Mar 22, 2020 at 3:31 PM David Blaikie wrote:
> >
> > On Sun, Mar 22, 2020 at 9:34 AM Aaron Ballman
> wrote:
> >>
> >> On Sun, Mar 22, 2020 at 12:19 PM David Blaikie
> wrote:
> >> >
> >> > On Sun, Mar 22, 2020 at 6:34 AM Aaron Ballm
Sent https://reviews.llvm.org/D76646 to hopefully make this a bit more
legible
On Mon, Mar 23, 2020 at 2:38 PM David Blaikie wrote:
> Ah, thanks. (I'm going to see about renaming/restructuring that API - to
> return Optional and be called 'get' rather than 'is' to make this
> more clear)
>
> On
Thanks again for talking it through & the documentation update - it's a
great reference point to keep in mind for future reviews, etc.
On Tue, Mar 24, 2020 at 1:08 PM Aaron Ballman
wrote:
> Thank you for the discussion on IRC about this topic. For reference,
> this generated https://reviews.llvm
logies for the confusion.
>>
>> I wrote the commit message after looking into this and I though the
>> issue was related to the capture by copy in the inner llvm::any_of and
>> the reuse in the outer. Looking back at the code I cannot say anymore
>> how I
>> (/home/buildbots/ppc64be-clang-multistage-test/clang-ppc64be-multistage/stage1/bin/clang+0x109674cc)
>> #23 0x109635b8 ExecuteCC1Tool(llvm::SmallVectorImpl> const*>&)
>> (/home/buildbots/ppc64be-clang-multistage-test/clang-ppc64be-multistage/stage1/bin/clang+0x
Author: David Blaikie
Date: 2020-03-26T20:09:57-07:00
New Revision: 819e540208d5d62e7841d0dbdef3580eecc2c2b6
URL:
https://github.com/llvm/llvm-project/commit/819e540208d5d62e7841d0dbdef3580eecc2c2b6
DIFF:
https://github.com/llvm/llvm-project/commit/819e540208d5d62e7841d0dbdef3580eecc2c2b6.diff
Usually this sort of thing is addressed with llvm_unreachable, rather than
a return statement that's not expected to be reached by any valid execution
of LLVM (it'd require a carefully hand-crafted CPU kind to reach that
return (since all the actual enumerators result in returns earlier, in the
swi
On Thu, Mar 26, 2020 at 8:49 PM Richard Smith wrote:
> On Thu, 26 Mar 2020 at 17:07, David Blaikie via cfe-commits <
> cfe-commits@lists.llvm.org> wrote:
>
>> On Thu, Mar 26, 2020 at 3:12 PM Arthur O'Dwyer
>> wrote:
>>
>>> I'm not sure,
501 - 600 of 1480 matches
Mail list logo