From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cZITY-0004zi-J5 for qemu-devel@nongnu.org; Thu, 02 Feb 2017 09:35:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cZITU-00059D-2X for qemu-devel@nongnu.org; Thu, 02 Feb 2017 09:35:04 -0500 Received: from mail-pg0-x244.google.com ([2607:f8b0:400e:c05::244]:36608) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cZITT-000592-Sn for qemu-devel@nongnu.org; Thu, 02 Feb 2017 09:35:00 -0500 Received: by mail-pg0-x244.google.com with SMTP id 75so1987405pgf.3 for ; Thu, 02 Feb 2017 06:34:59 -0800 (PST) Date: Thu, 2 Feb 2017 23:34:55 +0900 From: Stafford Horne Message-ID: <20170202143455.GB32144@lianli.shorne-pla.net> References: <20170120163918.GD7836@lianli.shorne-pla.net> <20170124102625.GF7836@lianli.shorne-pla.net> <01f7a18d-f4f5-18f3-0932-b32c06ad0b0c@twiddle.net> <20170125123430.GG7836@lianli.shorne-pla.net> <39f927aa-26fe-0e43-7c6b-efe1b70bc5fa@twiddle.net> <20170126131229.GB16014@lianli.shorne-pla.net> <20170201100423.GE21641@lianli.shorne-pla.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: Jia Liu , qemu-devel@nongnu.org, openrisc@lists.librecores.org On Wed, Feb 01, 2017 at 10:15:54AM -0800, Richard Henderson wrote: > On 02/01/2017 02:04 AM, Stafford Horne wrote: > > On Thu, Jan 26, 2017 at 09:26:55AM -0800, Richard Henderson wrote: > >> On 01/26/2017 05:12 AM, Stafford Horne wrote: > >>> I just sent you a mail with a link to my kernel for download. > >>> > >>> One thing I noticed is you passed '-append console=ttyS0' I think that > >>> does nothing on openrisc since as far as I know openrisc only gets boot > >>> params from the device tree file. I tried with and without it and got no > >>> differences. > >> > >> That was just reflex, wondering where the output went. > >> > >>> Another thing, I am using a 'late' version of gcc built with musl cross [1] > >>> , I dont think it would make a difference, but maybe? > >> > >> I think that's likely the difference. I can indeed boot your kernel. > > > > Hi Richard, > > > > For kernel builds I have created toolchain binaries here: > > > > http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/ > > > > These should work. > > > > If all is ok with the qemu patch I sent what is the next step to get them > > incorporated. Do you need any help from me? > > > > ... Actually I just checked your branch on github, it looks like you are > > doing a few updates. Let me know if you want me to review anything. > > Yes, I've been attempting to revive a patch set from 2013 that cleans up the > implementation, fixing a few other bugs in the process. > > However, testing it properly has been tricky. It appears as if I'm debugging > qemu and gcc simultaneously, while your gdb branch doesn't want to compile for > me. So I've been limited to instruction traces from qemu, which is slow going. What issue are you having compiling gdb? I compile gdb with these flags. ../binutils-gdb/configure --target=or1k-musl-linux \ --prefix=$PREFIX \ --disable-itcl \ --disable-tk \ --disable-tcl \ --disable-winsup \ --disable-gdbtk \ --disable-libgui \ --disable-rda \ --disable-sid \ --with-sysroot \ --disable-newlib \ --disable-libgloss \ --disable-gas \ --disable-ld \ --disable-binutils \ --disable-gprof \ --with-system-zlib Also, I uploaded my binaries just in case: http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/ My host gcc is "6.3.1 20161221", I used musl-cross and my gdb branch https://github.com/openrisc/musl-cross.git or1k git@github.com:stffrdhrn/binutils-gdb.git or1k-upstream > If you'd like to do your own testing on my tgt-or1k-2 branch, that would be > appreciated. I will have a look tomorrow if I can. -Stafford From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stafford Horne Date: Thu, 2 Feb 2017 23:34:55 +0900 Subject: [OpenRISC] [Qemu-devel] [PATCH] target-openrisc: Fix exception handling status registers In-Reply-To: References: <20170120163918.GD7836@lianli.shorne-pla.net> <20170124102625.GF7836@lianli.shorne-pla.net> <01f7a18d-f4f5-18f3-0932-b32c06ad0b0c@twiddle.net> <20170125123430.GG7836@lianli.shorne-pla.net> <39f927aa-26fe-0e43-7c6b-efe1b70bc5fa@twiddle.net> <20170126131229.GB16014@lianli.shorne-pla.net> <20170201100423.GE21641@lianli.shorne-pla.net> Message-ID: <20170202143455.GB32144@lianli.shorne-pla.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: openrisc@lists.librecores.org On Wed, Feb 01, 2017 at 10:15:54AM -0800, Richard Henderson wrote: > On 02/01/2017 02:04 AM, Stafford Horne wrote: > > On Thu, Jan 26, 2017 at 09:26:55AM -0800, Richard Henderson wrote: > >> On 01/26/2017 05:12 AM, Stafford Horne wrote: > >>> I just sent you a mail with a link to my kernel for download. > >>> > >>> One thing I noticed is you passed '-append console=ttyS0' I think that > >>> does nothing on openrisc since as far as I know openrisc only gets boot > >>> params from the device tree file. I tried with and without it and got no > >>> differences. > >> > >> That was just reflex, wondering where the output went. > >> > >>> Another thing, I am using a 'late' version of gcc built with musl cross [1] > >>> , I dont think it would make a difference, but maybe? > >> > >> I think that's likely the difference. I can indeed boot your kernel. > > > > Hi Richard, > > > > For kernel builds I have created toolchain binaries here: > > > > http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/ > > > > These should work. > > > > If all is ok with the qemu patch I sent what is the next step to get them > > incorporated. Do you need any help from me? > > > > ... Actually I just checked your branch on github, it looks like you are > > doing a few updates. Let me know if you want me to review anything. > > Yes, I've been attempting to revive a patch set from 2013 that cleans up the > implementation, fixing a few other bugs in the process. > > However, testing it properly has been tricky. It appears as if I'm debugging > qemu and gcc simultaneously, while your gdb branch doesn't want to compile for > me. So I've been limited to instruction traces from qemu, which is slow going. What issue are you having compiling gdb? I compile gdb with these flags. ../binutils-gdb/configure --target=or1k-musl-linux \ --prefix=$PREFIX \ --disable-itcl \ --disable-tk \ --disable-tcl \ --disable-winsup \ --disable-gdbtk \ --disable-libgui \ --disable-rda \ --disable-sid \ --with-sysroot \ --disable-newlib \ --disable-libgloss \ --disable-gas \ --disable-ld \ --disable-binutils \ --disable-gprof \ --with-system-zlib Also, I uploaded my binaries just in case: http://shorne.noip.me/crosstool/files/bin/x86_64/5.4.0/ My host gcc is "6.3.1 20161221", I used musl-cross and my gdb branch https://github.com/openrisc/musl-cross.git or1k git at github.com:stffrdhrn/binutils-gdb.git or1k-upstream > If you'd like to do your own testing on my tgt-or1k-2 branch, that would be > appreciated. I will have a look tomorrow if I can. -Stafford