> mips : > * need an explicit LLV_HOST_CPU to configure, which one ?
'(unknown)' is fine for the LLC host CPU. The main problem is the 'configure: error: unknown/unsupported host mips-unknown-linux-gnu'. This is caused by the lack of a 'mips*)' in the 'case $host_cpu in' on line 817 of configure.ac. It looks like the release_0_10 branch was created before I submitted Mips support. You need 37e3799 but even with that, big-endian Mips currently triggers an optimisation bug in LLVM which causes most tests to fail. I doubt this bug is going to be fixed in time. > mipsel : > * need an explicit LLV_HOST_CPU to configure, which one ? This is the same problem, but I haven't submitted mipsel support yet. In my working copy, little endian mips passes most tests but currently fails the shuffle tests and a couple others. I was planning on fixing the shuffle tests before I submitted little endian support but I can submit what I have tomorrow if you prefer. > -----Original Message----- > From: Vincent Danjean [mailto:[email protected]] > Sent: 09 October 2014 15:45 > To: Portable Computing Language development discussion > Subject: [pocl-devel] pocl in Debian : help needed > > Hi, > > As some of you know, pocl has just been accepted in Debian unstable. > We have 20 days for it to pass into testing so that it will be in the next > Debian stable. As there are 10 days delays between an upload and > a migration to testing (if no RC bugs), it means that the last upload > must be done in 10 days maximum... > > 1) Debian bugs > Would you agree that I subscribe the ML itself (ie > [email protected] ) to the BTS so that all Debian bug reports > will be sent to the ML ? > Of course, if any bugs are only related to the packaging, I will handle > them. But I suspect that most bugs will be for upstream and I would > probably be more efficient that the ML itself receive directly the mail. > 2) the BTS also offer the possibility to receive mail about build for > each Debian architecture. Would it be interested that the ML is also > subscribed to these mails ? > 3) pocl provides and install utlist.h. It is already packaged in Debian > in uthash-dev (see #764571) > I will remove utlist.h from the libpoclu-dev package. I was considering > adding a dependency but I fail to see why utlist.h is needed. > If utlist.h is needed by external applications but not by libpoclu itself, > I will not add the dependency. > 4) #764561 and #764563 show that there is problem on most > architectures. > https://buildd.debian.org/status/logs.php?pkg=pocl&ver=0.10-3&suite=sid > give an overview (clic on "Maybe-Failed" to have the build log). > amd64 (build locally) : > * I will force LLC_HOST_CPU=x86-64 > armel : > * need an explicit LLV_HOST_CPU to configure, which one ? > armhf : > * need an explicit LLV_HOST_CPU to configure, cortex-a7 ? > i386 : > * need an explicit LLV_HOST_CPU. It can be either i486 (to target > all supported hardware by Debian) or a x86_64 processor running > in 32bits mode (probably uses cases of pocl on this architecture). > In the later case, what would be the correct LLV_HOST_CPU ? > * the test suite fails for tests 8, 13 and 14. Any idea ? > mips : > * need an explicit LLV_HOST_CPU to configure, which one ? > mipsel : > * need an explicit LLV_HOST_CPU to configure, which one ? > powerpc : > * need an explicit LLV_HOST_CPU, which one ? > * lots of failed tests ("84 failed (4 expected failures).") > ppc64el : > * need an explicit LLV_HOST_CPU, which one ? > * errors on compilation (bug in compiler ?) > s390x : > * need an explicit LLV_HOST_CPU to configure, which one ? > > I will do an upload this evening, at least to close #764571. > I will put LLV_HOST_CPU for amd64, armhf and any other you > suggest me. And I will see later for the reminding architectures. > > Regards, > Vincent > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktr > k > _______________________________________________ > pocl-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/pocl-devel ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
