jplehr wrote:
I believe this results in tests failures on our bot:
https://lab.llvm.org/staging/#/builders/105/builds/9796 (and a few others)
https://github.com/llvm/llvm-project/pull/117199
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http
jplehr wrote:
This broke our flang-enabled buildbot
https://lab.llvm.org/staging/#/builders/105/builds/15554
Looking at it currently
https://github.com/llvm/llvm-project/pull/126297
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists
https://github.com/jplehr created
https://github.com/llvm/llvm-project/pull/126495
Reverts llvm/llvm-project#126297
Broken buildbots
https://lab.llvm.org/staging/#/builders/105/builds/15554
https://lab.llvm.org/buildbot/#/builders/30/builds/15490
Error is
```
# .---command stderr
#
https://github.com/jplehr closed
https://github.com/llvm/llvm-project/pull/126495
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
Is there the possibility to set up a buildbot for this architecture?
https://github.com/llvm/llvm-project/pull/120173
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
> Do you mean adding a dedicate buildbot for the `offload` sub-project? I think
> the answer is yes. Actually we plan to setup more buildbots for any other
> sub-projects, including `flang`, `lld` and `openmp`, etc.
Not necessarily a dedicated buildbot for the `offload` project,
jplehr wrote:
Hi @tahonermann do you have an idea on why this is failing?
https://github.com/llvm/llvm-project/pull/120327
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
Can someone more familiar with this push a fix? That would be much appreciated.
Thanks!
https://github.com/llvm/llvm-project/pull/120327
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listi
jplehr wrote:
Thank you.
https://github.com/llvm/llvm-project/pull/95474
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/jplehr approved this pull request.
Fixes a build issue I was hitting in
https://github.com/llvm/llvm-project/pull/123673
https://github.com/llvm/llvm-project/pull/124116
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https:
@@ -24,11 +24,24 @@ namespace offloading {
/// This is the record of an object that just be registered with the offloading
/// runtime.
struct EntryTy {
+ /// Reserved bytes used to detect an older version of the struct, always
zero.
+ uint64_t Reserved = 0x0;
+ /// The cur
jplehr wrote:
This also failed one of our bots:
https://lab.llvm.org/buildbot/#/builders/140/builds/14350
https://github.com/llvm/llvm-project/pull/120266
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/l
jplehr wrote:
> Yep already working on it, integration issue with another change from me, my
> bad
Thank you for working on a fix. :)
https://github.com/llvm/llvm-project/pull/120266
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lis
jplehr wrote:
> Hi, I think this broke two of our buildbots -- for reasons I don't quite
> understand, but reverting fixed the issue locally. Can you please take a look
> at it?
>
> https://lab.llvm.org/buildbot/#/builders/10/builds/980
> https://lab.llvm.org/buildbot/#/builders/73/builds/143
https://github.com/jplehr approved this pull request.
LGTM
thx
https://github.com/llvm/llvm-project/pull/134656
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
I think this broke one of our bots:
https://lab.llvm.org/buildbot/#/builders/10/builds/3726/steps/10/logs/stdio
The bot was red for another issue at the time, but the stack trace includes
methods that are touched in this PR.
This is part of the stack trace:
```
#12 0x748dc31b
jplehr wrote:
I can try later today to get dumps/preprocessed source or maybe some better
idea on how to reproduce the issue.
@jhuber6 if you have immediate thoughts on how to provide that (or maybe even
what may be the issue), let me know.
https://github.com/llvm/llvm-project/pull/136128
jplehr wrote:
> LLVM Buildbot has detected a new failure on builder `clang-hip-vega20`
> running on `hip-vega20-0` while building `clang` at step 3 "annotate".
>
> Full details are available at:
> https://lab.llvm.org/buildbot/#/builders/123/builds/17410
>
> Here is the relevant piece of the
jplehr wrote:
This should be device libs from ROCm 6.3.3.
```
$ apt show rocm-device-libs
Package: rocm-device-libs
Version: 1.0.0.60303-74~22.04
Priority: optional
Section: devel
Maintainer: ROCm Compiler Support
Installed-Size: 3424 kB
Depends: rocm-core
Homepage: https://github.com/RadeonOpe
https://github.com/jplehr approved this pull request.
LGTM
Thanks!
https://github.com/llvm/llvm-project/pull/136317
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
Hi, this turned a few bots red.
Can this be fixed forward or should we revert in the meantime?
Let me know if you need help with the bot setup / build config. Thanks!
https://github.com/llvm/llvm-project/pull/134174
___
cfe-commits mailin
jplehr wrote:
Did anybody to run the OpenMP VV suite before and after this change? Curious to
know if that improves results.
https://github.com/llvm/llvm-project/pull/125648
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.or
jplehr wrote:
> but it turns on LTO by default right?
This is very much how I read that patch too.
Maybe the flag names and comments are a bit misleading here.
https://github.com/llvm/llvm-project/pull/129118
___
cfe-commits mailing list
cfe-commits@l
jplehr wrote:
> I think people are just confusing what `-flto` means when put on a link job.
Including me. :)
Apologies for my ignorance, what does this do and why do we want it?
It allows for some (LTO-related?) flags to be forwarded/handled correctly?
https://github.com/llvm/llvm-project/pul
https://github.com/jplehr approved this pull request.
With the explanation that change seems reasonable. Thank you.
https://github.com/llvm/llvm-project/pull/129118
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/
jplehr wrote:
Hi, I think this broke two of our buildbots -- for reasons I don't quite
understand, but reverting fixed the issue locally.
Can you please take a look at it?
https://lab.llvm.org/buildbot/#/builders/10/builds/980
https://lab.llvm.org/buildbot/#/builders/73/builds/14304
https://gi
https://github.com/jplehr commented:
Certainly an improvement. I think this is good, but do not feel confident right
now to already approve.
https://github.com/llvm/llvm-project/pull/127890
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https
@@ -932,9 +932,18 @@ def W_Joined : Joined<["-"], "W">, Group,
def Xanalyzer : Separate<["-"], "Xanalyzer">,
HelpText<"Pass to the static analyzer">, MetaVarName<"">,
Group;
-def Xarch__ : JoinedAndSeparate<["-"], "Xarch_">, Flags<[NoXarchOption]>,
- HelpText<"Pass to th
https://github.com/jplehr edited
https://github.com/llvm/llvm-project/pull/127890
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
@@ -932,9 +932,18 @@ def W_Joined : Joined<["-"], "W">, Group,
def Xanalyzer : Separate<["-"], "Xanalyzer">,
HelpText<"Pass to the static analyzer">, MetaVarName<"">,
Group;
-def Xarch__ : JoinedAndSeparate<["-"], "Xarch_">, Flags<[NoXarchOption]>,
- HelpText<"Pass to th
@@ -932,9 +932,18 @@ def W_Joined : Joined<["-"], "W">, Group,
def Xanalyzer : Separate<["-"], "Xanalyzer">,
HelpText<"Pass to the static analyzer">, MetaVarName<"">,
Group;
-def Xarch__ : JoinedAndSeparate<["-"], "Xarch_">, Flags<[NoXarchOption]>,
- HelpText<"Pass to th
https://github.com/jplehr approved this pull request.
Thanks for all the comments and addressing concerns.
https://github.com/llvm/llvm-project/pull/125648
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/l
jplehr wrote:
I put up https://github.com/llvm/llvm-project/pull/138959 which removes the
offending `tiny` mcmodel from the Flang driver test. I don't know if this is
the right fix though.
https://github.com/llvm/llvm-project/pull/125643
___
cfe-comm
https://github.com/jplehr approved this pull request.
LG
https://github.com/llvm/llvm-project/pull/142159
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
jplehr wrote:
> It seems I need to add the line `// WARNING-NEXT:
> -Wmain-attached-to-named-module` on this
> [line](https://sourcegraph.com/github.com/llvm/llvm-project/-/blob/clang/test/Driver/autocomplete.c?L114)
> to fix the autocomplete test.
>
> What is the process to amend this PR?
I
jplehr wrote:
A LLVM syncbot commit turned our buildbot red:
https://lab.llvm.org/buildbot/#/builders/123/builds/23254
The syncbot commit links to this PR.
https://github.com/llvm/llvm-project/pull/146830
___
cfe-commits mailing list
cfe-commits@lis
jplehr wrote:
Hi, I don't know why, but it seems that on those machines, some git issue
creped up with some stale refs. I think I resolved them.
Nothing to worry about with this PR ,and apologies for the noise!
https://github.com/llvm/llvm-project/pull/146830
__
101 - 137 of 137 matches
Mail list logo
