carlosgalvezp wrote:
A bit late for the review but would have been nice to name the test
"out-of-line" instead of "ool", so it's easier to understand what it's about.
https://github.com/llvm/llvm-project/pull/91954
___
cfe-commits mailing list
carlosgalvezp wrote:
I realize it's probably very hard (if not impossible) to detect whether a class
is a base class unless it has virtual functions.
That's why the corresponding AUTOSAR rule bans only non-final classes. But that
is a bit overkill and leads to some pain.
carlosgalvezp wrote:
Otherwise since this is a problem also on non-polymorphic objects, maybe
"bugprone-pointer-arithmetic-base-class"?
https://github.com/llvm/llvm-project/pull/91951
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
carlosgalvezp wrote:
I'm not very happy about the name, there's no such thing as "virtual
arithmetic".
What about "bugprone-pointer-arithmetic-polymorphic-object"?
I rather have a long descriptive name than a short ambiguous name.
https://github.com/llvm/llvm-project/pull/91951
carlosgalvezp wrote:
Consider also that this check should probably not apply to variables of type
`auto`, see AUTOSAR rule A8-5-3.
https://github.com/llvm/llvm-project/pull/91124
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
carlosgalvezp wrote:
Regarding the problem of {} initialization and std::vector, I believe we could
restrict this check to not warn on classes that have a constructor taking a
`std:: initializer_list`. I believe AUTOSAR has an exception for that.
carlosgalvezp wrote:
> Should I implement auto-fix for this check?
As a first step we can have it without auto-fix and add that as a second step
once we figure out a good way to do it.
https://github.com/llvm/llvm-project/pull/90830
___
cfe-commits
carlosgalvezp wrote:
- I'm not sure this is so much a readability check, I'd put it in `misc`. The
main problem that it solves is avoiding ODR violations. I'd call it
`misc-prefer-internal-linkage`.
- The auto-fix should be configurable to choose `static` or anonymous namespace.
carlosgalvezp wrote:
Please note: the guidelines do not require one to replace [] with at(), that's
just one of the possible solutions. Actually at() is banned in many codebases
where exceptions are banned.
It would be good to make this fix-it opt-in, configurable via option, so the
check
carlosgalvezp wrote:
Great! Nothing else from my side
https://github.com/llvm/llvm-project/pull/87792
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
carlosgalvezp wrote:
Nice! Should we add this example as a test case?
https://github.com/llvm/llvm-project/pull/87792
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
carlosgalvezp wrote:
> the user may not have the ability to change the definition of the macro to be
> able to appease the check
My understanding of this PR is that the user would only need to change what
they pass into the macro, not the macro itself, or? E.g.
```cpp
-MY_MACRO(foo)
carlosgalvezp wrote:
Shouldn't we simply `return`?
As you say, the assert is disabled in Release mode. Even if it's enabled, the
author if `getSubExpr` may one day decide to remove the assert without possibly
knowing all the places that do rely on that assert, leaving the code
unprotected.
@@ -97,6 +97,9 @@ The improvements are...
Improvements to clang-tidy
--
+- Improved :program:`run-clang-tidy.py` script. Added argument `-source-filter`
+ to filter out source files from the compilation database.
carlosgalvezp wrote:
carlosgalvezp wrote:
> Why "ignore" instead of "filter"?
Why can't we make "filter" use a full regex that supports negative expressions
instead?
https://github.com/llvm/llvm-project/pull/82416
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
carlosgalvezp wrote:
This problem seems like it should be handled globally, not in a single specific
check. IIUC any check that reads options from the .cñsng-tidy file is affected.
What build system are you using, bazel? We use it and don't have any problems.
If your build system creates a
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/80333
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/80333
>From b40347c8025b0d5de83453012a76d412c07f54a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Thu, 1 Feb 2024 20:00:45 +
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/80330
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/80333
>From fbb0837342a566ff928b211cbb418075a7e744fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Thu, 1 Feb 2024 20:00:45 +
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/80333
…ationFileExtensions
Deprecated since clang-tidy 17. Use the corresponding global options instead.
Fixes #61947
>From fbb0837342a566ff928b211cbb418075a7e744fe Mon Sep 17 00:00:00 2001
From:
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/80330
This functionality already exists in
cppcoreguidelines-use-default-member-init. It was deprecated from this check in
clang-tidy 17.
This allows us to
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/80193
>From bfa4ea36a2695ec8d6ea92db588f91d5c818968a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Wed, 31 Jan 2024 20:25:27 +
carlosgalvezp wrote:
Thanks for the review! I agree, check names are not the best. It's a bit of a
hassle to change them though :/
I will fix the comment about the release notes tonight :+1:
https://github.com/llvm/llvm-project/pull/80193
___
@@ -230,139 +197,99 @@ void PreferMemberInitializerCheck::check(
updateAssignmentLevel(Field, InitValue, Ctor, AssignedFields);
if (!canAdvanceAssignment(AssignedFields[Field]))
continue;
-const bool IsInDefaultMemberInitializer =
-
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/80193
…refer-member-init
This functionality already exists in
cppcoreguidelines-use-default-member-init. It was deprecated from this check in
clang-tidy 17.
This allows us to fully decouple this check from the
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/80181
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
carlosgalvezp wrote:
The code formatting job seems to produce incorrect changes.
https://github.com/llvm/llvm-project/pull/80181
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/80181
Deprecated since clang-tidy 17. The rule DCL21-CPP has been removed from the
CERT guidelines, so it does not make sense to keep the check.
Fixes #42788
>From fdb65ef4805152ad143a120e343d696f8b08d3db Mon
carlosgalvezp wrote:
Thanks for understanding @11happy ! As you say the learning experience is
invaluable and will be very useful for the next check. All contributions are
greatly appreciated :)
I can recommend you look into fairly recent issues - older issues may not have
been reviewed
carlosgalvezp wrote:
I agree with the opinions from Aaron And Piotr above - this check does the
opposite of readability: it forces people to waste time digging into the
Standard to find the quote that says the return is not needed.
Could some argumentation be provided as to why this would be
carlosgalvezp wrote:
Apologies for the late reply, need to fix my mail filter so I don't miss the
notifications!
IMHO either modernize or readability are suitable categories. Performance can
vary/be negligible depending on context I suppose?
https://github.com/llvm/llvm-project/pull/72385
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/67528
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/67528
>From 08b5c95bea5b7bfceeae6dfc4deac764faff87a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Wed, 27 Sep 2023 08:07:01 +
Carlos =?utf-8?q?G=C3=A1lvez?= ,
Carlos =?utf-8?q?G=C3=A1lvez?=
Message-ID:
In-Reply-To:
carlosgalvezp wrote:
Friendly ping @AaronBallman @shafik
https://github.com/llvm/llvm-project/pull/67528
___
cfe-commits mailing list
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
carlosgalvezp 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 merging?
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/67528
>From 7a70366e08f2c2f1181bb74f7716d8b1e3f1b62e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Wed,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp resolved
https://github.com/llvm/llvm-project/pull/67528
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
carlosgalvezp wrote:
I would need some help with the failing pre-merge test, I don't really
understand why that failure would be related to this patch...
https://github.com/llvm/llvm-project/pull/67528
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/67528
>From f9c4fb4e0a5a9017da6214fb0d98f45f89ee16be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Wed,
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
@@ -405,7 +405,8 @@ def warn_fixedpoint_constant_overflow : Warning<
InGroup>;
def warn_constexpr_unscoped_enum_out_of_range : Warning<
"integer value %0 is outside the valid range of values [%1, %2] for the "
-
Carlos =?utf-8?q?Gálvez?=
Message-ID:
In-Reply-To:
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/67528
>From f9c4fb4e0a5a9017da6214fb0d98f45f89ee16be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Wed, 27 Sep 2023 08:07:01 +
@@ -405,7 +405,8 @@ def warn_fixedpoint_constant_overflow : Warning<
InGroup>;
def warn_constexpr_unscoped_enum_out_of_range : Warning<
"integer value %0 is outside the valid range of values [%1, %2] for the "
- "enumeration type %3">, DefaultError,
InGroup>;
+
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/67528
…macros
As per review comments on https://reviews.llvm.org/D150226, we should allow for
one more release before turning this warning into a hard error, by making it
visible in system headers and macros,
carlosgalvezp wrote:
Thanks @shafik , I wasn't aware! I will then close this PR and continue the
discussion on Phab.
https://github.com/llvm/llvm-project/pull/67170
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/67170
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
carlosgalvezp wrote:
Not sure what happens with the failed job in CI, I rebased on latest trunk and
ran the entire `ninja check-clang` suite and it passed successfully. Do I need
some special CMake configuration flag to enable the failing test?
About the patch itself - casting outside of
carlosgalvezp wrote:
To clarify, I'm not concerned about performance, but with code readability and
maintainability.
I realize the chain that I wrote above should not lead to recursion due to
`SkipMethods::Yes` in the relevant call. I'd like to take a closer look at the
problem, would you
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/67170
Casting an int into an enum is undefined behavior if the int is outside of the
range of the enum. UB is not allowed in constant expressions, therefore the
compiler must produce a hard error in that case.
carlosgalvezp wrote:
Being totally unfamiliar with the code, I have a feeling that we shouldn't be
fixing in the `analyze` function. `analyze` has 1 single responsibility: wrap
`analyzeImpl` in order to add cacheability for performance reasons, and it does
so simply and well, and it does
https://github.com/carlosgalvezp approved this pull request.
LGTM, thanks for the fix and the great cleanup!
https://github.com/llvm/llvm-project/pull/66835
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
@@ -729,3 +729,21 @@ struct forward_declared_as_struct;
class forward_declared_as_struct {
};
+namespace pr55156 {
+
+typedef enum {
+ VALUE0,
+ VALUE1,
+} ValueType;
+// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: invalid case style for typedef
'ValueType'
https://github.com/carlosgalvezp resolved
https://github.com/llvm/llvm-project/pull/66835
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -729,3 +729,21 @@ struct forward_declared_as_struct;
class forward_declared_as_struct {
};
+namespace pr55156 {
+
+typedef enum {
+ VALUE0,
+ VALUE1,
+} ValueType;
+// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: invalid case style for typedef
'ValueType'
@@ -207,11 +211,13 @@ void UseEmplaceCheck::registerMatchers(MatchFinder
*Finder) {
auto HasConstructExpr = has(ignoringImplicit(SoughtConstructExpr));
// allow for T{} to be replaced, even if no CTOR is declared
- auto HasConstructInitListExpr = has(initListExpr(anyOf(
@@ -207,11 +211,13 @@ void UseEmplaceCheck::registerMatchers(MatchFinder
*Finder) {
auto HasConstructExpr = has(ignoringImplicit(SoughtConstructExpr));
// allow for T{} to be replaced, even if no CTOR is declared
- auto HasConstructInitListExpr = has(initListExpr(anyOf(
@@ -1332,6 +1337,17 @@ void testBracedInitTemporaries() {
v3.push_back(NonTrivialWithCtor{{}});
v3.push_back({{0}});
v3.push_back({{}});
+
+ std::vector v4;
+
+ // These should not be noticed or fixed; after the correction, the code won't
+ // compile.
+
https://github.com/carlosgalvezp commented:
Should this change be reflected in the Release Notes?
https://github.com/llvm/llvm-project/pull/66504
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
carlosgalvezp wrote:
Thanks for the detailed response @adriannistor !
> will soon become a lot of if-then-else blocks.
In general the decision as to which checks to have should be based on Coding
Guidelines and user-facing experience - not on implementation complexity. In
that sense, as a
@@ -0,0 +1,34 @@
+.. title:: clang-tidy - google-cpp-init-class-members
+
+google-cpp-init-class-members
+=
+
+Checks that class members are initialized in constructors (implicitly or
+explicitly). Reports constructors or classes where class members
@@ -0,0 +1,34 @@
+.. title:: clang-tidy - google-cpp-init-class-members
+
+google-cpp-init-class-members
+=
+
+Checks that class members are initialized in constructors (implicitly or
+explicitly). Reports constructors or classes where class members
@@ -0,0 +1,32 @@
+.. title:: clang-tidy - google-cpp-init-class-members
+
+google-cpp-init-class-members
+=
+
+Checks that class members are initialized in constructors (implicitly or
+explicitly). Reports constructors or classes where class members
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp closed
https://github.com/llvm/llvm-project/pull/65231
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp resolved
https://github.com/llvm/llvm-project/pull/65231
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17
Carlos =?utf-8?q?G=C3=A1lvez?= ,
Carlos =?utf-8?q?G=C3=A1lvez?= ,
Carlos =?utf-8?q?G=C3=A1lvez?= ,
Carlos =?utf-8?q?G=C3=A1lvez?=
carlosgalvezp wrote:
Yes good point, will fix!
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
carlosgalvezp wrote:
Yep, we could certainly change it to C++11 or later, but I think it's out of
the scope for this NFC patch. Regarding documentation, I haven't seen that we
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
@@ -3,22 +3,37 @@
modernize-use-equals-delete
===
-This check marks unimplemented private special member functions with ``=
delete``.
-To
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17 00:00:00 2001
From:
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date:
Carlos =?utf-8?q?Gálvez?= ,
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Sun, 3 Sep 2023 18:24:55 +
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp resolved
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Carlos =?utf-8?q?Gálvez?=
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Sun, 3 Sep 2023 18:24:55 +
Subject: [PATCH 1/2]
https://github.com/carlosgalvezp edited
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/carlosgalvezp updated
https://github.com/llvm/llvm-project/pull/65231:
>From 9c5fec5e31f31b59262646625b7d34f23d57d6cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Carlos=20G=C3=A1lvez?=
Date: Sun, 3 Sep 2023 18:24:55 +
Subject: [PATCH] [clang-tidy][NFC][doc] Improve
https://github.com/carlosgalvezp review_requested
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/carlosgalvezp review_requested
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/carlosgalvezp created
https://github.com/llvm/llvm-project/pull/65231:
…-delete
So the purpose of the check is more clear. Update examples code to show
compliant code.
>From 0ffc7aab2f385babd81b57e8116b0433d85cfaf2 Mon Sep 17 00:00:00 2001
From:
https://github.com/carlosgalvezp review_requested
https://github.com/llvm/llvm-project/pull/65231
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/carlosgalvezp approved this pull request.
LGTM!
https://github.com/llvm/llvm-project/pull/65202
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
Author: Carlos Galvez
Date: 2023-07-30T12:10:48Z
New Revision: 2992d084774f44e7626a7d640fe6c30163db450e
URL:
https://github.com/llvm/llvm-project/commit/2992d084774f44e7626a7d640fe6c30163db450e
DIFF:
https://github.com/llvm/llvm-project/commit/2992d084774f44e7626a7d640fe6c30163db450e.diff
Author: Carlos Galvez
Date: 2023-07-26T10:26:43Z
New Revision: b7c6b39651b3ffdabf0081c45e0455a04a8be992
URL:
https://github.com/llvm/llvm-project/commit/b7c6b39651b3ffdabf0081c45e0455a04a8be992
DIFF:
https://github.com/llvm/llvm-project/commit/b7c6b39651b3ffdabf0081c45e0455a04a8be992.diff
Author: Carlos Galvez
Date: 2023-07-19T12:05:15Z
New Revision: b70e6e9681925ad06d9899462b9e43250be53f64
URL:
https://github.com/llvm/llvm-project/commit/b70e6e9681925ad06d9899462b9e43250be53f64
DIFF:
https://github.com/llvm/llvm-project/commit/b70e6e9681925ad06d9899462b9e43250be53f64.diff
Author: Carlos Galvez
Date: 2023-05-09T16:45:02Z
New Revision: 0d6d8a853a6ea29b5f461a475a8f8eb7e7ba18e2
URL:
https://github.com/llvm/llvm-project/commit/0d6d8a853a6ea29b5f461a475a8f8eb7e7ba18e2
DIFF:
https://github.com/llvm/llvm-project/commit/0d6d8a853a6ea29b5f461a475a8f8eb7e7ba18e2.diff
Author: Carlos Galvez
Date: 2023-05-07T16:36:30Z
New Revision: 26f476286fbcb5cde51176abb2d3c6c0986bc410
URL:
https://github.com/llvm/llvm-project/commit/26f476286fbcb5cde51176abb2d3c6c0986bc410
DIFF:
https://github.com/llvm/llvm-project/commit/26f476286fbcb5cde51176abb2d3c6c0986bc410.diff
Author: Carlos Galvez
Date: 2023-04-17T06:09:59Z
New Revision: b507bda4552347e00197032526c7ab4a80a853c2
URL:
https://github.com/llvm/llvm-project/commit/b507bda4552347e00197032526c7ab4a80a853c2
DIFF:
https://github.com/llvm/llvm-project/commit/b507bda4552347e00197032526c7ab4a80a853c2.diff
Author: Nathan James
Date: 2023-04-15T15:07:44Z
New Revision: 4530c3bc4897f6633577de07b61ceb1bf7e79f50
URL:
https://github.com/llvm/llvm-project/commit/4530c3bc4897f6633577de07b61ceb1bf7e79f50
DIFF:
https://github.com/llvm/llvm-project/commit/4530c3bc4897f6633577de07b61ceb1bf7e79f50.diff
LOG:
Author: Carlos Galvez
Date: 2023-04-15T14:49:20Z
New Revision: d69c362dfdc09d9b866cbce007e6342c17af2b2a
URL:
https://github.com/llvm/llvm-project/commit/d69c362dfdc09d9b866cbce007e6342c17af2b2a
DIFF:
https://github.com/llvm/llvm-project/commit/d69c362dfdc09d9b866cbce007e6342c17af2b2a.diff
Author: Carlos Galvez
Date: 2023-04-15T12:07:18Z
New Revision: fa3de2ed2964d18dd0b7457e77416fb4e688c8bd
URL:
https://github.com/llvm/llvm-project/commit/fa3de2ed2964d18dd0b7457e77416fb4e688c8bd
DIFF:
https://github.com/llvm/llvm-project/commit/fa3de2ed2964d18dd0b7457e77416fb4e688c8bd.diff
Author: Carlos Galvez
Date: 2023-04-15T10:10:04Z
New Revision: eedbe81b1c6dfbd85c2a46093e9e862335ad6516
URL:
https://github.com/llvm/llvm-project/commit/eedbe81b1c6dfbd85c2a46093e9e862335ad6516
DIFF:
https://github.com/llvm/llvm-project/commit/eedbe81b1c6dfbd85c2a46093e9e862335ad6516.diff
Author: Carlos Galvez
Date: 2023-04-10T19:31:33Z
New Revision: 132f1d31fd66c30baf9773bf8f37b36a40fa7039
URL:
https://github.com/llvm/llvm-project/commit/132f1d31fd66c30baf9773bf8f37b36a40fa7039
DIFF:
https://github.com/llvm/llvm-project/commit/132f1d31fd66c30baf9773bf8f37b36a40fa7039.diff
Author: Carlos Galvez
Date: 2023-04-05T06:33:40Z
New Revision: 712dfec1781db8aa92782b98cac5517db548b7f9
URL:
https://github.com/llvm/llvm-project/commit/712dfec1781db8aa92782b98cac5517db548b7f9
DIFF:
https://github.com/llvm/llvm-project/commit/712dfec1781db8aa92782b98cac5517db548b7f9.diff
Author: Carlos Galvez
Date: 2023-04-01T19:19:00Z
New Revision: 2469bd98a77242606426f8a5a8a797054c932bf0
URL:
https://github.com/llvm/llvm-project/commit/2469bd98a77242606426f8a5a8a797054c932bf0
DIFF:
https://github.com/llvm/llvm-project/commit/2469bd98a77242606426f8a5a8a797054c932bf0.diff
Author: Carlos Galvez
Date: 2023-03-28T20:36:34Z
New Revision: 4d4c0f9734607bb0423593b060b8fa73c06fe3d3
URL:
https://github.com/llvm/llvm-project/commit/4d4c0f9734607bb0423593b060b8fa73c06fe3d3
DIFF:
https://github.com/llvm/llvm-project/commit/4d4c0f9734607bb0423593b060b8fa73c06fe3d3.diff
Author: Carlos Galvez
Date: 2023-03-26T16:41:17Z
New Revision: 556600af6a8a7f241277f7a22c3e3746e7b09123
URL:
https://github.com/llvm/llvm-project/commit/556600af6a8a7f241277f7a22c3e3746e7b09123
DIFF:
https://github.com/llvm/llvm-project/commit/556600af6a8a7f241277f7a22c3e3746e7b09123.diff
Author: Carlos Galvez
Date: 2023-03-24T07:22:04Z
New Revision: f957b8fe1efe34ac04d1b2e6381e44edcef056b3
URL:
https://github.com/llvm/llvm-project/commit/f957b8fe1efe34ac04d1b2e6381e44edcef056b3
DIFF:
https://github.com/llvm/llvm-project/commit/f957b8fe1efe34ac04d1b2e6381e44edcef056b3.diff
Author: Carlos Galvez
Date: 2023-03-23T10:30:15Z
New Revision: b7677846da66fd003a538f87fd8de948cfcc3d6a
URL:
https://github.com/llvm/llvm-project/commit/b7677846da66fd003a538f87fd8de948cfcc3d6a
DIFF:
https://github.com/llvm/llvm-project/commit/b7677846da66fd003a538f87fd8de948cfcc3d6a.diff
Author: Carlos Galvez
Date: 2023-03-23T08:31:12Z
New Revision: b08d35f826a6b7696a02f1d811da7a2f951e74a1
URL:
https://github.com/llvm/llvm-project/commit/b08d35f826a6b7696a02f1d811da7a2f951e74a1
DIFF:
https://github.com/llvm/llvm-project/commit/b08d35f826a6b7696a02f1d811da7a2f951e74a1.diff
Author: Carlos Galvez
Date: 2023-03-22T18:51:51Z
New Revision: 7e5c48b8bd9ff0ee5de3ba28c833f1225f14e44d
URL:
https://github.com/llvm/llvm-project/commit/7e5c48b8bd9ff0ee5de3ba28c833f1225f14e44d
DIFF:
https://github.com/llvm/llvm-project/commit/7e5c48b8bd9ff0ee5de3ba28c833f1225f14e44d.diff
1 - 100 of 147 matches
Mail list logo
