Hi,
All the *nix build bots (lldb-x86_86-{debian,fedora}, netbsd-amd64) have
been offline for a while now. Some as far as July 12.
I’m not sure if this is being tracked or whom to contact about this.
Thank you.
- Afonso
--
Best regards,
António Afonso
___
Sean Silva via cfe-dev writes:
>> We have to support many different systems and those systems are always
>> changing (new processors, new BIOS, new OS, etc.). Performance can vary
>> widely day to day from factors completely outside the compiler's
>> control. As the performance changes you have
The build step works with r374250, but the install step fails. It needs
CMAKE_CFG_INTDIR added to:
install(DIRECTORY ${CMAKE_BINARY_DIR}/${LLDB_PYTHON_RELATIVE_PATH}/
DESTINATION ${LLDB_PYTHON_RELATIVE_PATH}
COMPONENT lldb-scripts)
> -Original Message-
>
On Thu, Oct 10, 2019 at 2:21 PM David Greene via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> Florian Hahn via llvm-dev writes:
>
> >> - Performance varies from implementation to implementation. It is
> >> difficult to keep tests up-to-date for all possible targets and
> >> subtargets.
> >
> > C
Hi David,
You answer some of your own questions down below, so I'll try to
collate the responses and shorten my reply.
On Fri, 11 Oct 2019 at 15:20, David Greene wrote:
> How are regressions reported? On llvm-dev?
They're buildbots, exactly like any other. Direct email, llvm-commits,
irc, bugz
Renato Golin via cfe-dev writes:
> On Thu, 10 Oct 2019 at 22:26, David Greene wrote:
>> That would be a shame. Where is test-suite run right now? Are there
>> bots? How are regressions reported?
>
> There is no shame in making the test-suite better.
That's not what I meant, sorry. I mean it
"Robinson, Paul via Openmp-dev" writes:
> David Greene, will you be at the LLVM Dev Meeting? If so, could you sign
> up for a Round Table session on this topic? Obviously lots to discuss
> and concerns to be addressed.
That's a great idea. I will be there. I'm also hoping to help run a
routab
On Thu, 2019-10-10 at 23:11 +, Ted Woodward wrote:
> Starting in r372835 (Fix installing Python modules on systems using
> /usr/lib), the finish_swig and installation steps using multi-configuration
> generators (like Visual Studio or XCode) are broken.
>
> The problem is the symlink and ins
