| Commit message (Collapse) | Author | Files | Lines |
|
Adjust build support files to new directory layout.
This patch is a part of the BSP source reorganization.
Update #3285.
|
|
Updates #3520.
|
|
Update #2408.
|
|
The TLS section symbols had wrong values in case of an empty TLS data
section and a nonempty TLS BSS section.
|
|
|
|
Script does what is expected and tries to do it as
smartly as possible.
+ remove occurrences of two blank comment lines
next to each other after Id string line removed.
+ remove entire comment blocks which only exited to
contain CVS Ids
+ If the processing left a blank line at the top of
a file, it was removed.
|
|
* Makefile.am, include/bsp.h, startup/init68360.c, startup/linkcmds,
startup/linkcmds.bootp, startup/linkcmds.prom: Use top level shared
bsp_get_work_area() implementation.
|
|
* startup/linkcmds, startup/linkcmds.bootp, startup/linkcmds.prom: Add
wildcard to gcc_except_table section so programs compiled with gcc
4.3.x can link.
|
|
* startup/linkcmds: Handle .data.* sections
|
|
* startup/linkcmds, startup/linkcmds.bootp, startup/linkcmds.prom: Add
sections required by newer gcc versions.
|
|
* startup/linkcmds, startup/linkcmds.bootp, startup/linkcmds.prom: Add
new bss sections .bss.* and .gnu.linkonce.b*.
|
|
* startup/linkcmds: Add .gnu.linkonce.b.*.
|
|
|
|
* startup/linkcmds: In support of gcc 3.1, added one of more
of the sections .jcr, .rodata*, .data.*, .gnu.linkonce.s2.*,
.gnu.linkonce.sb2.*, and .gnu.linkonce.s.*. Spacing corrections
and direction of segments to memory regions may also have been
addressed. This was a sweep across all BSPs.
|
|
* startup/linkcmds: Added lines so DWARF debug information
would be available. Otherwise gdb complains that the offsets
for the debug info are incorrect and doesn't load the files.
|
|
|
|
|
|
|
|
for the gen68360 that let it work with ELF and C++ exceptions. This
was used as the basis for changes to EVERY m68k bsp_specs and linkcmds.
Before this modification is over, the layout of the starting stack,
heap, and workspace will likely be modified for every m68k BSP. Then
they will all be very similar.
|
|
In another attempt to get C++ exceptions working on the gen68360 target
I tried building for the m68k-elf target. All the tools built and
installed properly as did all of RTEMS. No applications would run,
though -- not even hello.exe!
It turns out the problem was in the linker script. The alignment was in
the wrong place.
Here's a patch. Exceptions still don't work, but at least I can get
some things working with the ELF format now.
|
|
work with m68k-elf on late model versions of binutils (990901+)
without overlapping or missing section errors.
|
|
Here are some patches to the gen68360 BSP. The improvements include:
Boot prom run-time selection of DRAM size (1/4/16 Mbytes)
Full 32-bit ethernet address obtained from boot prom.
Updated README.
|
|
|
|
1) In my haste to add C++ constructor/destructors to the 68360
linkcmds scripts I managed to break all existing 68360 programs.
Linker scripts which actually produce a working executable are
contained below. The problem was that the constructor/destructors
weren't included before the etext symbol.
On top of that Eric and I appear to have problems with attachments:
2) In deciphering the above problem I think I stumbled across the
reason you've had with patches mailed from me. I noticed that the
linkcmds (and linkcmds.bootp) scripts in the latest distribution have
a control-M (carriage return) at the end of each line. Could you
check the files below before installing them in the distribution and
see that there aren't returns in the files? Maybe if I send
everything as a tar attatchment things will work better.
|
|
|
|
|
|
was done based on the 3.6.0 release and had to be autoconf'ed locally.
It is turned on is the bsp enables it and it is not explicitly disabled
via the configure option --disable-tcpip. As many warnings as possible
were removed locally after the code was merged. Only the gen68360
and mvme136 bsps were compiled this way.
The ka9q port and network driver were submitted by Eric Norum
(eric@skatter.USask.Ca).
The network demo programs are not included in the tree at this point.
|
|
up to 2.6
|
|
|
|
should be undone when the m68k-coff cross toolset is updated next time.
|
|
Contact information:
W. Eric Norum
Saskatchewan Accelerator Laboratory
107 North Road
University of Saskatchewan
Saskatoon, Saskatchewan, CANADA
S7N 5C6
|