Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Thu, Mar 31, 2016 at 5:59 PM, Mathieu Malaterre wrote: > On Thu, Mar 31, 2016 at 2:44 PM, Mathieu Malaterre wrote: >> On Thu, Mar 31, 2016 at 1:08 PM, Jo Shields wrote: >>> >>> >>> On 31/03/16 11:49, Mathieu Malaterre wrote: While at it, I was wondering why a portion of the patch did not

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Thu, Mar 31, 2016 at 2:44 PM, Mathieu Malaterre wrote: > On Thu, Mar 31, 2016 at 1:08 PM, Jo Shields wrote: >> >> >> On 31/03/16 11:49, Mathieu Malaterre wrote: >>> While at it, I was wondering why a portion of the patch did not make >>> it into Debian: >>> >>> https://bugzilla.xamarin.com/sho

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Thu, Mar 31, 2016 at 1:08 PM, Jo Shields wrote: > > > On 31/03/16 11:49, Mathieu Malaterre wrote: >> While at it, I was wondering why a portion of the patch did not make >> it into Debian: >> >> https://bugzilla.xamarin.com/show_bug.cgi?id=28679#c9 >> >> + /* It is expected to be a function des

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 31/03/16 11:49, Mathieu Malaterre wrote: > While at it, I was wondering why a portion of the patch did not make > it into Debian: > > https://bugzilla.xamarin.com/show_bug.cgi?id=28679#c9 > > + /* It is expected to be a function descriptor on power pre-v2 ABI */ > + buf = mono_create_ftnptr

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

While at it, I was wondering why a portion of the patch did not make it into Debian: https://bugzilla.xamarin.com/show_bug.cgi?id=28679#c9 + /* It is expected to be a function descriptor on power pre-v2 ABI */ + buf = mono_create_ftnptr (mono_domain_get (), buf);

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Sep 09, 2015 at 03:13:56PM +0100, Jo Shields wrote: > porpora has the same ppc64 kernel as partch, libc 2.19-19 > > That's an interesting idea. Try building from > http://http.debian.net/debian/pool/main/m/mono/mono_4.0.4.1+dfsg-1.dsc > which bundles a matched monolite generated from its o

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 09/09/15 15:08, Lennart Sorensen wrote: > On Wed, Sep 09, 2015 at 08:27:44AM +0100, Jo Shields wrote: >> It's not the silicon - it failed on a G5 XServe as well >> >> It's not gcc - I did a successful build on gcc5. >> >> It's not the kernel version - it succeeded on a Mac Mini with >> 3.16.0-

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Sep 09, 2015 at 08:27:44AM +0100, Jo Shields wrote: > It's not the silicon - it failed on a G5 XServe as well > > It's not gcc - I did a successful build on gcc5. > > It's not the kernel version - it succeeded on a Mac Mini with > 3.16.0-4-powerpc... actually... You've been using a ppc64

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 08/09/15 16:40, Lennart Sorensen wrote: > On Tue, Sep 08, 2015 at 04:24:10PM +0100, Jo Shields wrote: >> 3.16.0-4-powerpc64 >> >> partch.debian.org, the porterbox where it fails: >> cpu: POWER7 (architected), altivec supported >> model: IBM,8231-E2B > > I am running on a 8231-

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Sep 08, 2015 at 04:24:10PM +0100, Jo Shields wrote: > 3.16.0-4-powerpc64 > > partch.debian.org, the porterbox where it fails: > cpu: POWER7 (architected), altivec supported > model: IBM,8231-E2B I am running on a 8231-E1C, so not very different. ... processor : 23 c

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 08/09/15 16:08, Lennart Sorensen wrote: > On Mon, Sep 07, 2015 at 03:42:03PM +0100, Jo Shields wrote: >> I can get things in under a "trivial" exception. One patch is in, the >> other is stuck in "please rewrite this" hell @ >> https://github.com/mono/referencesource/pull/16 - I'll try to get

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Mon, Sep 07, 2015 at 03:42:03PM +0100, Jo Shields wrote: > I can get things in under a "trivial" exception. One patch is in, the > other is stuck in "please rewrite this" hell @ > https://github.com/mono/referencesource/pull/16 - I'll try to get to it > when I have time, but I have a backlog of

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 07/09/15 15:42, Jo Shields wrote: > Any bright ideas from anyone else in the peanut gallery? It seems dumb > as hell to be to need to pull the package when it *does* work - just not > on the right computer for it to be considered "fine". > This is where we are, having tried with the known-fin

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 01/09/15 16:42, Lennart Sorensen wrote: > On Tue, Sep 01, 2015 at 09:48:54AM +0100, Jo Shields wrote: >> If you can sign the CLA at https://cla.xamarin.com/ I can take care of >> the patch process > Well I looked at it and it would seem I can not. > > I am employed by someone, but they have no

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Sep 01, 2015 at 09:48:54AM +0100, Jo Shields wrote: > If you can sign the CLA at https://cla.xamarin.com/ I can take care of > the patch process Well I looked at it and it would seem I can not. I am employed by someone, but they have nothing to do with me contributing patches to things in

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

It would be not so nice to lost support for products like the Pegasos II which is a 32bit G4 device. :( > Am 24.08.2015 um 23:49 schrieb Lennart Sorensen > : > > On Sun, Aug 16, 2015 at 08:59:19AM +0100, Jo Shields wrote: >> Dear PPC porter people, >> >> The major Mono version pending in expe

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 28/08/15 18:58, Lennart Sorensen wrote: > Assuming GH means github, then I have no idea how one would do that. > I only ever just pull things from github. If you can sign the CLA at https://cla.xamarin.com/ I can take care of the patch process > Certainly getting the fixes in would be great,

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Fri, Aug 28, 2015 at 01:58:56PM -0400, Lennart Sorensen wrote: > On Fri, Aug 28, 2015 at 08:58:22AM +0100, Jo Shields wrote: > > Okay. At this point, I've tried testing on a different box I was > > generously offered access to, and it works as well as you indicate - > > so my suspicion is there

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Fri, Aug 28, 2015 at 08:58:22AM +0100, Jo Shields wrote: > Okay. At this point, I've tried testing on a different box I was > generously offered access to, and it works as well as you indicate - > so my suspicion is there is Something Weird(tm) on partch.debian.org. That's good, I think. > I i

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/08/15 22:14, Lennart Sorensen wrote: > Patch I did, which worked this well on the first try, but I won't > say it is perfect for sure (and I suspect if it makes sense, then > ppc64 could add the instructions to their .md file too). > > diff

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 10:47:07PM +0100, Jo Shields wrote: > > > On 26/08/15 22:44, Lennart Sorensen wrote: > > > >I managed to get failure 1 and 2 above to go away by changing the test > >slightly: > > > >diff --git a/mcs/class/corlib/Test/System/DateTimeTest.cs > >b/mcs/class/corlib/Test/Sys

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 26/08/15 22:44, Lennart Sorensen wrote: I managed to get failure 1 and 2 above to go away by changing the test slightly: diff --git a/mcs/class/corlib/Test/System/DateTimeTest.cs b/mcs/class/corlib/Test/System/DateTimeTest.cs index 0e3076b..2db099c 100644 --- a/mcs/class/corlib/Test/Syste

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 05:14:55PM -0400, Lennart Sorensen wrote: > On Wed, Aug 26, 2015 at 09:05:30PM +0100, Jo Shields wrote: > > > > > > On 26/08/15 20:12, Lennart Sorensen wrote: > > >On Wed, Aug 26, 2015 at 07:01:31PM +0100, Jo Shields wrote: > > >> > > >>On 26/08/15 18:47, Lennart Sorensen

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 09:05:30PM +0100, Jo Shields wrote: > > > On 26/08/15 20:12, Lennart Sorensen wrote: > >On Wed, Aug 26, 2015 at 07:01:31PM +0100, Jo Shields wrote: > >> > >>On 26/08/15 18:47, Lennart Sorensen wrote: > >>>Opcode 'move_f_to_i4' missing from machine description file. > >>> >

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 26/08/15 20:12, Lennart Sorensen wrote: On Wed, Aug 26, 2015 at 07:01:31PM +0100, Jo Shields wrote: On 26/08/15 18:47, Lennart Sorensen wrote: Opcode 'move_f_to_i4' missing from machine description file. I agree with its assessment, there's no OP_MOVE_F_TO_I4 in mono/mini/mini-ppc.c and

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 07:01:31PM +0100, Jo Shields wrote: > > > On 26/08/15 18:47, Lennart Sorensen wrote: > >Opcode 'move_f_to_i4' missing from machine description file. > > > > I agree with its assessment, there's no OP_MOVE_F_TO_I4 in > mono/mini/mini-ppc.c and no move_f_to_i4 in mono/mini/

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 26/08/15 18:47, Lennart Sorensen wrote: Opcode 'move_f_to_i4' missing from machine description file. I agree with its assessment, there's no OP_MOVE_F_TO_I4 in mono/mini/mini-ppc.c and no move_f_to_i4 in mono/mini/cpu-ppc.md (maybe there should be? other arches have it)

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 01:47:09PM -0400, Lennart Sorensen wrote: > Well M=0 did no difference. > > I added -labels to the nunit-console.exe arguments which made it print > each test name before running it to the output file and that allowed me > to determine the hang was in: > > DefaultThreadCur

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 05:40:15PM +0100, Jo Shields wrote: > > > On 26/08/15 17:26, Lennart Sorensen wrote: > > > > And running the test suite as NOT root solved that. So now the only > > problem I see left in 'make mcs-do-tests' is getting stuck forever in > > one test: > > > > make[9]: Enteri

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 26/08/15 17:26, Lennart Sorensen wrote: > > And running the test suite as NOT root solved that. So now the only > problem I see left in 'make mcs-do-tests' is getting stuck forever in > one test: > > make[9]: Entering directory '/tmp/mono-new/mono-1/mcs/class/corlib' > ok=:; \ > PATH="/tmp/mo

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 05:28:28PM +0100, Jo Shields wrote: > > > On 26/08/15 17:16, Lennart Sorensen wrote: > > > > And a patch that fixes that (since the double's stored in the table are > > little endian, they have to be endian swapped before being returned as > > a double). > > > > diff --git

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 26/08/15 17:16, Lennart Sorensen wrote: > > And a patch that fixes that (since the double's stored in the table are > little endian, they have to be endian swapped before being returned as > a double). > > diff --git a/mscorlib/system/globalization/charunicodeinfo.cs > b/mscorlib/system/globa

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 12:16:14PM -0400, Lennart Sorensen wrote: > On Wed, Aug 26, 2015 at 10:45:24AM -0400, Lennart Sorensen wrote: > > On Tue, Aug 25, 2015 at 05:54:10PM -0400, Lennart Sorensen wrote: > > > On Tue, Aug 25, 2015 at 10:30:45PM +0100, Jo Shields wrote: > > > > On 25/08/15 22:29, Le

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Wed, Aug 26, 2015 at 10:45:24AM -0400, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 05:54:10PM -0400, Lennart Sorensen wrote: > > On Tue, Aug 25, 2015 at 10:30:45PM +0100, Jo Shields wrote: > > > On 25/08/15 22:29, Lennart Sorensen wrote: > > > > I had thought that could be it too. I certai

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 05:54:10PM -0400, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 10:30:45PM +0100, Jo Shields wrote: > > On 25/08/15 22:29, Lennart Sorensen wrote: > > > I had thought that could be it too. I certainly haven't seen that > > > particular problem so far. Are you simply runn

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 10:30:45PM +0100, Jo Shields wrote: > On 25/08/15 22:29, Lennart Sorensen wrote: > > I had thought that could be it too. I certainly haven't seen that > > particular problem so far. Are you simply running make or are you > > passing any arguments to configure or anything? I

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 25/08/15 22:29, Lennart Sorensen wrote: > I had thought that could be it too. I certainly haven't seen that > particular problem so far. Are you simply running make or are you > passing any arguments to configure or anything? I tried using a copy > of the debian dir from the mono package in ex

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 10:16:15PM +0100, Jo Shields wrote: > > > On 25/08/15 22:01, Lennart Sorensen wrote: > > On Tue, Aug 25, 2015 at 09:28:50PM +0100, Jo Shields wrote: > >> Okay, now I'm confused? The point of that branch was it was the > >> almost-working state, the compiler was one of the

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 25/08/15 22:01, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 09:28:50PM +0100, Jo Shields wrote: >> Okay, now I'm confused? The point of that branch was it was the >> almost-working state, the compiler was one of the things not working >> properly! Let me try building from the branch afre

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 09:28:50PM +0100, Jo Shields wrote: > Okay, now I'm confused? The point of that branch was it was the > almost-working state, the compiler was one of the things not working > properly! Let me try building from the branch afresh... Well if you want me to do a fresh pull agai

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 25/08/15 19:33, Lennart Sorensen wrote: > I am currently running make compiler-tests, which is currently "stuck" > after doing something and seems to be using no cpu but waiting 2 > seconds again and again for soem futex. Okay, now I'm confused? The point of that branch was it was the almost-

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 11:50:46AM -0400, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 11:46:41AM -0400, Lennart Sorensen wrote: > > On Tue, Aug 25, 2015 at 04:45:54PM +0100, Jo Shields wrote: > > > > > > > > > On 25/08/15 16:34, Lennart Sorensen wrote: > > > > On Tue, Aug 25, 2015 at 10:53:

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 11:46:41AM -0400, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 04:45:54PM +0100, Jo Shields wrote: > > > > > > On 25/08/15 16:34, Lennart Sorensen wrote: > > > On Tue, Aug 25, 2015 at 10:53:31AM -0400, Lennart Sorensen wrote: > > >> On Tue, Aug 25, 2015 at 10:09:58AM

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 25/08/15 16:34, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 10:53:31AM -0400, Lennart Sorensen wrote: >> On Tue, Aug 25, 2015 at 10:09:58AM -0400, Lennart Sorensen wrote: >>> OK, I was just trying what README.md said to do when using the get >>> monolite option. >>> >>> I also just notic

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 04:45:54PM +0100, Jo Shields wrote: > > > On 25/08/15 16:34, Lennart Sorensen wrote: > > On Tue, Aug 25, 2015 at 10:53:31AM -0400, Lennart Sorensen wrote: > >> On Tue, Aug 25, 2015 at 10:09:58AM -0400, Lennart Sorensen wrote: > >>> OK, I was just trying what README.md said

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 10:53:31AM -0400, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 10:09:58AM -0400, Lennart Sorensen wrote: > > OK, I was just trying what README.md said to do when using the get > > monolite option. > > > > I also just noticed I hadn't installed all the dependancies list

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 10:09:58AM -0400, Lennart Sorensen wrote: > OK, I was just trying what README.md said to do when using the get > monolite option. > > I also just noticed I hadn't installed all the dependancies listed on > http://www.mono-project.com/docs/compiling-mono/linux/ so I just did

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Tue, Aug 25, 2015 at 03:06:21PM +0100, Jo Shields wrote: > > > On 25/08/15 14:44, Lennart Sorensen wrote: > > > > I did that, and got a ton of other errors. > > > > The readme file said to use: > > > > make get-monolite-latest > > make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/basic.exe > >

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 25/08/15 14:44, Lennart Sorensen wrote: > > I did that, and got a ton of other errors. > > The readme file said to use: > > make get-monolite-latest > make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/basic.exe Don't touch EXTERNAL_MCS - if set, it needs to be the path to an executable compiler

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Mon, Aug 24, 2015 at 11:10:34PM +0100, Jo Shields wrote: > > > On 24/08/15 22:49, Lennart Sorensen wrote: > >On Sun, Aug 16, 2015 at 08:59:19AM +0100, Jo Shields wrote: > >>Dear PPC porter people, > >> > >>The major Mono version pending in experimental fixes GCC5 and fixes > >>reproducible bui

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 24/08/15 22:49, Lennart Sorensen wrote: On Sun, Aug 16, 2015 at 08:59:19AM +0100, Jo Shields wrote: Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I don't want to delay it. It doesn't build on Powe

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Sun, Aug 16, 2015 at 08:59:19AM +0100, Jo Shields wrote: > Dear PPC porter people, > > The major Mono version pending in experimental fixes GCC5 and fixes > reproducible builds and a dozen other bugs, so I don't want to delay it. > > It doesn't build on PowerPC any more, and nobody upstream is

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On 16/08/15 11:00, Mathieu Malaterre wrote: On Sun, Aug 16, 2015 at 9:59 AM, Jo Shields > wrote: Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I don't want

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

On Sun, Aug 16, 2015 at 9:59 AM, Jo Shields wrote: > Dear PPC porter people, > > The major Mono version pending in experimental fixes GCC5 and fixes > reproducible builds and a dozen other bugs, so I don't want to delay it. > > It doesn't build on PowerPC any more, and nobody upstream is working

Potential Mono removal from 32-bit big endian PowerPC in next upload

Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I don't want to delay it. It doesn't build on PowerPC any more, and nobody upstream is working on it. We recently introduced ppc64el, which is working, bu