Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Mon, 18 Aug 2014, Oleg Endo wrote: On Mon, 2014-08-18 at 16:57 -0400, Hans-Peter Nilsson wrote: On Mon, 18 Aug 2014, Oleg Endo wrote: On Sun, 2014-08-17 at 16:56 -0400, Hans-Peter Nilsson wrote: On Fri, 15 Aug 2014, Oleg Endo wrote: How about the attached .html as a replacement for the current one? I removed the requirement of setting up a combined tree, as I believe it makes things much more easy. At least it's been working for me that way. Is this helpful / OK to commit? Maybe a patch is better in this case, instead of the whole .html. hm no likey, this is simply changing too much and making it SH-specific. Also, /usr/local is the default. I thought the it would work for other targets by replacing sh-elf with $TARGET. However, I can't test all of those. Maybe maintainers/users of other targets can comment on the applicability beyond SH. I'm afraid that's all I can do for now. I'll pick this up. After all, I'm supposedly the maintainer of that page... thanks. BTW, I've just noticed that I've duplicated the 'Passing options and running multiple testsuites' section mentioned on https://gcc.gnu.org/install/test.html . Maybe the sim-test page could be simply integrated into the test.html page in a stripped down form. There's certainly an unexpected disconnect but I think a link would be better than inlining. Most parts of my description have actually nothing to do with sim-testing, but are just one way of setting up a newlib based cross toolchain. Maybe that can be put as a cross toolchain example somewhere else on the wwwdocs, like https://gcc.gnu.org/install/build.html Sounds like a good idea. BTW, to check out the web pages to generate patches, see http://gcc.gnu.org/about.html#cvs. brgds, H-P
Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Tue, 2014-08-19 at 07:02 -0400, Hans-Peter Nilsson wrote: On Mon, 18 Aug 2014, Oleg Endo wrote: On Mon, 2014-08-18 at 16:57 -0400, Hans-Peter Nilsson wrote: On Mon, 18 Aug 2014, Oleg Endo wrote: On Sun, 2014-08-17 at 16:56 -0400, Hans-Peter Nilsson wrote: On Fri, 15 Aug 2014, Oleg Endo wrote: How about the attached .html as a replacement for the current one? I removed the requirement of setting up a combined tree, as I believe it makes things much more easy. At least it's been working for me that way. Is this helpful / OK to commit? Maybe a patch is better in this case, instead of the whole .html. hm no likey, this is simply changing too much and making it SH-specific. Also, /usr/local is the default. I thought the it would work for other targets by replacing sh-elf with $TARGET. However, I can't test all of those. Maybe maintainers/users of other targets can comment on the applicability beyond SH. I'm afraid that's all I can do for now. I'll pick this up. After all, I'm supposedly the maintainer of that page... thanks. BTW, I've just noticed that I've duplicated the 'Passing options and running multiple testsuites' section mentioned on https://gcc.gnu.org/install/test.html . Maybe the sim-test page could be simply integrated into the test.html page in a stripped down form. There's certainly an unexpected disconnect but I think a link would be better than inlining. Most parts of my description have actually nothing to do with sim-testing, but are just one way of setting up a newlib based cross toolchain. Maybe that can be put as a cross toolchain example somewhere else on the wwwdocs, like https://gcc.gnu.org/install/build.html Sounds like a good idea. BTW, to check out the web pages to generate patches, see http://gcc.gnu.org/about.html#cvs. I know. It's been in place here for a while. See also my previous wwwdoc commits. I don't know how I got the funny idea to send the .html instead of the patch before ... Cheers, Oleg
Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Sun, 2014-08-17 at 16:56 -0400, Hans-Peter Nilsson wrote: On Fri, 15 Aug 2014, Oleg Endo wrote: How about the attached .html as a replacement for the current one? I removed the requirement of setting up a combined tree, as I believe it makes things much more easy. At least it's been working for me that way. Is this helpful / OK to commit? Maybe a patch is better in this case, instead of the whole .html. hm no likey, this is simply changing too much and making it SH-specific. Also, /usr/local is the default. I thought the it would work for other targets by replacing sh-elf with $TARGET. However, I can't test all of those. Maybe maintainers/users of other targets can comment on the applicability beyond SH. I'm afraid that's all I can do for now. Cheers, Oleg
Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Mon, 18 Aug 2014, Oleg Endo wrote: On Sun, 2014-08-17 at 16:56 -0400, Hans-Peter Nilsson wrote: On Fri, 15 Aug 2014, Oleg Endo wrote: How about the attached .html as a replacement for the current one? I removed the requirement of setting up a combined tree, as I believe it makes things much more easy. At least it's been working for me that way. Is this helpful / OK to commit? Maybe a patch is better in this case, instead of the whole .html. hm no likey, this is simply changing too much and making it SH-specific. Also, /usr/local is the default. I thought the it would work for other targets by replacing sh-elf with $TARGET. However, I can't test all of those. Maybe maintainers/users of other targets can comment on the applicability beyond SH. I'm afraid that's all I can do for now. I'll pick this up. After all, I'm supposedly the maintainer of that page... thanks. brgds, H-P
Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Fri, 15 Aug 2014, Oleg Endo wrote: How about the attached .html as a replacement for the current one? I removed the requirement of setting up a combined tree, as I believe it makes things much more easy. At least it's been working for me that way. Is this helpful / OK to commit? Maybe a patch is better in this case, instead of the whole .html. hm no likey, this is simply changing too much and making it SH-specific. Also, /usr/local is the default. brgds, H-P
Re: [wwwdocs] Re: gcc.gnu.org/simtest-howto.html (was: Question for ARM person re asm_fprintf)(
On Fri, 2014-08-15 at 22:58 +0200, Oleg Endo wrote:
On Mon, 2014-08-04 at 08:19 +0200, Oleg Endo wrote:
On Aug 4, 2014, at 6:00 AM, Gerald Pfeifer ger...@pfeifer.com wrote:
On Wed, 23 Jul 2014, Hans-Peter Nilsson wrote:
The page https://gcc.gnu.org/simtest-howto.html is
unfortunately out of date (e.g. binutils+sim now lives in the
same git repo) but it gives you the idea.
Sooo, any volunteer to update this page? Doesn't have to be
perfect, even incremental improvements help.
Or is it bad enough that we should rather remove this unless/
until someone steps up?
Since I'm basically doing all the testing in sh-sim, I could try to update
that page.
How about the attached .html as a replacement for the current one?
I removed the requirement of setting up a combined tree, as I believe
it makes things much more easy. At least it's been working for me
that way. Is this helpful / OK to commit?
Maybe a patch is better in this case, instead of the whole .html.
Cheers,
Oleg
? simtest_howto.patch
Index: simtest-howto.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/simtest-howto.html,v
retrieving revision 1.29
diff -u -r1.29 simtest-howto.html
--- simtest-howto.html 27 Jun 2014 11:48:46 - 1.29
+++ simtest-howto.html 15 Aug 2014 21:00:31 -
@@ -1,9 +1,41 @@
-html
- head
-titleHow to test GCC on a simulator/title
- /head
+?xml version=1.0 encoding=utf-8?
+ !DOCTYPE html
+PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
+http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en lang=en
+
+ head
+
+meta http-equiv=Content-Type content=text/html; charset=utf-8 /
+link rev=made href=mailto:g...@gcc.gnu.org /
+link rel=shortcut icon href=https://gcc.gnu.org/favicon.ico; /
+link rel=stylesheet type=text/css href=https://gcc.gnu.org/gcc.css; /
+
+ title
+How to test GCC on a simulator
+- GNU Project - Free Software Foundation (FSF)/title
+
+ /head
+
body
+
+
+
h1How to test GCC on a simulator/h1
pSeveral GCC targets can be tested using simulators. These allow
@@ -11,270 +43,280 @@
access to hardware, or for targets that have general characteristics
you'd like to test, like endianness or word size./p
-pAll of the instructions here start out from a directory we'll
-call code${TOP}/code, which is initially empty./p
-
-h2Set up sources/h2
-
-pTesting with a simulator requires use of a combined tree;
-you can't easily build newlib, required for simulator testing,
-outside of a combined tree, and the build of the other components
-is easiest in a combined tree./p
-
-pThe combined tree contains GCC sources plus several modules of
-the codesrc/code tree: codebinutils/code and
-codenewlib/code for the build and codesim/code for the
-simulators. If you already build with a combined tree you can use
-your current setup; if not, these instructions will get you the
-sources you need./p
-
-h3Check out initial CVS trees/h3
-
-pIf you don't yet have either tree you'll need to do an initial
-check-outs./p
+h2Setup/h2
-pCheck out mainline GCC:/p
+pTesting with a simulator requires an installation of a working
+GCC toolchain and a GDB simulator. For a list of supported targets please
+refer to the a href=http://www.sourceware.org/gdb/download/onlinedocs/gdb.html#Embedded-Processors;GDB documentation/a.
+The following describes how to create a Renesas SuperH cross compiler
+setup that can be used for simulator testing.
+/p
+pAll of the instructions here start out from a directory we'll
+call code${TOP}/code, which contains the following directories with
+unpacked sources:
+ul
+licode${TOP}/binutils-src/code/li
+licode${TOP}/gcc-src/code/li
+licode${TOP}/newlib-src/code/li
+licode${TOP}/gdb-src/code/li
+/ul
+and the following corresponding build directories which are initially
+empty:
+ul
+licode${TOP}/binutils-build/code/li
+licode${TOP}/gcc-build/code/li
+licode${TOP}/newlib-build/code/li
+licode${TOP}/gdb-build/code/li
+/ul
+To keep things simple, all parts of the cross toolchain will be installed
+into code/usr/local/code, which usually requires superuser rights for
+writing. If that is inconvenient, you might also install it into another
+place.
+/p
+
+h3Build and install Binutils/h3
pre
-cd ${TOP}
-svn checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
-# This makes sure that file timestamps are in order initially.
-cd ${TOP}/gcc
-contrib/gcc_update --touch
+cd ${TOP}/binutils-build
+../binutils-src/configure --target=sh-elf --prefix=/usr/local --disable-nls --disable-werror
+make all
+sudo make install
/pre
+This should have installed the cross
