Hello Maintainers:
It is finished with qemu today, it spends 13 days, the result is below,
please help check.
With qemu:
=== gcc Summary ===
# of expected passes83439
# of unexpected failures175
# of unexpected successes 1
# of
After try the latest gcc again (execuse me, during these days, I have to
do another things), all things OK, the kernel can be started by QEMU,
all related issues are fixed by other members.
I shall start the make check with qemu again (it is about 12-13 days).
I guess, this thread is almost spam
On 12/20/14 02:09, Chen Gang wrote:
By the way, if this thread really has negative effect with other members,
please warn me, I should not notify it to mailing list again, and try my
best to finish it within myself.
I appreciate your enthusiasm and perseverance in pursuing this bug.
If the
On 12/21/2014 12:31 AM, Michael Eager wrote:
On 12/20/14 02:09, Chen Gang wrote:
By the way, if this thread really has negative effect with other members,
please warn me, I should not notify it to mailing list again, and try my
best to finish it within myself.
I appreciate your enthusiasm
Hello Maintainers:
After analysing, it is not kernel's issue, it is gcc issue, after let
kernel related variable bypass this gcc issue, the kernel can start up
successfully.
The issue is after declaration, the __attribute_((__section__ ...))
will be ignored. After simplification, the related
Oh, sorry, after ran more than 10 days, the qemu crashed :-(
After checked the output log, and compare with the original log, we know
we have finished more than 90% test, and it is OK (no any new issues).
I guess the reason is I started too many other things on this machine.
Next, I shall try
At present, I use simplified sshd, ssh and scp (dropbear open source
program) to communicate with microblaze qemu successfully, and let gcc
'make check' have real effect.
It is just testing, at least after almost 10 hours, the log output is
OK. For each ssh login, it will wast 10 - 20 seconds,
At present, I use telnet (without password), login to microblaze qemu
successfully! :-)
- I compile busy box with the glibc in orginal 'ramfs', so get telnetd:
use new busybox replace the old one, and add symbol link 'telnetd' to
busybox in /bin.
- configure qemu with network support
On 10/29/14 23:58, Chen Gang wrote:
On 10/27/14 9:42, Chen Gang wrote:
On 10/27/14 2:22, Michael Eager wrote:
Microblaze-sim provides basic instruction set architecture and memory
simulation.
There is no operating system support. (It's also quite old. I'm not sure
which version of the MB
On 10/27/14 9:42, Chen Gang wrote:
On 10/27/14 2:22, Michael Eager wrote:
Microblaze-sim provides basic instruction set architecture and memory
simulation.
There is no operating system support. (It's also quite old. I'm not sure
which version of the MB architecture it models, but it is
On 10/22/2014 09:34 AM, Chen Gang wrote:
Yes, if you want to test on a target, you will need a target. You can
either have a simulator (see binutils and sim/* for an example of how to
write one) or target hardware in some form.
After tried 'sim', I found the root cause is microblaze sim
On 10/26/14 03:36, Chen Gang wrote:
On 10/22/2014 09:34 AM, Chen Gang wrote:
Yes, if you want to test on a target, you will need a target. You can either
have a simulator (see binutils and sim/* for an example of how to write one) or
target hardware in some form.
After tried 'sim', I
On 10/27/14 2:22, Michael Eager wrote:
On 10/26/14 03:36, Chen Gang wrote:
On 10/22/2014 09:34 AM, Chen Gang wrote:
Yes, if you want to test on a target, you will need a target. You can
either have a simulator (see binutils and sim/* for an example of how to
write one) or target
On 09/25/2014 08:12 AM, Chen Gang wrote:
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on
Qemu, and try to make patches for it).
Excuse me, after tried upstream qemu, it cann't run microblaze correctly,
even for Xilinx qemu branch, I cann't run correctly either. I
On 10/21/14 22:55, Chen Gang wrote:
On 09/25/2014 08:12 AM, Chen Gang wrote:
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on
Qemu, and try to make patches for it).
Excuse me, after tried upstream qemu, it cann't run microblaze correctly,
even for Xilinx qemu
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I guess, our
testsuite under Darwin x86_64 is OK.
If no any additional reply within a week, I shall continue to try to
analyze the libjava Throw_2 issue.
Throw_2 is a test specially contrived to
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I guess, our
testsuite under Darwin x86_64 is OK.
If no any additional reply within a week, I shall continue to try to
analyze the libjava Throw_2 issue.
On 10/06/2014 02:53 PM, Chen Gang wrote:
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I guess, our
testsuite under Darwin x86_64 is OK.
If no any additional reply within a week, I shall continue to try to
On 10/6/14 21:54, Andrew Haley wrote:
On 10/06/2014 02:53 PM, Chen Gang wrote:
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I guess, our
testsuite under Darwin x86_64 is OK.
If no any additional reply
On 10/06/2014 03:27 PM, Chen Gang wrote:
On 10/6/14 21:54, Andrew Haley wrote:
On 10/06/2014 02:53 PM, Chen Gang wrote:
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I guess, our
testsuite under Darwin x86_64
On 10/6/14 22:28, Andrew Haley wrote:
On 10/06/2014 03:27 PM, Chen Gang wrote:
On 10/6/14 21:54, Andrew Haley wrote:
On 10/06/2014 02:53 PM, Chen Gang wrote:
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal configure, get almost the same result, I
On 10/06/2014 04:00 PM, Chen Gang wrote:
On 10/6/14 22:28, Andrew Haley wrote:
On 10/06/2014 03:27 PM, Chen Gang wrote:
On 10/6/14 21:54, Andrew Haley wrote:
On 10/06/2014 02:53 PM, Chen Gang wrote:
On 10/6/14 16:37, Andrew Haley wrote:
On 06/10/14 05:08, Chen Gang wrote:
After try normal
On 10/6/14 22:59, Andrew Haley wrote:
On 10/06/2014 04:00 PM, Chen Gang wrote:
On 10/6/14 22:28, Andrew Haley wrote:
[...]
The testsuite isn't breaking: it's telling you something useful.
Sorry it is breaked, at present, I temporarily skipped it and then can
let make check finish, the
On Oct 6, 2014, at 8:36 AM, Chen Gang gang.chen.5...@gmail.com wrote:
For me, make -k check is suitable for one sub-system (e.g. for cross
building, and mainly focus on gcc), but not for global check (full
non-cross building check):
In our world, there is no sub-system, so, talk of such is
On 10/7/14 1:29, Mike Stump wrote:
On Oct 6, 2014, at 8:36 AM, Chen Gang gang.chen.5...@gmail.com wrote:
For me, make -k check is suitable for one sub-system (e.g. for cross
building, and mainly focus on gcc), but not for global check (full
non-cross building check):
In our world, there is
On 10/7/14 7:18, Chen Gang wrote:
On 10/7/14 1:29, Mike Stump wrote:
On Oct 6, 2014, at 8:36 AM, Chen Gang gang.chen.5...@gmail.com wrote:
For me, make -k check is suitable for one sub-system (e.g. for cross
building, and mainly focus on gcc), but not for global check (full
non-cross building
On 10/5/14 11:32, Chen Gang wrote:
On 10/5/14 11:15, Chen Gang wrote:
On 9/25/14 8:12, Chen Gang wrote:
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on
Qemu, and try to make patches for it).
And, I also need finish the testsuite under Darwin x86_64, next month for
On 9/25/14 8:12, Chen Gang wrote:
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on
Qemu, and try to make patches for it).
And, I also need finish the testsuite under Darwin x86_64, next month for gcc.
I finish tried testsuit under Darwin x86_64, originally, I
On 10/5/14 11:15, Chen Gang wrote:
On 9/25/14 8:12, Chen Gang wrote:
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on
Qemu, and try to make patches for it).
And, I also need finish the testsuite under Darwin x86_64, next month for
gcc.
I finish tried testsuit
Hello Michael:
Firstly, thank you very much for always providing your aid to me for
microblaze.
At present, after try testsuite, the result is much better than my
original trying, please help check the result: is it enough for our
microblaze testsuite (can we say it pass checking)?
Current
On 09/24/14 07:31, Chen Gang wrote:
Hello Michael:
Firstly, thank you very much for always providing your aid to me for
microblaze.
At present, after try testsuite, the result is much better than my
original trying, please help check the result: is it enough for our
microblaze testsuite (can
On Sep 24, 2014, at 8:28 AM, Michael Eager ea...@eagerm.com wrote:
After check the current result log, I find many remote target test
related sentences, do we have to process it?
e.g. Download to microblaze-xilinx-gdb failed, couldn't execute rcp: no
such file or directory.
The test
On 09/24/2014 11:28 PM, Michael Eager wrote:
On 09/24/14 07:31, Chen Gang wrote:
Hello Michael:
Firstly, thank you very much for always providing your aid to me for
microblaze.
At present, after try testsuite, the result is much better than my
original trying, please help check the result:
On 09/24/2014 11:37 PM, Mike Stump wrote:
On Sep 24, 2014, at 8:28 AM, Michael Eager ea...@eagerm.com wrote:
After check the current result log, I find many remote target test
related sentences, do we have to process it?
e.g. Download to microblaze-xilinx-gdb failed, couldn't execute rcp:
On Sep 24, 2014, at 9:23 AM, Chen Gang gang.chen.5...@gmail.com wrote:
For one simple solving way under fedora: yum install rsh, and I will
get another issue:
Download to microblaze-xilinx-gdb failed, microblaze-xilinx-gdb: Unknown
host
So I guess the root cause is: I only use
On 09/24/14 09:23, Chen Gang wrote:
On 09/24/2014 11:37 PM, Mike Stump wrote:
On Sep 24, 2014, at 8:28 AM, Michael Eager ea...@eagerm.com wrote:
After check the current result log, I find many remote target test
related sentences, do we have to process it?
e.g. Download to
OK, thanks, next month, I shall try Qemu for microblaze (I also focus on Qemu,
and try to make patches for it).
And, I also need finish the testsuite under Darwin x86_64, next month for gcc.
Hope I can succeed.
Thanks
Send from Lenovo A788t.
Mike Stump mikest...@comcast.net wrote:
On Sep
Thank you for your information, I shall notice about it when trying Qemu
microblaze.
Thanks
Send from Lenovo A788t.
Michael Eager ea...@eagerm.com wrote:
On 09/24/14 09:23, Chen Gang wrote:
On 09/24/2014 11:37 PM, Mike Stump wrote:
On Sep 24, 2014, at 8:28 AM, Michael Eager ea...@eagerm.com
On 09/21/14 21:10, Chen Gang wrote:
On 9/22/14 2:09, Michael Eager wrote:
Generally, you should use gcc to link programs, not ld. gcc is
a driver which will select the appropriate libraries and support routines
(such as crt0.o, which contains _start) and pass them to the linker.
OK,
On 09/21/14 20:55, Chen Gang wrote:
On 9/22/14 2:03, Michael Eager wrote:
On 09/20/14 23:24, Chen Gang wrote:
And it seems, we also need 'LinkScr.ld' for ldscript, could you share it
to me, thanks.
set_board_info ldscript -T/home/eager/Xilinx/dg/microblaze_0/LinkScr.ld
Hi Chen --
The
On 09/22/2014 10:45 PM, Michael Eager wrote:
On 09/21/14 21:10, Chen Gang wrote:
On 9/22/14 2:09, Michael Eager wrote:
Generally, you should use gcc to link programs, not ld. gcc is
a driver which will select the appropriate libraries and support routines
(such as crt0.o, which contains
On 09/22/2014 10:46 PM, Michael Eager wrote:
On 09/21/14 20:55, Chen Gang wrote:
On 9/22/14 2:03, Michael Eager wrote:
On 09/20/14 23:24, Chen Gang wrote:
And it seems, we also need 'LinkScr.ld' for ldscript, could you share it
to me, thanks.
set_board_info ldscript
After check the details, I guess, we need:
- Cross compile and install glibc with raw microblaze cross-compiler,
- Then compile new microblaze cross compiler with glibc.
- Then make check the new microblaze cross compiler with glibc.
And it seems, we also need 'LinkScr.ld' for ldscript,
On 09/21/2014 02:24 PM, Chen Gang wrote:
After check the details, I guess, we need:
- Cross compile and install glibc with raw microblaze cross-compiler,
After fix a compiling break bug for microblaze glibc, I succeed building
microblaze glibc with microblaze raw cross compiler, with
On 09/20/14 23:24, Chen Gang wrote:
And it seems, we also need 'LinkScr.ld' for ldscript, could you share it
to me, thanks.
set_board_info ldscript -T/home/eager/Xilinx/dg/microblaze_0/LinkScr.ld
Hi Chen --
The DejaGNU configuration I provided is for a bare-metal environment.
If you are
On 09/21/14 03:46, Chen Gang wrote:
Excuse me, I want to consult one thing: I installed raw microblaze cross
compiler, binutils and glibc into one directory (/upstream/release), and
try to build a Hello world C program for microblaze under x86_64 host.
I guess it is OK, but I am not quite sure
On 9/22/14 2:03, Michael Eager wrote:
On 09/20/14 23:24, Chen Gang wrote:
And it seems, we also need 'LinkScr.ld' for ldscript, could you share it
to me, thanks.
set_board_info ldscript -T/home/eager/Xilinx/dg/microblaze_0/LinkScr.ld
Hi Chen --
The DejaGNU configuration I provided
On 9/22/14 2:09, Michael Eager wrote:
On 09/21/14 03:46, Chen Gang wrote:
Excuse me, I want to consult one thing: I installed raw microblaze cross
compiler, binutils and glibc into one directory (/upstream/release), and
try to build a Hello world C program for microblaze under x86_64 host.
I
On 09/16/2014 08:33 PM, Michael Eager wrote:
On 09/15/14 15:53, Chen Gang wrote:
On 09/15/2014 11:30 PM, Michael Eager wrote:
Configuring DejaGNU for cross-target testing requires creating a
configuration
file describing the target board.
OK, thank you very much. And could you share
On 09/20/14 08:52, Chen Gang wrote:
Thank you very much for your attachments, it is very useful to me!
I tried testsuite for microblaze cross target on x86_64 host, it says
OK (echo $? == 0), but I am not quite sure about it (I still doubt
that my configuration is incorrect), please help
Thank you very much for your quickly response, I shall continue try.
Thanks.
On 09/21/2014 12:31 AM, Michael Eager wrote:
On 09/20/14 08:52, Chen Gang wrote:
Thank you very much for your attachments, it is very useful to me!
I tried testsuite for microblaze cross target on x86_64 host, it
On 09/15/14 15:53, Chen Gang wrote:
On 09/15/2014 11:30 PM, Michael Eager wrote:
Configuring DejaGNU for cross-target testing requires creating a configuration
file describing the target board.
OK, thank you very much. And could you share your configuration file,
which I can reference to?
On 09/14/14 21:19, Chen Gang wrote:
On 9/15/14 11:03, Michael Eager wrote:
On 09/14/14 00:51, Chen Gang wrote:
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite familiar the testsuite for
microblaze, could
On 09/15/2014 11:30 PM, Michael Eager wrote:
On 09/14/14 21:19, Chen Gang wrote:
On 9/15/14 11:03, Michael Eager wrote:
On 09/14/14 00:51, Chen Gang wrote:
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite familiar the testsuite for
microblaze, could you provide any related information for it?
Thanks.
On 09/08/2014 11:28 PM, Chen Gang wrote:
On 09/08/2014 10:24
On 09/14/14 00:51, Chen Gang wrote:
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite familiar the testsuite for
microblaze, could you provide any related information for it?
Hi Chen --
This is the gcc
On 9/15/14 11:03, Michael Eager wrote:
On 09/14/14 00:51, Chen Gang wrote:
Hello maintainers:
I also find some warnings during compiling microblaze, I also shall try
to fix them, but excuse me, I am not quite familiar the testsuite for
microblaze, could you provide any related information
On 09/08/2014 10:24 AM, Chen Gang wrote:
On 09/07/2014 11:17 PM, Chen Gang wrote:
On 8/13/14 23:10, Michael Eager wrote:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has done.
On 8/13/14 23:10, Michael Eager wrote:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has done.
The related warning:
../../gcc/gcc/config/microblaze/microblaze.md:2172:
On 09/07/2014 11:17 PM, Chen Gang wrote:
On 8/13/14 23:10, Michael Eager wrote:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has done.
The related warning:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has done.
The related warning:
../../gcc/gcc/config/microblaze/microblaze.md:2172: warning: operand 1
missing mode?
Firstly, thank you very much for spending your time resource on the
related 2 patches.
On 8/13/14 23:10, Michael Eager wrote:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has
On 08/13/14 18:35, Chen Gang wrote:
Firstly, thank you very much for spending your time resource on the
related 2 patches.
You're welcome.
On 8/13/14 23:10, Michael Eager wrote:
On 07/06/14 03:26, Chen Gang wrote:
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
On 8/14/14 10:14, Michael Eager wrote:
OK, thanks, and I shall analyze it, but excuse me, I have to do other
things this week, so hope I can finish it within next week (2014-08-24).
If this time point is too long to bare, please let me know.
Take your time and let me know when you have this
* microblaze/mocroblaze.md (call_value_intern): Use 'SI' instead of
'VOID' for operand 1, just like 'call_internal1' has done.
The related warning:
../../gcc/gcc/config/microblaze/microblaze.md:2172: warning: operand 1
missing mode?
Signed-off-by: Chen Gang gang.chen.5...@gmail.com
---
65 matches
Mail list logo
