search for: ps4

Should "lit :: shtest-format.py" (from check-lit) be marked unsupported on PS4? It seems flakey there. This evening, it failed on my commit, r337514, and I'm fairly confident it wasn't my commit's fault. Then it recovered on the next commit. http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast/builds/33502 <http://lab.llvm.org:8011/b...

FWIW, I've seen it fail on some of my commits too, but I don't remember whether it was on the PS4 bot exclusively or not. Anyway, my understanding is that this test shouldn't inherently have different behaviour on PS4 specifically, but I could be mistaken. I suspect it's something more general to do with the configuration of the bot. James On 20 July 2018 at 03:52, Justin Bogner via l...

As I've left Sony, I should handoff code ownership of the PS4 triple. Sony is still committed to LLVM and I look forward to continue to work with them in open source. Sony has asked that I nominate Paul Robinson to become code owner. +------------------------------------------------------------+ | Alexander M. Rosenberg <mailto:alexr at leftfield....

...------- Index: buildbot/osuosl/master/config/slaves.py =================================================================== --- buildbot/osuosl/master/config/slaves.py (revision 259443) +++ buildbot/osuosl/master/config/slaves.py (working copy) @@ -183,6 +183,9 @@ # Ubuntu 14.04 x86_64-scei-ps4, 2 x Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz create_slave("ps4-buildslave1", properties={'jobs': 72}, max_builds=1), + # Windows 10 Pro x86_64-scei-ps4, 2 x Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz + create_slave("ps4-buildslave2", properties=...

Hello everyone, I have configured buildbot to report build statuses to github. It is running in a pilot mode. Only the following 4 builders annotate revisions they build for now: * llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast * llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast * llvm-clang-x86_64-expensive-checks-ubuntu * llvm-clang-x86_64-win-fast Please let me know if you have any questions, concerns, or see any issues. Thanks Galina -------------- next part -------------- An HTML attachment was scrubbed...

Hello, I've compiled Samba 3.0.0 with CUPS support. I verified this: # ldd /usr/local/samba/sbin/smbd *snip* libcups.so.2 => /usr/lib/libcups.so.2 (0x400dc000) *snip* My smb.conf was copied from the HOWTO and the relevant sections look like: [global] *snip* # print support load printers = yes printing = cups printcap name = cups *snip* [printers] comment = All

As you might have noticed, we’ve begun landing patches to open source the Sony PlayStation®4 system compiler. Many more are coming. I’d like to propose that I be named code owner for this platform. I already have this role internally for open source. It feels necessary to establish as part of the process to handle external contributions. ----------------------------------------- Alex Rosenberg

Jake and I have been integrating IRPGO on PS4, and we've identified 3 remaining work items. - Driver changes We'd like to make IRPGO the default on PS4. We also think that it would be beneficial to make IRPGO the default PGO on all platforms (coverage would continue to use FE instr as it does currently, of course). In previous conve...

Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB" or in other words "on for GDB only." "not LLDB" wouldn'...

On Wed, May 25, 2016 at 12:12 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > On Mon, May 23, 2016 at 8:23 PM, Sean Silva <chisophugis at gmail.com> wrote: > >> Jake and I have been integrating IRPGO on PS4, and we've identified 3 >> remaining work items. >> >> >> - Driver changes >> >> We'd like to make IRPGO the default on PS4. We also think that it would >> be beneficial to make IRPGO the default PGO on all platforms (coverage >> would continu...

...We use this to measure changes to stack size between versions of the compiler and it also allows our licensees to do the same for their code. The section simply contains pairs of function symbol references (8 byte) and stack sizes (unsigned LEB128). We would like to upstream this change as a PS4 only modification, or as a more general cross platform one. Would people be interested in (or happy with) such a patch, target specific or otherwise? Thanks, Sean Eveson SN Systems - Sony Interactive Entertainment -------------- next part -------------- An HTML attachment was scrubbed... URL...

...about what they want from the DWARF info for a program. Our first line of defense of course is the DWARF standard itself, but as we've seen, that is not a universally definitive reference. LLVM already emits DWARF slightly differently for different *targets*; primarily Darwin, in a few cases PS4. But in at least some cases, the target is just a (somewhat unreliable) proxy for which *debugger* the compiler expects to be consuming the DWARF. The most instructive case is the exact DWARF expression used to describe the location of a thread- local variable. DWARF v3 defined an operator to fi...

On Mon, May 23, 2016 at 8:23 PM, Sean Silva <chisophugis at gmail.com> wrote: > Jake and I have been integrating IRPGO on PS4, and we've identified 3 > remaining work items. > > > - Driver changes > > We'd like to make IRPGO the default on PS4. We also think that it would be > beneficial to make IRPGO the default PGO on all platforms (coverage would > continue to use FE instr as it does cur...

...rogram. Our first line > > of defense of course is the DWARF standard itself, but as we've seen, > > that is not a universally definitive reference. > > > > LLVM already emits DWARF slightly differently for different *targets*; > > primarily Darwin, in a few cases PS4. But in at least some cases, the > > target is just a (somewhat unreliable) proxy for which *debugger* the > > compiler expects to be consuming the DWARF. The most instructive case > > is the exact DWARF expression used to describe the location of a thread- > > local varia...

...e | was_red -----------------------------------------------------------+----------- sanitizer-x86_64-linux-bootstrap | 134:12:25 perf-x86_64-penryn-O3-polly-parallel-fast | 46:29:26 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast | 37:56:11 polly-amd64-linux | 34:53:03 sanitizer-x86_64-linux-fuzzer | 30:17:25 clang-x64-ninja-win7 | 25:37:00 llvm-clang-lld-x86_64-debian-fast...

...,3,2),c(0,1,1,0,0));colnames(p5)=c("x","y") p6=cbind(c(2,2,3,3,2),c(1,2,2,1,1));colnames(p6)=c("x","y") ps1=Polygons(list(Polygon(p1)), ID="ps1") ps2=Polygons(list(Polygon(p2)), ID="ps2") ps3=Polygons(list(Polygon(p3)), ID="ps3") ps4=Polygons(list(Polygon(p4)), ID="ps4") ps5=Polygons(list(Polygon(p5)), ID="ps5") ps6=Polygons(list(Polygon(p6)), ID="ps6") sps = SpatialPolygons(list(ps1,ps2,ps3, ps4, ps5, ps6)) spdf= SpatialPolygonsDataFrame(sps,data.frame(weight=c(0.1,0.1,0.3,0.4,0.45,0.6),row.names=...

...ote: > > > On Wed, May 25, 2016 at 12:12 PM, Sean Silva <chisophugis at gmail.com> > wrote: > >> >> >> On Mon, May 23, 2016 at 8:23 PM, Sean Silva <chisophugis at gmail.com> >> wrote: >> >>> Jake and I have been integrating IRPGO on PS4, and we've identified 3 >>> remaining work items. >>> >>> >>> - Driver changes >>> >>> We'd like to make IRPGO the default on PS4. We also think that it would >>> be beneficial to make IRPGO the default PGO on all platforms (cov...

...ls_address) Some are bigger things: - accelerator tables - pubnames/pubtypes Really these aren't so much _platform_ specific things as they are _debugger_ specific things. For example: - accelerator tables: default on for Darwin, but really on for LLDB. - pubnames/pubtypes: off for Darwin and PS4, but really on for GDB. We're co-opting platform as a proxy for the debugger. Sometimes they are closely tied, but in other cases maybe not so much. I think it is already the case that LLDB is used in more places than just Darwin? But the things that look like they ought to be LLDB-specific...

On Mon, May 23, 2016 at 8:23 PM, Sean Silva <chisophugis at gmail.com> wrote: > Jake and I have been integrating IRPGO on PS4, and we've identified 3 > remaining work items. > Sean, thanks for the write up. It matches very well with what we think as well. > > > - Driver changes > > We'd like to make IRPGO the default on PS4. We also think that it would be > beneficial to make IRPGO the de...

Hi, Recently one Windows build bot failed by my commit, because the obj file being generated is too big: C:\ps4-buildslave2\llvm-clang-x86_64-expensive-checks-win\llvm\tools\clang\unittests\AST\ASTImporterTest.cpp : fatal error C1128: number of sections exceeded object file format limit: compile with /bigobj Is there an LLVM policy to limit the maximum size of the generated obj files? If not then I suspect...