public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
@ 1997-11-14 17:02 teunis
  1997-11-16 22:46 ` Jeffrey A Law
  0 siblings, 1 reply; 11+ messages in thread
From: teunis @ 1997-11-14 17:02 UTC (permalink / raw)
  To: egcs list

configure --enable-shared --prefix=/usr

Are there any problems with this?

and:
	What's the proper way to test egcs?  (make check?)
	How does one make a cross-compiler?
		(first few attempts failed ....)

TIA and G'day, eh? :)
	- Teunis

Test Run By root on Fri Nov 14 18:08:10 1997
Native configuration is i586-pc-linux-gnu

		=== libio tests ===

Running target unix
Using /usr/bin/../share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/bin/../share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/default.exp as tool-and-target-specific interface file.
Running ./libio.tests/hounddog.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/hounddog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs
-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/hounddog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/hounddog.cc:25:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/hounddog.cc:25:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: hounddog.cc compilation 
XFAIL: hounddog.cc execution 
XFAIL: hounddog.cc output 
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/hounddog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs
-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/hounddog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/hounddog.cc:25:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/hounddog.cc:25:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: hounddog.cc compilation -b0
XFAIL: hounddog.cc execution -b0
XFAIL: hounddog.cc output -b0
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/hounddog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs
-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/hounddog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/hounddog.cc:25:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/hounddog.cc:25:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: hounddog.cc compilation -b2
XFAIL: hounddog.cc execution -b2
XFAIL: hounddog.cc output -b2
testcase ./libio.tests/hounddog.exp completed in 8 seconds
Running ./libio.tests/putbackdog.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/putbackdog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/eg
cs-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/putbackdog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/putbackdog.cc:27:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/putbackdog.cc:27:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: putbackdog.cc compilation 
XFAIL: putbackdog.cc execution 
XFAIL: putbackdog.cc output 
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/putbackdog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/eg
cs-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/putbackdog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/putbackdog.cc:27:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/putbackdog.cc:27:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: putbackdog.cc compilation -b0
XFAIL: putbackdog.cc execution -b0
XFAIL: putbackdog.cc output -b0
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/putbackdog.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/eg
cs-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/putbackdog   
output is:
In file included from ../iostream.h:31,
                 from ./../tests/putbackdog.cc:27:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ./../tests/putbackdog.cc:27:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
FAIL: putbackdog.cc compilation -b2
XFAIL: putbackdog.cc execution -b2
XFAIL: putbackdog.cc output -b2
testcase ./libio.tests/putbackdog.exp completed in 8 seconds
Running ./libio.tests/tFile.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tFile.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs-97
1114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tFile   
compiler exited with status 1
output is:
In file included from ../iostream.h:31,
                 from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
../fstream.h: In method `class fstreambase & fstreambase::raw()':
In file included from ./../tests/tFile.cc:33:
../fstream.h:55: no matching function for call to `filebuf::setbuf (void *, int)'
../streambuf.h:434: candidates are: filebuf::setbuf(char *, int)
../strstream.h: At top level:
In file included from ./../tests/tFile.cc:35:
../strstream.h:64: warning: invalid type `void *' for default argument to `signed char *'
../strstream.h:58: warning: invalid type `void *' for default argument to `unsigned char *'
../strstream.h:56: warning: invalid type `void *' for default argument to `char *'
./../tests/tFile.cc: In function `void t9()':
./../tests/tFile.cc:382: warning: ANSI C++ forbids implicit conversion from `void *' in default argument
./../tests/tFile.cc:399: warning: ANSI C++ forbids implicit conversion from `void *' in default argument

FAIL: tFile.cc compilation 
XFAIL: tFile.cc execution 
XFAIL: tFile.cc output 
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tFile.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs-97
1114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tFile   
compiler exited with status 1
output is:
In file included from ../iostream.h:31,
                 from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
../fstream.h: In method `class fstreambase & fstreambase::raw()':
In file included from ./../tests/tFile.cc:33:
../fstream.h:55: no matching function for call to `filebuf::setbuf (void *, int)'
../streambuf.h:434: candidates are: filebuf::setbuf(char *, int)
../strstream.h: At top level:
In file included from ./../tests/tFile.cc:35:
../strstream.h:64: warning: invalid type `void *' for default argument to `signed char *'
../strstream.h:58: warning: invalid type `void *' for default argument to `unsigned char *'
../strstream.h:56: warning: invalid type `void *' for default argument to `char *'
./../tests/tFile.cc: In function `void t9()':
./../tests/tFile.cc:382: warning: ANSI C++ forbids implicit conversion from `void *' in default argument
./../tests/tFile.cc:399: warning: ANSI C++ forbids implicit conversion from `void *' in default argument

FAIL: tFile.cc compilation -b0
XFAIL: tFile.cc execution -b0
XFAIL: tFile.cc output -b0
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tFile.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs-97
1114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tFile   
compiler exited with status 1
output is:
In file included from ../iostream.h:31,
                 from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../streambuf.h:394: warning: invalid type `void *' for default argument to `ios *'
In file included from ../stream.h:33,
                 from ./../tests/tFile.cc:32:
../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
../fstream.h: In method `class fstreambase & fstreambase::raw()':
In file included from ./../tests/tFile.cc:33:
../fstream.h:55: no matching function for call to `filebuf::setbuf (void *, int)'
../streambuf.h:434: candidates are: filebuf::setbuf(char *, int)
../strstream.h: At top level:
In file included from ./../tests/tFile.cc:35:
../strstream.h:64: warning: invalid type `void *' for default argument to `signed char *'
../strstream.h:58: warning: invalid type `void *' for default argument to `unsigned char *'
../strstream.h:56: warning: invalid type `void *' for default argument to `char *'
./../tests/tFile.cc: In function `void t9()':
./../tests/tFile.cc:382: warning: ANSI C++ forbids implicit conversion from `void *' in default argument
./../tests/tFile.cc:399: warning: ANSI C++ forbids implicit conversion from `void *' in default argument

FAIL: tFile.cc compilation -b3
XFAIL: tFile.cc execution -b3
XFAIL: tFile.cc output -b3
testcase ./libio.tests/tFile.exp completed in 45 seconds
Running ./libio.tests/tfformat.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tfformat.c  -O3 -I.. -I./..  -DTEST_LIBIO -DTEST_EXACTNESS -L/archive/src/egcs-971114/libraries/libio -L/archive/src/egcs-971114/libraries//libiberty -g -lio -
liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tfformat   
PASS: tfformat.c compilation 
PASS: tfformat.c execution 
testcase ./libio.tests/tfformat.exp completed in 16 seconds
Running ./libio.tests/tiformat.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tiformat.c  -O3 -I.. -I./..  -DTEST_LIBIO -L/archive/src/egcs-971114/libraries/libio -L/archive/src/egcs-971114/libraries//libiberty -g -lio -liberty   -lm  -o
 /archive/src/egcs-971114/libraries/libio/testsuite/tiformat   
PASS: tiformat.c compilation 
PASS: tiformat.c execution 
testcase ./libio.tests/tiformat.exp completed in 10 seconds
Running ./libio.tests/tiomanip.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tiomanip.cc  -O3 -I.. -I./..  -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/egcs
-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tiomanip   
PASS: tiomanip.cc compilation 
PASS: tiomanip.cc execution 
PASS: tiomanip.cc output 
testcase ./libio.tests/tiomanip.exp completed in 2 seconds
Running ./libio.tests/tiomisc.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tiomisc.cc  -O3 -I.. -I./..  -w -nostdinc++ -I/archive/src/egcs-971114/libraries/libstdc++ -I/archive/src/egcs-971114/libraries/libstdc++/stl -L/archive/src/eg
cs-971114/libraries//libstdc++ -L/archive/src/egcs-971114/libraries//libiberty  -L/archive/src/egcs-971114/libraries//libiberty -g -lstdc++ -liberty   -lm  -o /archive/src/egcs-971114/libraries/libio/testsuite/tiomisc   
PASS: tiomisc.cc compilation 
PASS: tiomisc.cc execution 
PASS: tiomisc.cc output 
testcase ./libio.tests/tiomisc.exp completed in 7 seconds
Running ./libio.tests/tstdiomisc.exp ...
Executing on host: /archive/src/egcs-971114/gcc/xgcc -B/archive/src/egcs-971114/gcc/ ./../tests/tstdiomisc.c  -O3 -I.. -I./..  -L/archive/src/egcs-971114/libraries/libio -L/archive/src/egcs-971114/libraries//libiberty -g -lio -liberty   -lm  -o /archive/s
rc/egcs-971114/libraries/libio/testsuite/tstdiomisc   
PASS: tstdiomisc.c compilation 
PASS: tstdiomisc.c execution 
PASS: tstdiomisc.c output 
testcase ./libio.tests/tstdiomisc.exp completed in 1 seconds

		=== libio Summary ===

# of expected passes		13
# of unexpected failures	9
# of expected failures		18
runtest completed at Fri Nov 14 18:09:48 1997



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-14 17:02 linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :) teunis
@ 1997-11-16 22:46 ` Jeffrey A Law
  1997-11-17 10:23   ` H.J. Lu
  1997-11-17 14:21   ` teunis
  0 siblings, 2 replies; 11+ messages in thread
From: Jeffrey A Law @ 1997-11-16 22:46 UTC (permalink / raw)
  To: teunis; +Cc: egcs list

  In message < Pine.LNX.3.96.971114180852.16600A-100000@sigil.computersupportcentre.com >you write:
  > and:
  > 	What's the proper way to test egcs?  (make check?)
make check

  > 	How does one make a cross-compiler?
  > 		(first few attempts failed ....)
Same, however you need many more pieces to get meaningful results (cross
assembler, linker, libraries & a simulator).


  > ../streambuf.h:394: warning: invalid type `void *' for default argument to ios *'
  > In file included from ./../tests/hounddog.cc:25:
  > ../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
  > ../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
  > ../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
Hmmm, I thought we had fixed this problem several snapshots ago.

Jason, HJ any thoughts?


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-16 22:46 ` Jeffrey A Law
@ 1997-11-17 10:23   ` H.J. Lu
  1997-11-17 13:18     ` Paul Koning
  1997-11-17 14:21   ` teunis
  1 sibling, 1 reply; 11+ messages in thread
From: H.J. Lu @ 1997-11-17 10:23 UTC (permalink / raw)
  To: law; +Cc: teunis, egcs, Ulrich Drepper

> 
>   In message < Pine.LNX.3.96.971114180852.16600A-100000@sigil.computersupportcentre.com >you write:
>   > and:
>   > 	What's the proper way to test egcs?  (make check?)
> make check
> 
>   > 	How does one make a cross-compiler?
>   > 		(first few attempts failed ....)
> Same, however you need many more pieces to get meaningful results (cross
> assembler, linker, libraries & a simulator).
> 
> 
>   > ../streambuf.h:394: warning: invalid type `void *' for default argument to ios *'
>   > In file included from ./../tests/hounddog.cc:25:
>   > ../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
>   > ../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
>   > ../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
> Hmmm, I thought we had fixed this problem several snapshots ago.
> 
> Jason, HJ any thoughts?
> 

I think it may be NULL defined in the kernel source. Jason has defined
NULL in _G_config.h. But glibc uses its own _G_config.h. Ulrich may
be glibc should do the same. Should it be in glibc 2.0.6?


-- 
H.J. Lu (hjl@gnu.ai.mit.edu)

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-17 10:23   ` H.J. Lu
@ 1997-11-17 13:18     ` Paul Koning
  0 siblings, 0 replies; 11+ messages in thread
From: Paul Koning @ 1997-11-17 13:18 UTC (permalink / raw)
  To: hjl; +Cc: egcs

>>>>> "H" == H J Lu <hjl@lucon.org> writes:

 H> I think it may be NULL defined in the kernel source. 

Grep shows up 5 files in /usr/include/linux that define NULL, and they
all define it wrong (i.e., as (void *)0 ).

	paul

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-16 22:46 ` Jeffrey A Law
  1997-11-17 10:23   ` H.J. Lu
@ 1997-11-17 14:21   ` teunis
  1997-11-18 22:06     ` Jeffrey A Law
  1 sibling, 1 reply; 11+ messages in thread
From: teunis @ 1997-11-17 14:21 UTC (permalink / raw)
  To: law; +Cc: egcs list

On Sun, 16 Nov 1997, Jeffrey A Law wrote:

>   In message < Pine.LNX.3.96.971114180852.16600A-100000@sigil.computersupportcentre.com >you write:
>   >
>   > 	How does one make a cross-compiler?
>   > 		(first few attempts failed ....)
> Same, however you need many more pieces to get meaningful results (cross
> assembler, linker, libraries & a simulator).

binutils-latest + support for additional wanted platforms (eg. Win32 :)
libraries?  I don't know where to obtain them.
Same for simulator....  (why a simulator?)

> 
>   > ../streambuf.h:394: warning: invalid type `void *' for default argument to ios *'
>   > In file included from ./../tests/hounddog.cc:25:
>   > ../iostream.h:50: warning: invalid type `void *' for default argument to `ostream *'
>   > ../iostream.h:123: warning: invalid type `void *' for default argument to `ostream *'
>   > ../iostream.h:230: warning: invalid type `void *' for default argument to `ostream *'
> Hmmm, I thought we had fixed this problem several snapshots ago.

Seems to prolly be a glibc-2.0.5c-ism...  as the other entry I've seen
here was from glibc-1 (libc5?)

I also get random "exception 11"s - where I didn't used to with previous
compilers.  [they're quite consistent actually - but I haven't yet tracked
down what's causing them]

TIA and G'day, eh? :)
	- Teunis


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-17 14:21   ` teunis
@ 1997-11-18 22:06     ` Jeffrey A Law
  1997-11-19  8:46       ` teunis
  0 siblings, 1 reply; 11+ messages in thread
From: Jeffrey A Law @ 1997-11-18 22:06 UTC (permalink / raw)
  To: teunis; +Cc: egcs list

  In message < Pine.LNX.3.96.971117143148.2661A-100000@sigil.computersupportcentre.com >you write:
  > binutils-latest + support for additional wanted platforms (eg. Win32 :)
  > libraries?  I don't know where to obtain them.
  > Same for simulator....  (why a simulator?)
Well, for many you can use the latest newlib release.

You'd want a instruction set simulator so that you can run the "execution"
tests -- particularly useful if you don't have a target board, or it has
a terribly slow (less than ethernet) speed link.

  > Seems to prolly be a glibc-2.0.5c-ism...  as the other entry I've seen
  > here was from glibc-1 (libc5?)
Likely.

  > I also get random "exception 11"s - where I didn't used to with previous
  > compilers.  [they're quite consistent actually - but I haven't yet tracked
  > down what's causing them]
You might want to look at the g77 info files for "Signal 11 and Friends".  This
might be a hardware failure.

jeff 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-18 22:06     ` Jeffrey A Law
@ 1997-11-19  8:46       ` teunis
  1997-11-22  0:42         ` Jeffrey A Law
  0 siblings, 1 reply; 11+ messages in thread
From: teunis @ 1997-11-19  8:46 UTC (permalink / raw)
  To: law; +Cc: egcs list

On Tue, 18 Nov 1997, Jeffrey A Law wrote:

>   In message < Pine.LNX.3.96.971117143148.2661A-100000@sigil.computersupportcentre.com >you write:
>   > binutils-latest + support for additional wanted platforms (eg. Win32 :)
>   > libraries?  I don't know where to obtain them.
>   > Same for simulator....  (why a simulator?)
> Well, for many you can use the latest newlib release.

???? newlib release ????

> You'd want a instruction set simulator so that you can run the "execution"
> tests -- particularly useful if you don't have a target board, or it has
> a terribly slow (less than ethernet) speed link.

To be quite honest:
	I don't have immediate access to some of the hardware.....
	... and there's no Win32 emulator available... that works.

So how do I build a cross-compiler?

>   > I also get random "exception 11"s - where I didn't used to with previous
>   > compilers.  [they're quite consistent actually - but I haven't yet tracked
>   > down what's causing them]
> You might want to look at the g77 info files for "Signal 11 and Friends".  This
> might be a hardware failure.

No - this is definitely egcs-971114
	(ref someone else's post about linux source causing this)

gcc-2.7.2.1 - works perfectly on all files
egcs-2.90.10p (pentium-gcc mods) - works perfectly... most of the time...
	(older egcs - some bugs present then)
egcs-2.90.16 - some problems, nothing serious.

my test code is ~3M of VR/math-related work.  VERY cpu-intensive (and
memory-intensive) to compile.  Makes an excellent test of optimizations
too - for instance: pgcc's output code is 30-50% faster than gcc-2.7.2.1's
output code with this project.

... egcs (plus other changes to the computer) have slowed it down - so
egcs is not yet as efficient for i586 as pentium-gcc.

G'day, eh? :)
	- Teunis


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-19  8:46       ` teunis
@ 1997-11-22  0:42         ` Jeffrey A Law
  1997-11-23 15:41           ` Joel Sherrill
  1997-11-27  2:29           ` teunis
  0 siblings, 2 replies; 11+ messages in thread
From: Jeffrey A Law @ 1997-11-22  0:42 UTC (permalink / raw)
  To: teunis; +Cc: egcs list

  In message <Pine.LNX.3.96.971119094848.5443B-100000@sigil.computersupportcent
re.com>you write:
  > On Tue, 18 Nov 1997, Jeffrey A Law wrote:
  > > Well, for many you can use the latest newlib release.
  > 
  > ???? newlib release ????
newlib is a ANSI C library.  It's what Cygnus uses for most of its cross
builds.  I also believe it's used by RTEMS.

ftp.cygnus.com:pub/newlib

  > To be quite honest:
  > 	I don't have immediate access to some of the hardware.....
  > 	... and there's no Win32 emulator available... that works.
Which is why an instruction set simulator is so useful; not I'm not talking
about hardware, I'm talking about a program that simulates the ISA of a
particular chip.

  > So how do I build a cross-compiler?
I really don't have the time to discuss all the aspects of building a
cross compiler, because doing so also requires additional tools (cross
assembler, cross linker, cross binutils, target include files, target
libraries, etc etc).

If you just want a compiler that generates code for some target then
configure --target=blah
make cross

It will probably fail building libgcc1 or libgcc2 because you probably don't
have a cross assembler or suitable include files.


Jeff



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-22  0:42         ` Jeffrey A Law
@ 1997-11-23 15:41           ` Joel Sherrill
  1997-11-24  0:32             ` Jeffrey A Law
  1997-11-27  2:29           ` teunis
  1 sibling, 1 reply; 11+ messages in thread
From: Joel Sherrill @ 1997-11-23 15:41 UTC (permalink / raw)
  To: Jeffrey A Law; +Cc: teunis, egcs list

On Sat, 22 Nov 1997, Jeffrey A Law wrote:

>   > > Well, for many you can use the latest newlib release.
>   > 
>   > ???? newlib release ????
> newlib is a ANSI C library.  It's what Cygnus uses for most of its cross
> builds.  I also believe it's used by RTEMS.
> 
> ftp.cygnus.com:pub/newlib

Yes.  newlib is the official C Library of RTEMS.  AFAIK RTEMS is the only
OS for which that is the case.

>   > 	I don't have immediate access to some of the hardware.....
>   > 	... and there's no Win32 emulator available... that works.
> Which is why an instruction set simulator is so useful; not I'm not talking
> about hardware, I'm talking about a program that simulates the ISA of a
> particular chip.

psim for the PowerPC and sis for the SPARC ERC32 are both very good
simulators.  Both can be viewed as a simple embedded target with a serial
port for console IO and a timer. 

>   > So how do I build a cross-compiler?
> I really don't have the time to discuss all the aspects of building a
> cross compiler, because doing so also requires additional tools (cross
> assembler, cross linker, cross binutils, target include files, target
> libraries, etc etc).

The best thing to do is read the crossgcc FAQ at
ftp.cygnus.com:/pub/embedded/crossgcc.

Good Luck.

--joel
Joel Sherrill                    Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (205) 722-9985




^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-23 15:41           ` Joel Sherrill
@ 1997-11-24  0:32             ` Jeffrey A Law
  0 siblings, 0 replies; 11+ messages in thread
From: Jeffrey A Law @ 1997-11-24  0:32 UTC (permalink / raw)
  To: Joel Sherrill; +Cc: teunis, egcs list

  In message < Pine.BSF.3.96.971123173901.6353B-100000@vespucci.advicom.net >you 
write:
  > 
  > The best thing to do is read the crossgcc FAQ at
  > ftp.cygnus.com:/pub/embedded/crossgcc.
Agreed.  I'll also put  a pointer to the crossgcc FAQ in the egcs FAQ.

jeff

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :)
  1997-11-22  0:42         ` Jeffrey A Law
  1997-11-23 15:41           ` Joel Sherrill
@ 1997-11-27  2:29           ` teunis
  1 sibling, 0 replies; 11+ messages in thread
From: teunis @ 1997-11-27  2:29 UTC (permalink / raw)
  To: Jeffrey A Law; +Cc: egcs list

FWIW : this should be documented somewhere....

README.cross material?

On Sat, 22 Nov 1997, Jeffrey A Law wrote:

>   > > Well, for many you can use the latest newlib release.
>   > 
>   > ???? newlib release ????
> newlib is a ANSI C library.  It's what Cygnus uses for most of its cross
> builds.  I also believe it's used by RTEMS.
> 
> ftp.cygnus.com:pub/newlib
> 
>   > To be quite honest:
>   > 	I don't have immediate access to some of the hardware.....
>   > 	... and there's no Win32 emulator available... that works.
> Which is why an instruction set simulator is so useful; not I'm not talking
> about hardware, I'm talking about a program that simulates the ISA of a
> particular chip.
> 
>   > So how do I build a cross-compiler?
> I really don't have the time to discuss all the aspects of building a
> cross compiler, because doing so also requires additional tools (cross
> assembler, cross linker, cross binutils, target include files, target
> libraries, etc etc).
> 
> If you just want a compiler that generates code for some target then
> configure --target=blah
> make cross
       ^^^^^

This was the most important....  My compile was failing and I had no idea
why.....  this was it!

> It will probably fail building libgcc1 or libgcc2 because you probably don't
> have a cross assembler or suitable include files.

Already setup:
	Cross assembler
	Cross linker
(complete binutils....)

I was just missing the compiler.....  (and "newlib")

G'day, eh? :)
	- Teunis



^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~1997-11-27  2:29 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-11-14 17:02 linux-2.1.60/i586,glibc-2.0.5c,egcs-971114 snapshot :) teunis
1997-11-16 22:46 ` Jeffrey A Law
1997-11-17 10:23   ` H.J. Lu
1997-11-17 13:18     ` Paul Koning
1997-11-17 14:21   ` teunis
1997-11-18 22:06     ` Jeffrey A Law
1997-11-19  8:46       ` teunis
1997-11-22  0:42         ` Jeffrey A Law
1997-11-23 15:41           ` Joel Sherrill
1997-11-24  0:32             ` Jeffrey A Law
1997-11-27  2:29           ` teunis

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).