Displaying 4 results from an estimated 4 matches for "am1i".
2019 Jan 31
2
[RFC] migrating past C++11
...re the buildbots. I audited *all* bots in http://lab.llvm.org:8011/buildslaves (there's so many!). Some of them are down, I therefore have no idea what they run. Here are the bots that will definitely break, with their maintainers:
>
> Galina Kistanova <gkistanova at gmail.com>
> am1i-slv1 -- gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
> as-bldslv4 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
> ps4-buildslave2 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
>
> Hexagon QA <llvm.buildmaster at quicinc.com>
> hexagon-build-02 -- gcc (Ubuntu 4.9.2-10ubuntu13) 4....
2019 Feb 02
2
[RFC] migrating past C++11
...uildslaves> (there's so many!). Some of them are down, I therefore have no idea what they run. Here are the bots that will definitely break, with their maintainers:
>>>
>>> Galina Kistanova <gkistanova at gmail.com <mailto:gkistanova at gmail.com>>
>>> am1i-slv1 -- gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
>>> as-bldslv4 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
>>> ps4-buildslave2 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
>>>
>>> Hexagon QA <llvm.buildmaster at quicinc.com <mailto:llvm.buildmaster...
2019 Feb 07
5
[RFC] migrating past C++11
...tp://lab.llvm.org:8011/buildslaves> (there's so many!). Some of them are down, I therefore have no idea what they run. Here are the bots that will definitely break, with their maintainers:
>
> Galina Kistanova <gkistanova at gmail.com <mailto:gkistanova at gmail.com>>
> am1i-slv1 -- gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
> as-bldslv4 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
> ps4-buildslave2 -- Microsoft (R) Visual Studio (R) 2015 (14.0)
>
> Hexagon QA <llvm.buildmaster at quicinc.com <mailto:llvm.buildmaster at quicinc.com>>
> hexa...
2019 Jan 26
4
[RFC] migrating past C++11
+1, thanks again for driving this.
On Fri, Jan 25, 2019 at 3:57 PM JF Bastien via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> The discussion seems to have died down and gotten good consensus. I’ve
> therefore create a patch which applies the proposed soft-errors:
>
> https://reviews.llvm.org/D57264
>
>
> We’ll only migrate to hard-error (and start using new