drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* doc/porting.texi: Fix typos.

This commit is contained in:
Corinna Vinschen 2010-09-23 08:07:47 +00:00
parent 631c8d784b
commit 4996145486
2 changed files with 17 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
libgloss/ChangeLog
View File

@ -1,3 +1,8 @@
2010-09-23 Mike Frysinger <vapier@gentoo.org>
Corinna Vinschen <vinschen@redhat.com>
* doc/porting.texi: Fix typos.
2010-09-22 Mike Frysinger <vapier@gentoo.org> 2010-09-22 Mike Frysinger <vapier@gentoo.org>
* README: Add bfin to the list. * README: Add bfin to the list.

24
libgloss/doc/porting.texi
View File

@ -104,18 +104,18 @@ the final executable image.
Most of the time a tool chain does only have to support one target Most of the time a tool chain does only have to support one target
execution environment. An example of this would be a tool chain for the execution environment. An example of this would be a tool chain for the
AMD 29k processor family. All of the execution environments for this AMD 29k processor family. All of the execution environments for this
processor are have the same interface, the same memory map, and the same processor have the same interface, the same memory map, and the same
I/O code. In this case all of the support code is in newlib/sys/FIXME. I/O code. In this case all of the support code is under newlib/libc/sys.
Libgloss's creation was forced initially be the @code{cpu32} processor Libgloss's creation was forced initially because of the @code{cpu32}
family. There are many different execution environments for this line, processor family. There are many different execution environments for
and they vary wildly. newlib itself has only has a few dependencies that this line, and they vary wildly. newlib itself has only a few
it needs for each target. These are explained later in this doc. The dependencies that it needs for each target. These are explained later in
hardware dependent part of newlib was reorganized into a separate this doc. The hardware dependent part of newlib was reorganized into a
directory structure within newlib called the stub dirs. It was initially separate directory structure within newlib called the stub dirs. It was
called this because most of the routines newlib needs for a target were initially called this because most of the routines newlib needs for a
simple stubs that do nothing, but return a value to the application. They target were simple stubs that do nothing, but return a value to the
only exist so the linker can produce a final executable image. This work application. They only exist so the linker can produce a final
was done during the early part of 1993. executable image. This work was done during the early part of 1993.
After a while it became apparent that this approach of isolating the After a while it became apparent that this approach of isolating the
hardware and systems files together made sense. Around this same time hardware and systems files together made sense. Around this same time