[RTEMS Project] #2577: Complete per-function section addition sweep

[RTEMS trac]

#2577: Complete per-function section addition sweep
---------------------------+----------------------------
 Reporter:  Joel Sherrill  |       Owner:  Joel Sherrill
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  Indefinite
Component:  bsps           |     Version:  5
 Severity:  normal         |  Resolution:
 Keywords:                 |  Blocked By:
 Blocking:                 |
---------------------------+----------------------------
Description changed by Joel Sherrill:

Old description:

> As part of the GCI task described at
> https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs, most
> BSPs were reviewed for the addition of per function section compilation
> and linking. This ticket is to complete that sweep.
>
> Follow the instructions in that GCI task with the addition that you
> should be EXTREMELY cautious in reviewing the size drop and whether the
> BSP linker script has KEEP sections. If the BSP does not have KEEP
> sections file a ticket to track it.
>

> Use #2572 as a guide for the new ticket. Just copy the contents and
> change the title to reflect the different BSP. Use the commented out
> lines for the mcf5206elite BSP make/custom file as a guide.
>
> Short version:
>
> * Do the GCI task for each BSP family listed below. Follow the format for
> the commit message.
> * If the BSP has KEEP sections and cxx_iostream does not drop a
> suspiciously large amount, then the modification should be OK to be
> merged.
> * If the BSP does NOT have KEEP sections, then a BSP specific ticket
> should be filed and the per-function section build lines commented out in
> the .cfg file with a FIXME line and the ticket number.
> * When done, update this ticket so the BSP family either says "done" or
> has a ticket number next to it. We need to track the remaining set to
> sweep this into.
>
> Be very careful to follow the existing patterns for tickets, commit
> messages, and code changes.
>
> * arm/lpc24xx
> * arm/lpc32xx
> * arm/raspberrypi
> * arm/realview-pbx-a9
> * arm/rtl22xx
> * arm/smdk2410
> * arm/stm32f4
> * arm/tms570
> * arm/xilinx-zynq
> * bfin/bf537Stamp
> * bfin/eZKit533
> * bfin/TLL6527M
> * epiphany/epiphany_sim
> * i386/pc386
> * lm32/lm32_evr
> * lm32/milkymist
> * m32c/m32cbsp
> * nios2/nios2_iss
> * or1k/generic_or1k
> * powerpc/motorola_powerpc - #2579
> * sh/gensh1
> * sh/gensh2
> * sh/gensh4
> * sh/shsim
> * sparc64/niagara
> * sparc64/usiii
> * v850/gdbv850sim

New description:

 As part of the GCI task described at
 https://devel.rtems.org/wiki/GCI/Coding/AddPerSectionSupportToBSPs, most
 BSPs were reviewed for the addition of per function section compilation
 and linking. This ticket is to complete that sweep.

 Use #2572 as a guide for the new ticket. Just copy the contents and change
 the title to reflect the different BSP. Use the commented out lines for
 the mcf5206elite BSP make/custom file as a guide.  Short version:

 * Do the GCI task for each BSP family listed below. Follow the format for
 the commit message.

 * If the BSP has KEEP sections and cxx_iostream does not drop a
 suspiciously large amount, then the modification should be OK to be
 merged.

 * If the BSP does NOT have KEEP sections, then a BSP specific ticket
 should be filed and the per-function section build lines commented out in
 the .cfg file with a FIXME line and the ticket number.

 * When done, update the associated ticket for the BSP family as needed. It
 should be closed as a side-effect of commiting any fixes so do NOT
 manually close them.

 Follow the instructions in that GCI task with the addition that you should
 be EXTREMELY cautious in reviewing the size drop and whether the BSP
 linker script has KEEP sections. If the BSP does not have KEEP sections
 file a ticket to track it.

 Be very careful to follow the existing patterns for tickets, commit
 messages, and code changes such as #2579 for the powerpc/motorola_powerpc.
 At the bottom of this text is a current list of "BSP families" which an
 automated search shows as missing per-function section linking.


 FIXME: Inline this query.
 The tickets associated with this activity are shown here:
 https://devel.rtems.org/query?status=!closed&keywords=~KEEP

 Some of these may already be implemented and just need to be reviewed and
 closed. Close this ticket when they are all done

 The following BSPs were shown to need per function sections by an
 automated search on 14 September 2018

 * m68k/av5282 - #2574
 * m68k/gen68340 - #2573
 * m68k/gen68360 - #2566
 * m68k/mcf5235 - #2571
 * m68k/mcf5329 - #2569
 * m68k/mcf5206elite - #2572
 * m68k/mrm332 - #2567
 * m68k/mcf5225x - #2568
 * m68k/uC5282 - #2575
 * powerpc/haleakala - #2561
 * powerpc/mpc8260ads - #2565
 * powerpc/qemuppc - #2564
 * powerpc/ss555 - #2563

--

--
Ticket URL: <http://devel.rtems.org/ticket/2577#comment:8>
RTEMS Project <http://www.rtems.org/>
RTEMS Project