Displaying 20 results from an estimated 80 matches for "thakis".
2015 Sep 04
3
Running tests on OS X 10.10 vs "Killed: 9"
...there
some tweakable to tell the kernel "please don't kill my processes"?
Here's an example from just now:
FAIL: LLVM :: MC/X86/shuffle-comments.s (18589 of 28139)
******************** TEST 'LLVM :: MC/X86/shuffle-comments.s' FAILED
********************
Script:
--
/Users/thakis/src/chromefetch/src/third_party/llvm-bootstrap/./bin/llvm-mc
/Volumes/MacintoshHD2/src/chromefetch/src/third_party/llvm/test/MC/X86/shuffle-comments.s
-triple=x86_64-unknown-unknown |
/Users/thakis/src/chromefetch/src/third_party/llvm-bootstrap/./bin/FileCheck
/Volumes/MacintoshHD2/src/chromefetch/...
2018 Nov 20
2
Ninja build (on Windows anyway) may be doing redundant work
...e from the same invocation. Surely ninja could spawn two links, which then independently report "Creating library" after ninja emits the [N/M] lines.
--paulr
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of via llvm-dev
Sent: Tuesday, November 20, 2018 9:01 AM
To: thakis at chromium.org
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Ninja build (on Windows anyway) may be doing redundant work
OK, worth knowing. Thanks.
--paulr
From: Nico Weber [mailto:thakis at chromium.org]
Sent: Monday, November 19, 2018 7:11 PM
To: Robinson, Paul
Cc: Zachary Turner; ll...
2018 Nov 20
2
Ninja build (on Windows anyway) may be doing redundant work
...o
with it.
On Mon, Nov 19, 2018 at 6:57 PM <paul.robinson at sony.com> wrote:
> I'm more concerned about seeing the message come out twice, which implies
> Ninja is executing a rule twice when it doesn't need to.
>
> --paulr
>
>
>
> *From:* Nico Weber [mailto:thakis at chromium.org]
> *Sent:* Monday, November 19, 2018 6:09 PM
> *To:* Zachary Turner
> *Cc:* Robinson, Paul; llvm-dev
> *Subject:* Re: [llvm-dev] Ninja build (on Windows anyway) may be doing
> redundant work
>
>
>
> Do you still see this if you use lld-link for linking?
&g...
2015 Sep 04
2
[cfe-dev] Running tests on OS X 10.10 vs "Killed: 9"
...lar development? (what combination of LLVM repos were
> checked out and being tested simultaneously?)
>
> -- Sean Silva
>
>
>> ******************** TEST 'LLVM :: MC/X86/shuffle-comments.s' FAILED
>> ********************
>> Script:
>> --
>> /Users/thakis/src/chromefetch/src/third_party/llvm-bootstrap/./bin/llvm-mc
>> /Volumes/MacintoshHD2/src/chromefetch/src/third_party/llvm/test/MC/X86/shuffle-comments.s
>> -triple=x86_64-unknown-unknown |
>> /Users/thakis/src/chromefetch/src/third_party/llvm-bootstrap/./bin/FileCheck
>> /V...
2019 Jun 06
4
Adding llvm-undname to the llvm-cov bot
On Wed, Jun 5, 2019 at 1:33 PM <vsk at apple.com> wrote:
>
>
> On Jun 4, 2019, at 4:41 PM, Nico Weber <thakis at chromium.org> wrote:
>
> On Mon, Jun 3, 2019 at 2:06 PM <vsk at apple.com> wrote:
>
>> Hi Nico,
>>
>> Sorry for the delay, I've been OOO. The llvm-cov bot should produce
>> reports for llvm-undname starting today.
>>
>
> Thanks! It looks...
2019 Jun 10
2
Adding llvm-undname to the llvm-cov bot
On Mon, Jun 10, 2019 at 2:11 PM <vsk at apple.com> wrote:
>
>
> On Jun 6, 2019, at 9:56 AM, Nico Weber <thakis at chromium.org> wrote:
>
> On Wed, Jun 5, 2019 at 1:33 PM <vsk at apple.com> wrote:
>
>>
>>
>> On Jun 4, 2019, at 4:41 PM, Nico Weber <thakis at chromium.org> wrote:
>>
>> On Mon, Jun 3, 2019 at 2:06 PM <vsk at apple.com> wrote:
>>...
2020 Feb 14
5
Moving the AVR backend out of experimental
...os and cons of making it a stable target? Does anyone else have any concerns about doing so?
-Chris
> On Feb 14, 2020, at 7:59 AM, Nico Weber via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> +better dylanmckay address
>
> On Fri, Feb 14, 2020 at 10:58 AM Nico Weber <thakis at chromium.org <mailto:thakis at chromium.org>> wrote:
> Hi,
>
> There was a thread a few days ago about the expectations for experimental targets. At the moment, the only experimental target is AVR. It's been in the tree for a long time now, and generally seems well-behaved...
2019 May 31
2
Adding llvm-undname to the llvm-cov bot
...an may have a better idea.
I'm reasonably certain that the missing +x is just an oversight.
-Chris
> On May 30, 2019, at 6:24 PM, Nico Weber via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Vedant or Chris: Ping :)
>
> On Wed, May 29, 2019 at 7:56 AM Nico Weber <thakis at chromium.org <mailto:thakis at chromium.org>> wrote:
> Hi Vedant and Chris,
>
> is the config for http://lab.llvm.org:8080/coverage/coverage-reports/index.html <http://lab.llvm.org:8080/coverage/coverage-reports/index.html> public somewhere? If so, where? (I looked in zo...
2020 Sep 01
2
[cfe-dev] Can we remove llvmbb from IRC?
On Tue, Sep 1, 2020 at 3:57 PM David Blaikie <dblaikie at gmail.com> wrote:
>
>
> On Tue, Sep 1, 2020 at 12:42 PM Nico Weber <thakis at chromium.org> wrote:
>
>> On Tue, Sep 1, 2020 at 3:32 PM David Blaikie <dblaikie at gmail.com> wrote:
>>
>>> On Tue, Sep 1, 2020 at 12:07 PM Nico Weber via cfe-dev <
>>> cfe-dev at lists.llvm.org> wrote:
>>>
>>>> Hi,
>>&g...
2018 Sep 06
3
Did anything weird happen to the git monorepo?
Hi,
I got a forced update when pulling today. If I merge master to a local
branch, I get a bunch of add/add conflicts.
This same commit exists under several hashes:
https://github.com/llvm-project/llvm-project-20170507/commit/687841777ef505
https://github.com/llvm-project/llvm-project-20170507/commit/74725885552
Did someone push -f to the monorepo after doing branch surgery?
Maybe there was a
2018 Nov 19
2
Ninja build (on Windows anyway) may be doing redundant work
Do you still see this if you use lld-link for linking?
The "corrupt obj file" is something we saw on chrome's bots every now and
then before we switched to lld.
On Mon, Nov 19, 2018 at 5:27 PM Zachary Turner <zturner at google.com> wrote:
> +Nico Weber <thakis at google.com>
>
> On Mon, Nov 19, 2018 at 12:25 PM via llvm-dev <llvm-dev at lists.llvm.org>
> wrote:
>
>> This afternoon I did a clean build of llvm using ninja and MSVC 2015 on
>> Windows 10. I saw something curious and wondered if any of the ninja or
>> CM...
2015 Jul 24
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
On Fri, Jul 24, 2015 at 12:05 PM, Nico Weber <thakis at chromium.org> wrote:
> On Thu, Jul 16, 2015 at 8:08 AM, Nico Weber <thakis at chromium.org> wrote:
>
>> On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace <
>> russell.wallace at gmail.com> wrote:
>>
>>> Basic test results on Windows 7, visual stud...
2013 Sep 12
3
[LLVMdev] Let's not depend on terminfo / curses?
On Mon, Sep 9, 2013 at 12:24 AM, Renato Golin <renato.golin at linaro.org>wrote:
> On 9 September 2013 01:09, Nico Weber <thakis at chromium.org> wrote:
>
>> I think depending on curses is gross,
>>
>
> I totally agree, but I also don't have a better way of doing this. I agree
> with Joerg that hard-coding escape sequences is not the way forward.
>
llvm is still hard-coding escape sequences...
2016 Sep 01
3
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
...n as possible? Once VS 2015 is the minimum, it doesn't seem like we
should worry too much about upgrading compiler versions anymore (aside from
the effort to actually do it and make sure it works and the compiler bugs
and issues are known about).
On Thu, Sep 1, 2016 at 12:24 PM Nico Weber <thakis at chromium.org> wrote:
> On Thu, Sep 1, 2016 at 3:16 PM, Zachary Turner <zturner at google.com> wrote:
>
>> I don't see how the policy of supporting 2 versions is related to that
>> difficulty though. Whether we support 1 versions or 2 versions, 1 version
>> i...
2019 May 29
2
Adding llvm-undname to the llvm-cov bot
Hi Vedant and Chris,
is the config for
http://lab.llvm.org:8080/coverage/coverage-reports/index.html public
somewhere? If so, where? (I looked in zorg but didn't find it.)
If not, could you add "llvm-undname" to the list of binaries passed to
llvm/utils/prepare-code-coverage-artifact.py so that
llvm/lib/Demangle/MicrosoftDemangle.cpp (and friends) show up? (If the
config is public,
2019 Dec 17
2
Python 2 compatibility for utility scripts
On Tue, Dec 17, 2019 at 12:55 PM Nico Weber <thakis at chromium.org> wrote:
> On Tue, Dec 17, 2019 at 12:41 PM James Y Knight <jyknight at google.com>
> wrote:
>
>> It sounds like you ran into a bug in the test infrastructure's code to
>> determine if python3 is supported. Fixing that might be harder, but it only
&...
2019 Jul 31
2
buildbot failure in LLVM on sanitizer-x86_64-linux-gn
vitalybuka, sanitizer-x86_64-linux-gn is _still_ on
http://lab.llvm.org:8011/console . Can we please get it removed?
On Wed, Jul 3, 2019 at 7:07 AM Nico Weber <thakis at chromium.org> wrote:
> https://reviews.llvm.org/D63909 landed. Maybe it needs a master restart
> to have an effect?
>
> On Wed, Jul 3, 2019 at 1:03 PM Roman Lebedev <lebedev.ri at gmail.com> wrote:
>
>> Why does GN bot still send mails?
>> I thought it got fi...
2020 Nov 11
2
lld :: ELF/invalid/symtab-sh-info.s is flaky on Windows
lld/test/ELF/invalid/symtab-sh-info.s (check-lld-elf) is recently flaky on
Windows, e.g.
https://reviews.llvm.org/harbormaster/unit/view/192869/
http://45.33.8.238/win/27684/step_10.txt
It fails like every 3 or 4 builds. Could someone with a Windows machine
check what is going on? Is that due to output non-determinism (just my
guess) in yaml2obj.exe?
-------------- next part --------------
An
2019 Jun 04
2
Adding llvm-undname to the llvm-cov bot
...>
> I'm reasonably certain that the missing +x is just an oversight.
>
> -Chris
>
> On May 30, 2019, at 6:24 PM, Nico Weber via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Vedant or Chris: Ping :)
>
> On Wed, May 29, 2019 at 7:56 AM Nico Weber <thakis at chromium.org> wrote:
>
>> Hi Vedant and Chris,
>>
>> is the config for
>> http://lab.llvm.org:8080/coverage/coverage-reports/index.html public
>> somewhere? If so, where? (I looked in zorg but didn't find it.)
>>
>> If not, could you add "...
2020 Sep 01
2
[cfe-dev] Can we remove llvmbb from IRC?
On Tue, Sep 1, 2020 at 3:32 PM David Blaikie <dblaikie at gmail.com> wrote:
> On Tue, Sep 1, 2020 at 12:07 PM Nico Weber via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
>> Hi,
>>
>> llvmbb's job is to inform people of build breaks. However, it seems to
>> trigger for a big list of bots, and at least one of them seems to always be
>>